This reference code is for information only. It is shown in the Product activity log as a side effect of a condition that was detected by LIC.

Normally, no action should be taken as a result of information reference codes. However, to isolate the root cause, use these suggestions:
1.        Examine the date and time of the informational reference code.
2.        Determine if any other reference codes have been logged at or before the same date and time.
3.        Begin the service approach based on these other logged errors.

Words 2 to 9 of this SRC contain additional diagnostic information. Record SRC words 1 through 9 before attempting to IPL again and report the problem to your Software Service Provider.

Perform LICIP01.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

The server detected an unrecoverable machine check condition.

Collect all the words of the SRC and the main store dump and send to your system manufacturer for analysis.

Re-IPL the partition that terminated. Then, look for and correct errors with SRCs of the form B1xxxxxx in the Serviceable Event View that indicate the replacement of memory in the failing item list. If there are no B1xxxxxx SRCs in the Serviceable Event View that indicate a memory problem, perform a slow boot in order to run diagnostics on the memory. Then, look for and correct erros with SRCs of the form B1xxxxxx in the Serviceable Event View.

Restore the Licensed Internal Code using "Licensed Internal Code Install and Restore" in the iSeries™ Service Functions information.

The out of storage condition in the system ASP can be caused by an allocation failure in some other system software. This could be a looping condition that continues to allocate storage. Contact your service representative for assistance with the Main Storage Dump.

No service action required. This entry is logged for information only.

Provide the Product Activity Log entry to your next level of support for analysis.

Do not power off the system.

Perform LICIP13.

Note:
Do not power off the system when performing this procedure.

Look at the 4 leftmost characters of the Data display for word 7. These four characters indicate the type of problem that exists and the recovery action to perform.

If these characters are 8402 or 2002, the compression disk unit is temporarily full of data. The command to the compression disk is being held. When the storage subsystem controller has created sufficient space on the compression disk unit to contain the data, the command which is being held will be released and the system will resume normal processing. If the system does not resume normal processing within 20 minutes, contact your next level of support.

If these characters are 8400 or 2000, the compression disk unit is full of data. The command to the compression disk is being held.

The customer should perform the recovery actions specified in "Disk Unit Full Considerations" in the Backup and Recovery Guide .

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Component Specific Exception Handler recursion is detected in an OS/400 process.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

A main store dump was initiated.

Words 2 to 9 of this SRC contain additional diagnostic information. Record SRC words 1 through 9.

Perform a system IPL and collect the Product activity log and main store dump and provide them along with the recorded SRC information to IBM Service Support.

The problem may also be that there is not enough auxiliary storage.

During system IPL, the LIDMgr detected an I/O failure or media failure while trying to read the LID directory.

Perform LICIP08.

During system IPL, the LIDMgr detected that the LID directory and associated load source is not usable.

Reinstall the Licensed Internal Code by using Utilities to install and restore Licensed Internal Code.

For more information, contact IBM Service Support.

This reference code is usually the result of a system termination while the LinkLoader is performing its work.

Reinstall the Licensed Internal Code by using Utilities to install and restore Licensed Internal Code.

The LinkLoader was not successful in performing a programmed IPL.

Perform a system IPL. If the problem persists, examine the main storage dump and determine the reason for the failure of the programmed IPL.

Perform LICIP08.

MISR is not readable. Perform a manual install to reinitialize the system.

Determine that correct install media is loaded. If correct install media is installed, media could be corrupt. Obtain another copy of the install media and reattempt the install. If the install still fails, contact your service representative.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

Perform LICIP08.

An error occurred during task creation which requires a power off of the system.

Perform LICIP08.

The create could fail for two reasons:

• A code problem

• No free auxiliary storage on the system

Licensed Internal Code has detected a condition that is impacting system performance. System operation can continue, but system performance may be noticeably reduced until the next IPL.

Look at the Product Activity Log entry, and find the value at offset x'000180'. If the value equals x'00000122', the error was caused by too much processor memory being installed.

For more information, contact IBM Service Support.

Copy the current main storage dump to media. For more information on how to copy a Main Storage Dump, refer to the iSeries Service Functions Information (see "Copying a Main Storage Dump" under "Working with Storage Dumps").

Words 12 and 13 of this SRC contain additional diagnostic information.

Install LIC using physical media.

To determine what caused the failure, collect SRC information and contact your next level of support.

A main store dump was initiated. Words 12 and 13 of this SRC contain additional diagnostic information.

To recover the partition using the previously installed LIC, perform a B-mode IPL. You can then re-try the installation of LIC. Otherwise, install LIC using physical media.

To determine what caused this failure, collect SRC information and main store dump and contact your next level of support.

Copy the current main storage dump to media.

For more information on how to perform a Main Storage Dump, refer to iSeries Service Functions information (see "Copying a Main Storage Dump" under "Working with Storage Dumps").

