System reference codes (SRCs) for logical partitions

Cause: The secondary partition could not perform the IPL. The IPL is ended. An example of what causes this SRC to appear is not assigning the correct amount of processors or memory to a secondary partition.

Recovery: From the Work With System Partitions display, correct the configuration problem based on the reason code, then try the secondary partition's IPL again. If it continues to fail, contact your service provider.

Problem analysis procedure: Identify the reason code from word 3 of the SRC. Possible reason code values are the following:

• 000000A2: Insufficient amount of interactive performance
• 000000A3: Insufficient number of processors
• 000000A4: Insufficient main storage size

For any other reason code, contact your service provider.

Cause: The primary partition's IPL mode does not allow the secondary partition to IPL the given mode. The IPL is ended. An example of what causes this SRC to appear is the primary partition is in C-mode IPL and the secondary partition is B-mode IPL. When the primary partition is in a D-mode IPL, the secondary partitions are not allowed to IPL at all.

Recovery: Go to the Work With System Partitions display and assign the secondary partitions the same IPL mode as the primary partition. Then, try the secondary partition IPL again. If the problem continues to fail, contact your service provider.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) entry for this problem.

Cause: The Timed Power On (TPO) setting was reached for a secondary partition, but the keylock was not set to Automatic or Normal. The IPL will end.

Recovery: Go to the Work With System Partitions display and change the keylock from its current setting of Manual-Secure to Normal- Automatic. Then, try the secondary partition IPL again. If the problem continues to fail, contact your service provider.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) entry for this problem.

Cause: No alternate (D-mode) IPL device IOP selected. The IPL will attempt to continue, but there might not be enough information to find the correct D-mode load source.

Recovery: Go to the Work With System Partitions display and configure an alternate IPL IOP for the secondary partition. Then, try the secondary partition IPL again. If it continues to fail, contact your service provider.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) for this problem for your service provider.

Cause: No default load source IOP selected for an A-mode or a B-mode IPL. The IPL will attempt to continue, but there might not be enough information to find the correct load source.

Recovery: Go to the Work With System Partitions display and configure a load source IOP for the secondary partition. Then, try the secondary partition IPL again. If it continues to fail, contact your service provider.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) for this problem for your service provider.

Cause: All load source candidates have been scanned for valid secondary partition code. However, in all cases, errors were encountered that prevented each from being used as a load source candidate for the IPL. The IPL is ended.

Recovery: Address each problem found, and then try the secondary partition's IPL again. If it continues to fail, contact your service provider.

Problem analysis procedure: Scan the secondary partition's SRC history list for prior B2ppxxxx failure SRCs (where pp is the partition ID) to pinpoint the source of the problem.

Cause: The IOA slot does not belong to the IOP. A check is made to the specific IOP to ensure an IOA slot has been assigned to it. This SRC indicates that no IOA slot has been assigned to an IOP, and hence all unit addresses under this slot will not be attempted. The IPL will attempt to continue by skipping to the next slot address.

Recovery: This SRC probably indicates a LPAR configuration error. Use the Work with Partitions display to check your partition configuration to ensure that all the slots are allocated to the partition correctly.

Problem analysis procedure: Use the product activity log (PAL) to find SRCs that pertain to the device address referenced in words 13-16 of the SRC. Correct any problems found, and then retry the secondary IPL.

Cause: Memory allocation for early IPL objects failed. The primary is low on memory. The IPL sequence will be retried to the same device.

Recovery: If the primary partition does not have enough main storage, remove some main storage from one or more secondary partitions, then add it to the primary partition. If the primary partition does have enough main storage, try the IPL again. If it continues to fail, contact your service provider.

Problem analysis procedure: Ensure that the primary partition has an adequate amount of main storage available to perform the IPL of the secondary partition.

Cause: No bus object was found for the specified bus number. The IPL will attempt to continue, but all subsequent load source devices at this bus address will be skipped.

Recovery: If word 3 is zero, then is SRC is informational and can be ignored. A nonzero bus number has no associated bus object. Contact your service provider to resolve the issue.

Problem analysis procedure: The value for word 3 is as follows:

• Word 3: Bus address information

This value can help you to identify the hardware that caused the error.