Copy the current main storage dump to media. Then exit the Main Storage Dump Manager.

For more information on how to perform a Main Storage Dump, refer to iSeries Service Functions information (see "Copying a Main Storage Dump" under "Working with Storage Dumps").

Copy the current main storage dump to media.

For more information on how to perform a Main Storage Dump, refer to iSeries Service Functions information (see "Copying a Main Storage Dump" under "Working with Storage Dumps").

Copy the current main storage dump. If copying to system ASP, existing copies may need to be deleted or renamed. Then exit the Main Storage Dump Manager.

For more information on how to perform a Main Storage Dump, refer to iSeries Service Functions information (see "Copying a Main Storage Dump" under "Working with Storage Dumps").

Delete other system ASP copies or exit the Main Storage Dump Manager and then from DST copy the Auto Copy to media and then delete the Auto Copy in system ASP.

The platform produced dump data, but the Main Storage Dump (MSD) Manager was not configured to automatically copy the dump to an Auxiliary Storage Pool (ASP). The dump will be lost if the system power is lost. Use MSD Manager to manually copy the current platform dump to media or an ASP.

The platform produced dump data, and the Main Storage Dump (MSD) Manager was configured to automatically copy the dump to an Auxiliary Storage Pool (ASP), but there was not sufficient free space available in the ASP. The dump will be lost if the system power is lost. Manually copy the current platform dump from the platform by performing one of the following:

• Make room in the designated ASP and then use the MSD Manager to copy the current platform dump to ASP.
• Use the MSD Manager to delete other dump copies, then copy the current platform dump to ASP.
• Use the MSD Manager to copy the current platform dump to a different ASP.
• Use the MSD Manager to copy the current platform dump to media.

Processor on Demand Data Block key is not valid.

Replace the Processor Capacity card.

Processor On Demand Data Block contains data that does not match the expected data.

Contact your service provider.

Processor On Demand Serialization has failed during IPL.

Contact your service provider.

SPCN communication failure during Processor On Demand.

Look in the Product Activity Log for other SPCN errors and perform the actions indicated for those errors.

Correct any Processor Capacity card or SPCN failures.

The Processor Capacity Card is the failing item since it has been swapped in from a different system.

Put the Processor Capacity Card back in the system it came from, and reinstall this system's original Processor Capacity Card.

The Processor Capacity Card was changed and there may be a problem.

If the system did have any activated standby processors before the Processor Capacity Card was replaced, then new processor on demand activation codes must be obtained to restore the previous activations.

Contact your service provider.

Correct any Processor Capacity card or SPCN failures.

Processor On Demand standby processors are in use.

Contact your service provider.

The Processor On Demand Trial Activation period is not valid. Contact your next level of support.

Contact your service provider.

The Processor On Demand Activation code just entered is not valid.

Contact your next level of support.

An invalid Processor On Demand Activation code has been entered more than 5 consecutive times. Contact your service provider.

Contact IBM Support to order a replacement Processor On Demand activation code.

If a new activation code was purchased, it should be entered now. Otherwise, the system will revert back to its previous activation state at the end of the Trial Activation Period.

The workstation I/O processor for the system or partition console did not respond.

Perform RTRIP01 to determine which Isolation procedure to perform.

A code problem occurred during an attempt to use the system console.

Perform LICIP03.

The ASCII system console failed to respond.

The system console failed to respond.

Perform RTRIP02 to determine which isolation procedure to perform.

The workstation adapter system console failed to respond.

Perform WSAIP01.

The workstation adapter console failed to respond.

Perform RTRIP07 to determine which isolation procedure to perform.

Perform OPCIP03.

Perform LICIP04.

A service program lost contact with the system console.

Perform RTRIP03 to determine which isolation procedure to perform.

A service program lost contact with the system console.

Perform TWSIP01.

Perform the following:

• If reference code A6005090 is displayed on the control panel for more than 10 minutes, perform LICIP11.
• For reference code B6005090, perform LICIP11.

Perform LICIP12.

Perform LICIP03.

System LIC detected a programming problem. If performance or other system degradation is occurring, the system may be operating with reduced resources.

Check the Product activity log for related entries. If this reference code is logged with a Class of Informational, then no action is required.

Otherwise, perform LICIP01.

System LIC detected a programming problem for which a main storage dump may have been initiated.

A problem log entry may be generated for this ref code.

Perform LICIP01.

System LIC detected an IOP programming problem for which an IOP dump may have been initiated.

Perform LICIP01.

System LIC detected an interface problem with the IOP or an IOP programming problem for which an IOP and main storage dump may have been initiated.

Perform LICIP01.

Copy the IOP dump entry and any related entries from the Product Activity Log to suitable media, and give to an IBM service representative.

The system was in a D IPL mode when the problem was detected. A main storage dump was not taken.

Perform LICIP01.

System LIC detected a missing IOP LIC code load during IPL of the IOP. This indicates that either the IOP code load is not installed on the system load source device or that system LIC was unable to successfully read that load from the load source device.

Perform LICIP01.

Verify that all IOP cable connections are secure, and check tape and other non-disk devices and media to verify that they are in a ready state.

Perform LICIP01.

An IOP signalled to system LIC that it had entered a critical internal state. LIC automatically attempted to restart the IOP.

This reference code is logged for information only. No action is required.

System Licensed Internal Code detected that an IOP Reset/Reload has occurred, and that the IOP successfully recovered.

Users who were signed on to a Workstation device under the IOP will need to sign back on. Any LAN/WAN communications lines under the IOP will need to be restarted. Tape/Optical devices under the IOP may need to be varied back on.

To determine the cause of the IOP Reset/Reload, check the Product Activity Log for additional entries logged with the same System Log ID, and perform any actions indicated for those errors.

LIC has detected a problem with the Service Processor IOP and has reset it but has not initiated reload of the Service Processor.

If the load source is mirrored, some system operations may be able to continue normally. However, some system service operations have been suspended and the system should be scheduled for power down as soon as possible.

Perform RTRIP08.

System LIC detected a logical partition configuration data consistency error. Copy the Product Activity Log data for this error and any related entries and contact your next level of hardware service support.

LPAR configuration data does not match current system configuration. The system will not IPL past DST until the problem is corrected.

Following is a list of problems which may have caused this SRC to be reported:

• Non-configured disk unit which was previously a load source on a partitioned system.
• Load source configuration data does not match partition for which it is being used.
• Load source configuration data does not match system serial number for which it is being used.
• Load source configuration data is newer than primary partition configuration data.

LPAR configuration data informational error.

The LPAR configuration data was found to be or inconsistent on a secondary partition's load source. The data was automatically updated to the current system level.

LPAR configuration data informational error.

The LPAR configuration data was found to be inconsistent on a primary partition and could only be corrected with an older copy of the data.

An I/O Adapter used by a guest partition is located in a card slot on the same PCI bridge set as an I/O Processor. Guest partition data may be lost if any of the following occur:

• A primary partition Type D IPL is performed.
• The I/O Adapter is moved to an operating system partition.
• An error causes the logical partition (LPAR) configuration to not be used.

http://www.ibm.com/eserver/iseries/lpar

Check the Primary partition's Product Activity Log for system processor entries from approximately the same time. Perform the actions indicated for those entries.

Check the primary partition Product Activity Log for system memory entries from approximately the same time. Perform the actions indicated for those entries.

Check the Primary partition's Product Activity Log for system processor entries from approximately the same time. Perform the actions indicated for those entries.

Check the Primary partition's Product Activity Log for system memory errors from approximately the same time. Perform the actions indicated for those entries.

The interactive performance specified in the configuration data for this partition could not be met.

Contact your next level of support.

The logical partition software version is outside the supported release delta. Check the Release Delta from the Primary partition "Display Partition Release Level" screen.

Check the LPAR documentation for the release level of the Primary partition and determine what the supported Release Delta is.

Record the Product Activity Log (PAL) hex data for this SRC or print the PAL entry.

Contact your next level of support.

Record the Product Activity Log (PAL) hex data for this SRC or print the PAL entry.

Contact your next level of support.

IOP log data can be copied to a spool file for examination by the development lab.

VPD data could not be read.

Look for other errors implicating hardware. There is no way to know what VPD read has failed, but the resource is not useable and should generate an error.

If no such error occurred, call your next level of support.

LIC could not access part of the HSL I/O bridge VPD. The bridge and HSL loop may be prevented from becoming operational.

For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event viewer you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed.

If the Service Action Log (SAL) or serviceable event view on the HMC is available then use the failing item list presented there for servicing this reference code.

If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.

NOTE: A fiber optic cleaning kit may be required for optical HSL connections.

LIC detected invalid data in the HSL I/O bridge VPD. The bridge and HSL loop may not have become operational.

For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed.

If the Service Action Log (SAL) or serviceable event view on the HMC, is available then use the failing item list presented there for servicing this reference code.

If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.

NOTE: A fiber optic cleaning kit may be required for optical HSL connections.

LIC data in the I/O bus vpd could not be accessed. The I/O Bus identified in the SRC may not have become operational.

If there is a B600 6906 reference code, close this problem in the serviceable event view you are working with and work the 6906 error.

For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed.

If the Service Action Log or serviceable event view on the HMC or service processor is available then use the failing item list presented there for servicing this reference code.

If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.

NOTE: A fiber optic cleaning kit may be required for optical HSL connections.

LIC detected invalid data in the I/O bus VPD. The bus and resources associated with it may not be operational.

For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed.