Cause: The Transport Manager bus object type is neither SPD nor PCI. The only known bus types are RIO, SAN, and Virtual and none of these support the IPL mode as an LPAR load source. The entire bus will be skipped. The IPL will attempt to continue.

Recovery: Contact your service provider to resolve the issue.

Problem analysis procedure: The value for word 3 is as follows:

• Word 3: Bus address information

This value can help you to identify the hardware that caused the error.

Cause: The command (Initiate Self Load) sent to the IOP telling it to locate the selected load source device and load or reset itself has failed. The IPL will attempt to continue, and depending on the type of failure, the load source device can be retried or skipped.

Recovery: Look for SRCs in the PAL relating to the device location specified in words 3-6. Follow the recovery actions for problems found. Then, try the secondary partition IPL again. If it continues to fail, contact your service provider.

Problem analysis procedure: The values for words 3-6 are as follows:

• Word 3: Bus address information
• Word 4: Board address information
• Word 5: Card address information
• Word 6: Unit address information

These values can help you to identify the hardware that caused the error.

Cause: The load source device hardware drive has no HRI object. The IPL will attempt to try the entire IPL sequence from the specified load source again.

Recovery: If your IPL failed due to this SRC, capture a primary partition MSD and contact your service provider.

Problem analysis procedure: The value for word 3 is as follows:

• Word 3: Bus address information
• Word 4: Board address information
• Word 5: Card address information
• Word 6: Unit address information

This value can help you to identify the hardware that caused the error.

Cause: A mismatch has occurred between the expected load source candidate device's logical device location and the enlisted load source candidate device. The IPL will attempt to try the entire IPL sequence from the specified load source again.

Recovery: If your IPL failed due to this SRC, capture a primary partition MSD and contact your service provider.

Problem analysis procedure: The value for word 3 is as follows:

• Word 3: Bus address information
• Word 4: Board address information
• Word 5: Card address information
• Word 6: Unit address information

This value can help you to identify the hardware that caused the error.

Cause: A failure occurred when attempting to allocate storage in the primary partition.

Recovery: If the primary partition does not have enough main storage, remove some main storage from one or more secondary partitions, then add it to the primary partition.

Problem analysis procedure: Ensure the primary partition has an adequate amount of memory. Try the secondary partition IPL again.

Cause: The wrong kind of primary load source reported. The IPL will attempt to proceed by skipping all subsequent attempts to this device.

Recovery: Verify your hardware configuration for the secondary partition.

Problem analysis procedure: Ensure that the devices are located in the correct location.

Cause: The wrong kind of alternate load source reported. The IPL will attempt to continue by skipping all subsequent attempts to this device.

Recovery: Verify your hardware configuration for the secondary partition.

Problem analysis procedure: Ensure that the devices are located in the correct slot.

Cause: Creation of main storage dump-temporary segment has failed. An example of what causes this failure is running out of memory in the primary partition. The IPL will be retried to the same device unit address, under the assumption that this is a temporary condition.

Recovery: If the primary partition does not have enough main storage, remove some main storage from one or more secondary partitions, then add it to the primary partition. If the primary partition does have enough main storage, try the IPL again. If it continues to fail, contact your service provider.

Problem analysis procedure: Ensure that the primary partition has an adequate amount of main storage available to perform the IPL of the secondary partitions.

Cause: The secondary load source has allocated a MSD that is smaller than the minimum dump size. No dump can be captured. The IPL will end.

Recovery: Contact your service provider.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) entry for this problem. Contact your service provider.

Cause: Loading form the load source has failed. The IPL will attempt to continue by trying the entire IPL sequence to the same load source device again.

Recovery: If this SRC is preventing the secondary IPL from continuing, focus on the load source device at the location specified in words 3-6. Try the secondary partition's IPL again, after fixing any problems found.

Problem analysis procedure: These values for words 3-6 is as follows:

• Word 3: Bus information
• Word 4: Board information
• Word 5: Card information
• Word 6: Unit information

These values can help you to identify the hardware that caused the error.

Collect the detailed hexadecimal data from the product activity log (PAL) for this problem for your service provider.

Cause: An MSD or CPM IPL has occurred, but the current information cannot be written to the load source device because a valid dump already exists. The current MSD or CPM information is lost, and the IPL is ended.