If the Service Action Log (SAL) or serviceable event viewer on the HMC is available then use the failing item list presented there for servicing this reference code.

If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.

If the serviceable event view only indicated a frame or enclosure see the locations section for the frame or enclosure type. The location of the HSL I/O Bridge will be given in the locations tables.

NOTE: A fiber optic cleaning kit may be required for optical HSL connections.

Perform LICIP16.

An I/O processor timed out, returned bad status, or is not following the system bus protocol.

Perform LICIP07.

This system model does not allow a configuration of more than three (non-OptiConnect) I/O Processors.

Power down the system and remove the extra (non-OptiConnect) I/O Processor(s) so that there are three or less. Restart the system.

A system bus appears to be empty. If the bus is not empty, two I/O processors in consecutive slots may be missing or broken. If there are broken I/O processors, then another more serious SRC has occurred. Otherwise find the bus number for this failure from the Product activity log and use the system configuration list to verify the configuration of the I/O processors on that bus.

Slot unavailable due to 64 bit card in adjacent slot.

One of the messages documented with the symbolic FRU will describe the problem. See the SLOTERR symbolic FRU for a list of messages and corrective actions.

LED control failure, do not use slot.

The card location is not available for use. The Failing Item with the card slot error is in the Failing Item list for this reference code.

See the SLOTERR symbolic FRU for the list of messages and a further description of the problem detected by Licensed Internal Code.

For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed.

If the Service Action Log or a serviceable event viewer on the HMC is available for this problem then use the failing item list presented there for servicing this reference code.

If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.

Power control failure, do not use slot.

If there is a Linux partition in the system, any IOPs plugged into slots owned by a Linux partition will not power on. This error will be logged. Correct the situation by removing the IOP cards.

The card location is not available for use. The Failing Item with the card slot error is in the Failing Item list for this reference code.

See the SLOTERR symbolic FRU for the list of messages and a further description of the problem detected by Licensed Internal Code.

For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed.

If the Service Action Log, or serviceable event view on the HMC is available then use the failing item list presented there for servicing this reference code.

If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.

Power control failure, do not use slot.

The card location is not available for use. The Failing Item with the card slot error is in the Failing Item list for this reference code.

See the SLOTERR symbolic FRU for the list of messages and a further description of the problem detected by Licensed Internal Code.

For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event viewer you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed.

If the Service Action Log or serviceable event viewer on the HMC is available then use the failing item list presented there for servicing this reference code.

If serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.

One of several errors or configuration problems has occurred under a Multi-adapter bridge. If you are using the Service Action Log (SAL), or the serviceable event viewer on the HMC or the service processor, then the correct FRU, description and card position(s) will be listed. Use the FRUs and descriptions in the serviceable event view you are working with to determine the problem.

If you do not have access to the Service Action Log, or serviceable event view on the HMC or service processor, then word 4 of the SRC has more information. Examine the last 4 digits in word 4 to determine the problem by comparing them to the list below and using the FRU(s) listed here.
1.        xxxx2022 - IOP found in slots owned by a Linux partition. The Mutli-adapter Bridge and PCI Bridge set that it controls are assigned to a Linux partition. The IOP found in the SLOT indicated by the DSA in word 7 will not be configured.
2.        xxxx2014 - I/O adapters were found under the Multi-adapter Bridge but there is no IOP to support them. The adapters cannot be used.
3.        xxxx2015 - An card type was found that cannot be supported in the card position where it is located.

See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.

Card type not supported in this slot.

An I/O processor or I/O adapter card type is installed in the location indicated in word 7 of the SRC. The card type is not supported in that slot under the Multi-adapter bridge. The card is unavailable.

See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.

I/O processor removed from multi-adapter bridge card slot.

On the previous IPL an I/O processor was in the card location specified in word 7 of the SRC. The I/O processor was not detected on this IPL.

See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.

I/O adapter unavailable due to moved I/O processor card.

The I/O adapter specified in word 7 of the SRC is not available. On the previous IPL there was an I/O processor card the adapter was assigned to. The I/O processor was not detected on this IPL.

See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.

IOA removed from multi-adapter bridge slot.

On the previous IPL an I/O adapter was in the card slot specified in word 7 of the SRC. That I/O adapter was not detected on this IPL.

See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.

I/O adapter replaced by I/O processor card.

On the previous IPL there was an I/O adapter in the location specified in word 7 of the SRC. This IPL LIC detected that the IOA was replaced by an IOP in that location.

See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.

Perform LICIP14.

This can be caused by "PCI error injection policy" being set to "YES" and an I/O Processor being installed on the same Multi-adapter bridge domain as the I/O Adapter. Do one of the following:

-- Using the HMC or a customer PC with a Web browser access the Advanced System Management Interface (ASMI) and disable PCI error injection policy.

OR

-- Vary off the I/O Adapter. Using Hardware Service manager in SST/DST, locate the I/O Adapter resource. Using concurrent maintenance on the associated packaging resource, remove the I/O Adapter and install it in a location that does not have I/O Processors on the same Multi-adapter bridge domain.

OR

-- Vary off the I/O Adapter. Use the concurrent maintenance option in Hardware Service Manager in SST/DST to power off all I/O Processors located on the same Multi-adapter bridge domain as the I/O Adapter. Use concurrent maintenance to power off and power on the I/O Adapter. Then use concurrent maintenance to power on the I/O Processors located on the same Multi-adapter bridge domain as the I/O Adapter.

A system PCI bus failure was detected. Word 7 of the SRC contains the bus number.

This failure can occur when a tower in an HSL loop is powered off using concurrent maintenance. If this is the case, close this problem.

This error is most likely in the hardware that makes up the PCI bus, the PCI bus side of the HSL I/O bridge or the multi-adapter bridge. In some cases it may be caused by a failing IOP in the multi-adapter bridge's domain. When an IOP is causing the problem, the failing IOP cannot be identified.

NOTE: This SRC can occur for the PCI bus resource on a PCI bus in an I/O expansion unit when the unit is powered off for a concurrent maintenance action.

Exchange the failing items, one at a time, in the order they are listed in the serviceable event view or this document until you get to the BRDGSET or BRDGSTx symbolic FRU. If the problem still exists after exchanging the failing items up to, but not including, BRDGSET or BRDGSTx then perform MABIP03 to determine the failing I/O processor card.

For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed.

If the Service Action Log, or serviceable event view on the HMC or service processor, is available then use the failing item list presented there for servicing this reference code.

If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.

NOTE: A fiber optic cleaning kit may be required for optical HSL connections.

Failure in a multi-adapter bridge or on the bus to the card location it controls.

For this reference code the failing item list presented in the Service Action Log (SAL) or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed.

If the Service Action Log (SAL) or serviceable event viewer is available then use the failing item list presented there for servicing this reference code.

If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.

Perform MABIP02

Multi-adapter Bridge (MaB) failure detected.

For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event viewer you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed.

If the Service Action Log (SAL) or serviceable event viewer on the HMC is available then use the failing item list presented there for servicing this reference code.

If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.

Multi-adapter Bridge has detected a problem in the card installed in the location specified in word 7 of the SRC. Use the FRU list in the Service Action Log (SAL), or serviceable event view you are working with. If you are working from this document's FRU list use the Symbolic FRU BRDGSET to determine the failing items.

PCI I/O processor rejected the assignment of or the removal of an I/O adapter.

The direct select address in word 7 of the SRC specifies the location of the IOA. The direct select address of the IOP is in word 5 of the SRC.

See the DSA translation table and the Card positions table to determine the card locations for the IOA and the IOP.

Use slot concurrent maintenance under HSM to assign or remove the IOA.

Service processor error.

For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed.

If the Service Action Log (SAL) or a serviceable event viewer on the HMC is available then use the failing item list presented there for servicing this reference code.

If a serviceable event viewer is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.

The FRU list displayed in the Service Action Log (SAL) or serviceable event view you are working with, may vary from the failing item list given in this document. Use the FRU list in the serviceable event view if it is available to you.

NOTE: A fiber optic cleaning kit may be required for optical HSL connections.

Cycle power on the frame identified as the frame with failed HSL I/O Bridge prior to replacing FRUs.

The FRU list displayed in the Service Action Log (SAL), or serviceable event view you are using, may vary from the failing item list given in this document. Use the FRU list in the serviceable event view if it is available to you.

If you find either a B600 6982 or B600 6984 SRC logged at approximately the same time as this SRC then they were caused by the same failure. If you find a 6982 SRC logged at approximately the same time then close this problem and service the 6982 SRC. The failing item listed for this SRC is one of the failing items listed for B600 6982. If the serviceable event view's entry for this SRC has a location listed then record the location for use in servicing the 6982 SRC.

NOTE: This SRC can occur for the HSL I/O Bridge resource in an I/O expansion unit when the unit is powered off for a concurrent maintenance action.

NOTE: A fiber optic cleaning kit may be required for optical HSL connections.

If this SRC is not in the Service Action Log (SAL), or serviceable event view you are using, then it is informational and/or statistical only. It does not require a service action.

Otherwise: This is a connection failure on an HSL link. Perform RIOIP09 to determine the service action.

An HSL loop has an invalid configuration. Word 4 of the SRC contains the program return code (PRC) which identifies the problem with the loop's configuration. Use the PRC and the FRU listed to determine the problem.

If you are using the Service Action Log (SAL) or serviceable event view you are working with, the FRU description may already indicate the configuration problem.

An HSL loop has switched to its alternate path. This is an informational SRC only.