Recovery: Perform the IPL of the secondary partition past dedicated service tools (DST) to invalidate the old MSD or CPM information on the load source. Then, subsequent MSD or CPM dumps can be saved.

Problem analysis procedure: Identify the partition that has the problem through the partition identification number (xx) given in the SRC.

Cause: An MSD or CPM IPL has occurred, but the current information cannot be written to the load source device because a valid dump already exists. The current MSD or CPM information is lost, and the IPL is ended.

Recovery: Perform the IPL of the secondary partition past dedicated service tools (DST) to invalidate the old MSD or CPM information on the load source. Then, subsequent MSD or CPM dumps can be saved.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) and fix any problems found.

Cause: A disk unit write operation has failed during the writing of MSD or CPM mainstore pages. A partial dump of phase II information might be available in the dump and the MSD or CPM IPL will continue.

Recovery: Collect the detailed hexadecimal data from the product activity log (PAL) associated with the disk unit at the given location. Fix any potential problems found. This can be a sign of a disk unit, IOP, or Bus problem that needs to be fixed.

Problem analysis procedure: Identify the reason code from words 3-9 of the SRC. Possible reason code values are the following:

• Word 3: bus address information
• Word 4: Board address information
• Word 5: Card address information
• Word 6: Unit address information
• Word 7: Number of pages written in the operation
• Word 8: Device page position
• Word 9: DASD hardware driver return code

For any other reason code, contact your service provider.

Cause: Storing SID 82 LIDs during Phase II for the MSD or CPM path has failed. Phase II information will most likely not be available in the dump and the MSD or CPM IPL will continue.

Recovery: Collect the detailed hexadecimal data from the product activity log (PAL) associated with the disk unit at the given location. Fix any potential problems found. This can be a sign of a disk unit, IOP, or Bus problem that needs to be fixed.

Problem analysis procedure: Identify the reason code from words 3-6 of the SRC. Possible reason code values are the following:

• Word 3: bus address information
• Word 4: Board address information
• Word 5: Card address information
• Word 6: Unit address information

For any other reason code, contact your service provider.

Cause: A MSD occurred while the system was already performing a MSD or CPM recovery IPL. The first dump has already been copied or cleared. The second dump has been successfully saved into the secondary load source's SID 82, but he secondary partition will not IPL.

Recovery: Contact your service provider.

Problem analysis procedure: Identify the reason code from words 3-6 of the SRC. Possible reason code values are the following:

• Word 3: bus address information
• Word 4: Board address information
• Word 5: Card address information
• Word 6: Unit address information

For any other reason code, contact your service provider.

Cause: A secondary partition LID has been loaded into the partition's main storage successfully. However, it has been determined afterward that the actual LID was not fully contained in the partition's load area, and memory damage or corruption has potentially occurred. The IPL will be terminated.

Recovery: Contact your service provider. The secondary partition's load source device is corrupt. A reinstall might be necessary if the load source is DASD.

Problem analysis procedure: Identify the reason code from words 3-6 of the SRC. Possible reason code values are the following:

• Word 3: bus address information
• Word 4: Board address information
• Word 5: Card address information
• Word 6: Unit address information

For any other reason code, contact your service provider.

Cause: Getting the partition's load data area failed. The IPL will attempt to continue by skipping this device, and trying a subsequent load source candidate device.

Recovery: This is likely a problem with the load source media being corrupt or not valid. A re-installation of the Licensed Internal Code of the secondary partition is probably required to recover. If it continues to fail, contact your service provider.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) for this problem for your service provider.

Cause: Invalid memory for loading into the load ID. The IPL will attempt to continue by skipping this load source device candidate and trying the next candidate.

Recovery: This is likely a problem with the load source media being corrupt or invalid. A re-installation of the Licensed Internal Code of the secondary partition is probably required to recover. If it continues to fail, contact your service provider.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) for this problem for your service provider.

Cause: A low memory condition in the primary partition is the most likely cause of this SRC. The entire IPL sequence to the same unit address will be retried.

Recovery: If the primary partition does not have enough main storage, remove some main storage from one or more secondary partitions, then add it to the primary partition. If the primary partition does have enough main storage and there are no memory leaks, try the operation again.