Word 7 of the SRC contains the loop number in the leftmost 4 digits. The loop number is in hexadecimal format. You must convert the hexadecimal loop number into decimal format to recognize the loop number in HSM.

This SRC can be caused by a tower on the HSL loop powering off.

This SRC may also appear in the Service Action Log (SAL), or serviceable event viewer you are using, with a B600 6982 or B600 6981 logged at approximately the same time. In that case the other SRC is reporting a failure and this SRC is reporting that the alternate HSL path is now being used. Service the other SRC if present.

If this SRC is not in the Service Action Log (SAL), or serviceable event view you are using, then it is informational. Use FRU SIRSTAT to determine what this SRC means. Otherwise, continue with the following steps:

This error can appear as a serviceable event when a tower, or I/O unit or another system in the loop did not complete powering on before LIC on this system checked this loop for errors. Search the Product Activity Log (PAL) for the last B600 6985 SRC logged for this loop and use FRU SIRSTAT to determine if this error requires service. If the last entry indicates the loop is functioning (determined by FRU SIRSTAT) then no service action is required, close this problem

There may be multiple B600 6985 logs with xxxx 3205 in word 4 errors for the same loop resource in the serviceable event view. This is caused by retry and recovery attempts. If there is a B600 6985 with xxxx 3206 or xxxx 3208 in word 4 after the above B600 6985 entries in the PAL, then the recovery efforts were successful. If this is the case, close all the B600 6985 entries for that loop resource in the serviceable event view.
1.        If you find a B600 6981 in the serviceable event view then close that problem and go to step 2. Otherwise perform the following:

• Perform RIOIP06 to determine if any other systems are connected to this loop and return here. (HSL_LNK or HSLxxxx FRU in the Service Action Log (SAL) entry, or serviceable event view you are working with, indicates the loop number.) If there are other system(s) then continue with the steps that follow, otherwise go to step 2.
• Check for HSL failures on the other system(s) before replacing parts. HSL failures are serviceable event entries with HSL I/O Bridge and Network Interface Controller (NIC) resources. Ignore B600 6982 and B600 6984 entries. If there are HSL failures on other system(s) then continue with the steps that follow, otherwise go to step 2.
• Repair the problems on the other systems and return to this step. After making repairs on the other system(s) check the Product Activity Log (PAL) of this system for a B600 6985 logged after the repairs you made on the other system(s). If you find one then continue with the steps that follow, otherwise go to step 2.
• For the B600 6985 log you found, use FRU SIRSTAT to determine if the loop is now complete. If the loop is complete then this problem has been resolved. Use RIOIP01 to verify that the loop is now working properly. Otherwise, go to step 2.

If this SRC appears in the Service Action Log (SAL), or the serviceable event view you are using, with the Symbolic FRU HSL_LNK or HSLxxxx listed as a FRU, then perform problem isolation procedure RIOIP01. Otherwise exchange the FRUs listed in the serviceable event view.

NOTE: A fiber optic cleaning kit may be required for optical HSL connections.

During IPL, system LIC detected an HSL I/O bridge that was already initialized. The bridge should have been in a flushed and unintialized state after powering on. There is a problem with SPCN components that prevented the tower from powering off after a previous power off was issued. The tower will not be configured for this IPL.

This reference code is equivalent to 1xxx 90F0. When referring to the "CBLALL" symbolic FRU in the Failing Item list, perform the "CBLALL" procedure using reference code "90F0".

Word 5 of the SRC identifies the frame. Determine the frame by breaking down word 5:

Word 5 -> xxxx xxNN where: NN is the frame number in hexadecimal format.

Failures are occurring on the HSL link.

There may be B600 6982 errors logged on the same loop and about the same time as this error. Close those errors and continue to correct the problem by working this error.

• If there is a cable FRU in the serviceable event entry:

• If there was no cable in the Service Action Log (SAL), or serviceable event view you are using, then replace the FRUs listed in the serviceable event view.

A failure occurred with the service processor hardware or the service processor LIC.

The FRU list displayed in the Service Action Log (SAL), or serviceable event view you are working with, may vary from the failing item list given in this document. Use the FRU list in the serviceable event view if it is available to you.

The FRU list displayed in the Service Action Log (SAL) or serviceable event view you are working with, may vary from the failing item list given in this document. Use the FRU list in the serviceable event view if it is available to you.

This reference code is for information only. It indicates the presence of a wrap plug on the local optical link card.

This reference code is for information only and might include the following:

• Optical speed encode
• Broken optical links now operational
• Other information

This reference code is informational only.

HSL OptiConnect has established connection normally. The local system or partition is participating in HSL Opticonnect with other systems or partitions on the same HSL loop.

This reference code is informational only.

HSL Opticonnect disconnected normally from a remote node. The local system or partition has stopped participating in HSL Opticonnect with the remote system or partition on the same HSL loop. Possible reasons include:

• A remote system or partition went off line due to a normal power off or disable of HSL Opticonnect.

The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. The problem is most likely with the remote system or partition. Intervention at the remote system is most likely required. Examine both the local and remote HSL OptiConnected systems or partitions for problems on this HSL loop.

Possible reasons include: A fatal error in software or hardware in the remote system or partition or a power failure in the remote system.

If there was not a complete HSL loop before this error occurred then a failure or power down in an HSL component between the local system or partition and the remote system or partition could have caused this error. Check for a problem with: an HSL cable, HSL I/O bridge or a power problem in an expansion I/O tower or unit on this loop.

Examine the Service Action Log (SAL), or serviceable event view you are using on the local system or partition for HSL failures on the same HSL loop at approximately the same time this error occurred.

Examine the remote system or partition for problems. If the remote system or partition is powered on and IPL'd then examine the Service Action Log (SAL), or serviceable event view you are using, on the remote system or partition for problems on the same HSL loop at approximately the same time this error occurred.

Correct any problems you find with the remote and local systems or partitions that happened at approximately the same time and involve HSL Opticonnect or HSL loop components or Network Interface Controllers. When the remote system is IPL'd it will automatically reconnect with this system or partition.

If there are no problems with the remote system or partition and there are no problems with the local system or partition then collect all the Product Activity Log information for this failure on both systems. Be sure to record all words in the SRC. Contact your next level of support.

The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. LIC will attempt to recover from the error. Intervention at the local or remote system or partition may be required.

Possible causes are: time out, hang or hardware failure. The problem may be with: the local system or partition or the remote system or partition.

If there was not a complete HSL loop before this error then a failure or power down in an HSL component between the local system or partition and the remote system or partition could have caused this error. Check for SRCs with FRUs like: HSL cables, HSL I/O bridge or a power problem in an expansion I/O tower or unit on this loop.

Examine the SAL or serviceable event view you are working with on the local system or partition for failures on the same loop, or with the Network Interface Controller at approximately the same time.

Examine the remote system or partition for problems. Correct any HSL or NIC problems you find with the remote and local systems or partitions.

If there are no problems with the remote system or partition and there are no problems with the local system or partition then collect all the Product Activity Log (PAL) information for this failure on both systems. Be sure to record all words in the SRC. Contact your next level of support.

The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. All of the HSL OptiConnect connections on this loop will be in a failed state. LIC will attempt to recover from the error. Intervention at the local or remote system or partition may be required. Possible causes are:

• time out of a critical message
• LIC code / table problem
• Network deadlock detected

• The local system or partition
• The remote system or partition

Examine the remote system or partition for problems. Examine the Service Action Log (SAL), or serviceable event view you are using, on the remote system or partition for problems on the same HSL loop or with the Network Interface Controller at approximately the same time this error occurred.

Correct any problems you find with the remote and local systems or partitions that happened at approximately the same time and involve HSL Opticonnect or HSL loop components or Network Interface Controllers.

If there are no problems with the remote system or partition and there are no problems with the local system or partition then collect all the Product Activity Log information for this failure on all systems or partitions. Be sure to record all words in the SRCs. Contact your next level of support.

The local system or partition disconnected from a remote system or partition due to an failure in a LIC virtualized bus unit. LIC will attempt to recover from the error. Possible causes are:

• LIC problem where the local bus unit is off line.
• LIC problem where the remote bus unit is off line.

Examine the remote system or partition for problems. Examine the Service Action Log (SAL), or the serviceable event view you are using, on the remote system or partition for HSL Opticonnect problems that occurred at approximately the same time this error occurred.

Collect all the Product Activity Log information for this failure on all systems and partitions on this HSL loop. Be sure to record all words in the SRCs. Contact your next level of support with the information you have collected.

LIC internal error. All systems participating in HSL OptiConnect will be disconnected. The system must be re-IPL'd to recover. Before re-IPL'ing the system initiate a main store dump.

After getting the dump, examine the Service Action Log (SAL), or serviceable event view you are using, on the local system or partition for HSL Opticonnect failures that occurred at approximately the same time this error occurred.

Examine the remote systems or partitions for problems. Examine the Service Action Log (SAL), or serviceable event view you are using, on the remote systems or partitions for HSL Opticonnect problems that occurred at approximately the same time this error occurred.

Collect all the Product Activity Log information for this failure on all systems and partitions on this HSL loop. Be sure to record all words in the SRCs. Contact your next level of support with the information you have collected.

Firmware detected a hardware failure in the Host Ethernet Adapter (HEA).

A Licensed Internal Code error occurred. The partition will continue to run with this Host Ethernet Adapter (HEA) disabled. Perform a partition dump and then IPL the partition to recover the HEA. Send the partition dump to your next level of support.