Problem analysis procedure: Ensure that the partition was allocated enough main storage, verify that no memory leaks are present, and then try the operation again.

Cause: The secondary load source does not have an associated IOP hardware driver.

Recovery: Capture a primary partition MSD. Contact your service provider to resolve the issue.

Problem analysis procedure: Contact your service provider to resolve the issue.

Cause: Removing an IOP hardware driver (not the load source for the current IPL) from the primary partition failed. The IPL will continue, but the secondary partition will most likely not be able to establish connections to this IOP.

Recovery: You might need to perform another IPL of the secondary partition to recover the specified IOP for use by the secondary partition. If it continues to fail, contact your service provider.

Problem analysis procedure: Identify the values for words 3-5 to determine the cause of the error. The values for the words are as follows:

• Word 3: Bus address information
• Word 4: Board address information
• Word 5: Card address information

Cause: Removing the IOP hardware driver that is associated with the current load source has failed. The IPL will not proceed.

Recovery: Collect the detailed hexadecimal data from the product activity log (PAL) related to the specified IOP address. Fix any problems found by following the recovery actions for the PAL SRCs. Try the secondary partition IPL again. An IPL of the primary partition might be required to regain control of the IOP.

Problem analysis procedure: Identify the reason code from words 3-6 of the SRC. Possible reason code values are the following:

• Word 3: bus address information
• Word 4: Board address information
• Word 5: Card address information
• Word 6: IOP return code

For any other reason code, contact your service provider.

Cause: An error condition was encountered when attempting to send the exit VSP mode command (PCI-only bus command) to the load source IOP.

Recovery: Collect the detailed hexadecimal data from the product activity log (PAL) related to the specified IOP address. Fix any problems found by following the recovery actions for the PAL SRCs. Try the secondary partition IPL again. An IPL of the primary partition might be required to regain control of the IOP.

Problem analysis procedure: Identify the reason code from words 3-5 of the SRC. Possible reason code values are the following:

• Word 3: bus address information
• Word 4: Board address information
• Word 5: Card address information

For any other reason code, contact your service provider.

Cause: Initialization of secondary partition main storage data structures failed. The IPL is ended.

Recovery: This is likely a problem with the load source media being corrupt or invalid. A re-installation of the Licensed Internal Code of the secondary partition is probably required to recover. If it continues to fail, contact your service provider.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) for this problem for your service provider.

Cause: Failed to allocate main storage for Licensed Internal Code event messages. This indicates that free main storage is low in the primary partition. The IPL is ended.

Recovery: If the primary partition does not have enough main storage, remove some main storage from one or more secondary partitions, then add it to the primary partition.

Problem analysis procedure: Ensure the primary partition has an adequate amount of main storage to IPL the secondary partition.

Cause: The opening Licensed Internal Code Session Manager connections failed for some or all of the connections. The IPL will continue, but some connections will not be functional.

Recovery: You might need to perform another IPL of the secondary partition to recover the Licensed Internal Code Session Manager connections. If it continues to fail, contact your service provider.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) for this problem for your service provider.

Cause: Logical partition configuration data has a consistency error. The server cannot find a working copy of the configuration data for the logical partition.

Recovery: Contact your service provider. The server will not continue its IPL past dedicated service tools (DST) until the problem is corrected.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) for this problem for your service provider.

Cause: Logical partition configuration data does not match the current server configuration. Possible causes include:

• A nonconfigured disk unit which was previously a load source for a logical partition.
• Load source configuration data does not match the logical partition for which it is being used.
• Load source configuration data does not match the server serial number for which it is being used.
• Load source configuration data is newer than the primary partition configuration data.

Recovery: Perform one of the following tasks:

• If the load source has been replaced inadvertently, return the original and restart the server.
• If the load source is for the primary partition, recover the logical partition configuration data.
• If the specified load source is for a secondary partition, accept the disk as a load source for that secondary partition.
• If the specified disk unit is not configured, clear the nonconfigured load source to use the new disk unit in the server.
• If a load source disk unit has been moved from a server that has logical partitions, but the current server should not have logical partitions, clear all partition configuration data. This will delete all secondary partitions.
• If the load source came from a partitioned server and was inadvertently used to perform a partition IPL, do not take any action. The initialize disk process during installation clears existing configuration data.