The Host Ethernet Adapter (HEA) is not connected to the Ethernet switch. If the HEA connection is not needed, no service action is required.

If the HEA connection is needed, verify that the cable is connected and the switch is powered on. After repairing the problem, verify that the connection has been restored.

System log entry only, no service action required.

Firmware detected a failure in the HEA Media Interface Adapter.

Contact your next level of support.

This reference code is logged when the TCP/IP Attribute "Log Protocol Errors" is set, and the TCP/IP System LIC "silently discards" an inbound datagram. "Silently discard" is defined to mean discard the received datagram without reporting an error to the originating host device. Examples of such datagrams are those with checksums or destination addresses which are not valid.

This reference code is for information only. Normally no action should be taken as a result of this reference code. It is generated in order to assist with remote device or TCP/IP network problem determination.

This reference code is logged for information only.

This reference code is used to indicate that LIC timed out on a request to initiate a session.

The user must run problem analysis for this reference code. If this indicates a software problem, the user should dial IBM Software Support for assistance.

The Problem Determination Procedure (PDP) will indicate whether the original timeout condition still exists and what the corrective actions should be.

This reference code is used to indicate that LIC attempted to satisfy a session initiation request, but some failure condition was detected by LIC. The failure condition could be a configuration or operational problem in the network.

The user must run problem analysis for this reference code. If this indicates a software problem, the user should dial IBM Software Support for assistance.

The Problem Determination Procedure (PDP) will indicate whether the original timeout condition still exists and what the corrective actions should be.

This reference code is for information only. The Uninterruptible Power System (UPS) is reporting a utility failure.

This reference code is for information only. The Uninterruptible Power System (UPS) is reporting that utility power has been restored.

This reference code is for information only. The Uninterruptible Power System (UPS) is reporting a battery low condition.

This reference code is for information only. The Uninterruptible Power System (UPS) is reporting a bypass is active.

This reference code is for information only. The Uninterruptible Power System (UPS) is no longer reporting a battery low condition.

This reference code is for information only. The Uninterruptible Power System (UPS) is no longer reporting a bypass active condition.

The replacement period for BPU 1, installed in the System Unit, has been exceeded.

The replacement period for BPU 2, installed in the System Unit, has been exceeded.

The replacement period for BPU 1, installed in the Expansion Unit, has been exceeded.

The replacement dates for one of the Battery Power Units do not match. Run "Display Hardware Configuration" and verify that the dates match the labels on the batteries.

Storage Management detected a DASD datacheck condition and the defective sector was reallocated.

Perform a system IPL to restart the system.

A hardware resource is missing. The resource reported in to the system on a previous IPL, but has not reported in on the current IPL. This could occur for several different reasons.
1.        It could be a normal situation where the resource is currently powered off. In this case, when the resource is powered back on, it will no longer be missing.
2.        The hardware resource could also be missing if it has been removed from the system, for example, a tape drive that was replaced with a different tape drive. The service representative should use the Hardware service manager to remove the entry for this resource.
3.        The resource may not have reported in on this IPL because it is failing. Perform problem analysis to determine why the resource is failing.

Look for other errors in the Service Action Log (SAL), or serviceable event view you are working with, and fix them.

Look for other errors in the Service Action Log, or serviceable event view you are working with, and fix them.

An attempt to activate a connection from another I/O adapter to an external storage subsystem disk unit failed because the maximum number of connections are already active for this disk unit. No action required.

No action required.

Could not read configuration information from the disk unit. Look for other errors in the Service Action Log, or serviceable event view you are working with, and fix them.

A high performance connection to an external storage subsystem disk unit failed.

There are still two or more external storage subsystem disk unit connections, but performance might be degraded.

Look for other errors in the Service Action Log, or serviceable event view you are working with, and fix them.

A high performance connection to an external storage subsystem disk unit failed.

There is still one more external storage subsystem disk unit connection, but performance might be degraded.

Look for other errors in the Service Action Log, or serviceable event view you are working with, and fix them.

A high performance connection to an external storage subsystem disk unit was restored.

Performance is no longer degraded.

No action required.

A type D IPL terminated because of an optical load source device failure. If the optical load source is an external optical device, check the cables. If that does not correct the problem, replace the optical device. If the optical load source is an internal optical device, replace the optical device. If the optical load source is a virtual device, ensure it is set up correctly.

The optical disk drive addressing within the optical library is incorrect. This error is likely to be the result of faulty cabling or switch setting following service to an optical library.

Contact your hardware service provider.

Perform LICIP01.

The hypervisor terminated a partition with an unresponsive Operating System. A Main Store Dump must be done for service. Call your next level of support when the dump is complete.

Perform LICIP01.

This reference code is logged for information only. No action required.

This reference code indicates first failure data capture (FFDC) data was collected for a problem reported by licensed internal code.

The user should dial IBM Software Support for assistance.