The logical partition will not continue its IPL past DST until the problem is corrected with one of the above actions.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) entry for this problem for your service provider.

Cause: Informational indication that the server detected and corrected a configuration data inconsistency on a logical partition without any loss of data.

Recovery: None.

Problem analysis procedure: None unless a significant number of errors occur. Collect the detailed hexadecimal data from the product activity log (PAL) entries for these problems for your service provider.

Cause: The server detected a configuration data inconsistency for a logical partition and could not correct it without loss of the last configuration data update.

Recovery: Manually validate configuration data and repeat any missing configuration actions.

Problem analysis procedure: None unless a significant number of errors occur. Collect the detailed hexadecimal data from the product activity log (PAL) entries for these problems for your service provider.

Cause: An I/O Adapter used by a guest partition is located in a card position on the same Multi-adapter bridge domain as an I/O Processor. Guest partition data might be lost if any of the following occur:

• A primary partition Type D IPL is performed.
• The I/O Adapter is moved to an i5/OS™ partition.
• An error causes the Logical partition (LPAR) configuration data to not be used.

Recovery: Use the LPAR Validation Tool (LVT) to create a valid LPAR configuration. For more information about the LPAR Validation Tool, see the following Web site: http://www.ibm.com/eserver/iseries/lpar

Problem analysis procedure: Use the product activity log (PAL) to check the reason code from words 3-9 of the SRC. Use the reason code from words 3-9 to identify the location of the IOP and IOA. Possible reason code values are the following:

• Word 3: IOP partition ID
• Word 4: IOP Frame ID
• Word 5: IOP slot
• Word 6: IOA partition ID
• Word 7: IOA Frame ID
• Word 8: IOA slot
• Word 9: IOA Type number

For any other reason code, contact your service provider

Cause: A logical partition is running with less than the requested number of processors.

Recovery: Perform recovery for the processor-specific errors that are logged in the primary partition.

Problem analysis procedure: Check the product activity log (PAL) in the primary partition for SRCs that indicate hardware errors that should be corrected.

Cause: A logical partition is running with less than the requested amount of main storage.

Recovery: Perform recovery for the main storage-specific errors that are logged in the primary partition.

Problem analysis procedure: Check the product activity log (PAL) in the primary partition for SRCs that indicate hardware errors that should be corrected.

Cause: A logical partition has an insufficient number of processors. The logical partitions processor minimums could not be satisfied.

Recovery All resources have been temporarily assigned to the primary. Perform recovery for the processor specific errors that are logged in the primary partition.

Problem analysis procedure: Check the product activity log (PAL) for hardware errors.

Cause: A logical partition has an insufficient amount of memory. The logical partitions memory minimums could not be satisfied.

Recovery: All resources have been temporarily assigned to the primary. Perform recovery for the memory specific errors that are logged in the primary partition.

Problem analysis procedure: Check the product activity log (PAL) for hardware errors.

Cause: A logical partition has an insufficient amount of interactive performance. The logical partitions interactive performance minimums could not be satisfied.

Recovery: All resources have been temporarily assigned to the primary. Perform recovery for the interactive performance specific errors that are logged in the primary partition.

Problem analysis procedure: Check the product activity log (PAL) for hardware errors.

Cause: A logical partition software version is outside of the supported secondary partition release delta.

Recovery: Perform one of the following:

• Install a supported operating system version in the logical partition that has the problem.
• Install an operating system version in the primary partition that supports the version in the offending logical partition.

Problem analysis procedure: Display the logical partition release level and check the logical partition release delta.

Cause: An unexpected event occurred in the logical partition management code that was recovered.

Recovery: Contact your service provider if a significant number of these errors have occurred.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) entry for this problem.

Cause: An unexpected event occurred in the logical partition management code which could not be recovered. Further changes to the logical partition configuration might not be possible.

Recovery: If this error occurs on an installation or upgrade, the most likely resolution is to increase the minimum memory of the partition to which you are installing or upgrading. If increasing the minimum memory does not resolve the issue, contact your service provider. The server might not IPL past DST until the problem is corrected.

Problem analysis procedure: Collect the detailed hexadecimal data from the product activity log (PAL) entry for this problem.