LICIP11

Use this procedure to isolate a system STARTUP failure in the initial program load (IPL) mode.

Ensure you have read the danger notices in Licensed internal code (LIC) isolation procedures before continuing with this procedure.

How to find the cause code

  1. If the system has logical partitions, perform this procedure from the logical partition that reported the problem. To determine if the system has logical partitions, go to Determining if the system has logical partitions.
  2. Were you given a cause code by another procedure?
  3. Look at the Data display characters in word 3. You can obtain these characters by either:
  4. The 4 leftmost characters of word 3 represent the cause code. Select the cause code to go to the correct isolation instructions:
    0001 0010 0020 0031
    0002 0011 0021 0033
    0004 0012 0022 0034
    0005 0015 0023 0035
    0006 0016 0024 0037
    0007 0017 0025 0099
    0008 0018 0026
    0009 0019 0027
    000A 001A
    000B 001C
    000C 001D
    000D 001E
    000E 001F

0001

Disk configuration is missing.

  1. Select Manual mode and perform an IPL to DST for the failing partition (see Performing an IPL to DST). Does the Disk Configuration Error Report display appear?
  2. Is Missing Disk Configuration information displayed?
  3. On the Missing Disk Configuration display, perform the following:
    1. Select option 5 -> Display Detailed Report -> Work with disk units -> Work with disk unit recovery -> Recover Configuration.
    2. Follow the instructions on the display. After the disk configuration is recovered, the system automatically performs an IPL. This ends the procedure.

0002

Disk units are missing from the disk configuration.

Data from the control panel can be used to find information about the missing disk unit.

  1. Did you enter this procedure because all the devices listed on the Display Missing Units display (reached from the Disk Configuration Error Report, the Disk Configuration Attention Report, or the Disk Configuration Warning Report display) have a reference code of 0000?
  2. Have you installed a new disk enclosure in a disk unit and not restored the data to the disk unit?
  3. Use words 1-9 from the information recorded on the Problem summary form to determine the disk unit that is missing from the configuration:

    Are the problem disk units 432x, 433x, 660x, 671x, or 673x disk units?

  4. Attempt to get all devices attached to the MSIOP to Ready status by performing the following:
    1. The MSIOP address (MSIOP Direct Select Address) to use is characters 1-8 of the bottom 16 character line of function 12 (word 4).
    2. Verify the following and correct if necessary before continuing with step 10.
      • All cable connections are made correctly and are tight.
      • All storage devices have the correct signal bus address, as indicated in the system configuration list.
      • All storage devices are powered on and ready.
  5. Did you enter this procedure because there was an entry in the Service Action Log which has the reference code B6005090?
  6. Are customer jobs running on the system now?
  7. Select System Service Tools (SST) -> Work with disk units -> Display disk configuration -> Display disk configuration status.

    Are any disk units missing from the configuration (indicated by an asterisk *)?

  8. Do all of the disk units that are missing from the configuration have a status of "Suspended"?
  9. Use the Service Action Log to determine if there are any entries for the missing disk units (see Using the Service Action Log). Are there any entries in the Service Action Log for the missing disk units that were logged since the last IPL?
  10. Select Manual mode and perform an IPL to DST for the failing partition (see Performing an IPL to DST). Does the Disk Configuration Error Report, the Disk Configuration Attention Report, or the Disk Configuration Warning Report display appear?
  11. Does one of the following messages appear in the list?
  12. Select option 5. Do the missing units have device parity protected status? (Device parity protection status is indicated by "DPY/" as the first four characters of the status.)
  13. Is the status DPY/Active?
  14. Press F11, and press Enter to display the details.

    Do all of the disk units listed on the display have a reference code of 0000?

  15. Do all of the IOPs or devices listed on the display have a reference code of 0000?
  16. Does the following message appear in the list: Unknown load-source status?
  17. Select option 5, press F11, and then press Enter to display the details.

    Does the Assign Missing Load Source Disk display appear?

  18. Does the following message appear in the list?

    Load source failure

  19. Select option 5, press F11, and then press Enter to display the details.
  20. The number of failing disk unit facilities (actuators) is the number of disk units displayed. A disk unit has a Unit number greater than zero.

    Find the failing disk unit by type, model, serial number, or address displayed on the console.

  21. Is there more than one failing disk device attached to the IOA or MSIOP?
  22. Use the SAL to determine if there are any entries that occurred around the time of the A6xx/B6xx 5090 SRC (see Using the Service Action Log). Are there any such entries?
  23. Are all the disk devices that are attached to the IOA or MSIOP failing? (If the disk units are using mirrored protection, select Display Disk Status to find out.)
  24. Look up the SRC listed below for the specific disk unit and exchange the FRUs shown one at a time. Then return here and answer the question below the listed disk units.
    Disk Unit SRC to look up
    2105 21053002
    2107 21073002
    432x 432x3002
    433x 433x3002
    660x 660x3002
    671x 671x3002
    673x 673x3002

    Did the disk unit service information correct the problem?

  25. Exchange the IOA or MSIOP (see Locating FRUs).

    If exchanging the IOA or MSIOP did not correct the problem, use the original SRC and exchange the failing items, starting with the highest probable cause of failure. If the failing item list contains FI codes, Look up the FI code to help determine parts and locations. This ends the procedure.

0004

Some disk units are unprotected but configured into a mirrored ASP. These units were originally DPY protected but protection was disabled.

Perform the following:

  1. Is the system managed by an HMC?
  2. Select Work with disk units and take the actions to protect the system.

    If you do not know what actions to take, select Manual mode and perform an IPL to DST for the failing partition. See Performing an IPL to DST.

    When the Disk configuration error report appears, the recovery actions are listed in the Help text for the error message "Unprotected disk units in a mirrored ASP". This ends the procedure.

0005

A disk unit using parity protection is operating in exposed mode.

  1. Select Manual mode and perform an IPL to DST for the failing partition. See Performing an IPL to DST.
  2. Choose from the following options:

0006

There are new devices attached to the system that do not have Licensed Internal Code installed. Ask your next level of support for assistance.

0007

Some of the configured disk units have device parity protection disabled when the system expected device parity protection to be enabled.

  1. Is the system managed by an HMC?
  2. Correct the problem by doing the following:
    1. Select Work with disk units -> Work with disk unit recovery -> Correct device parity protection.
    2. Follow the online instructions. This ends the procedure.

0008

A disk unit has no more alternate sectors to assign.

  1. Determine the failing unit by type, model, serial number or address given in words 4-7. See The System Reference Code (SRC) Format Description.
  2. See the service information for the specific storage device. Use the disk unit reference code listed below for service information entry.
     
    432x 102E, 433x 102E, 660x 102E, 671x 102E, 673x 102E ( Look up a reference code.).

    This ends the procedure.

0009

The procedure to restore a disk unit from the tape unit did not complete. Continue with the disk unit exchange recovery procedure.

000A

There is a problem with a disk unit subsystem. As a result, there are missing disk units in the system.

Perform the following:

  1. Is the system managed by an HMC?
  2. On the Service Tools display, select Start a Service Tool -> Product activity log -> Analyze log.
  3. On the Select Subsystem Data display, select the option to view All Logs.
    Note:
    You can change the From: and To: Dates and Times from the 24-hour default if the time that the customer reported having the problem was more than 24 hours ago.
  4. Use the defaults on the Select Analysis Report Options display by pressing Enter.
  5. Search the entries on the Log Analysis Report display for system reference codes associated with the missing disk units.
  6. Go to Reference codes to correct the problem. This ends the procedure.

000B

Some system IOPs require cache storage be reclaimed.

  1. Is the system managed by an HMC?
  2. Reclaim the cache adapter card storage. See Reclaiming IOP cache storage.
    Note:
    The system operator may want to restore data from the most recent saved tape after you complete the repair.
    This ends the procedure.

000C

One of the mirror protected disk units has no more alternate sectors to assign.

  1. Determine the failing unit by type, model, serial number or address given in words 4-7. See System Reference Code (SRC) Information.
  2. See the service information for the specific storage device. Use the disk unit reference code listed below for service information entry.

    This ends the procedure.

000D

The system disk capacity has been exceeded.

For more information about disk capacity, see iSeries(TM) Handbook, GA19-5486-20.

000E

Start compression failure.

  1. Select Manual mode and perform an IPL to DST for the failing partition. See Performing an IPL to DST.
  2. Correct the problem by doing the following:
    1. Select Work with disk units -> Work with disk unit recovery -> Recover from start compression failure.
    2. Follow the on-line instructions. This ends the procedure.

0010

The disk configuration has changed.

The operating system must be installed again, and all customer data must be restored.

  1. Select Manual mode on the control panel.
  2. Perform an IPL to reinstall the operating system.
  3. The customer must restore all data from the latest system backup. This ends the procedure.

0011

The serial number of the control panel does not match the system serial number.

  1. Select Manual mode on the control panel.
  2. Perform an IPL. You will be prompted for the system serial number. This ends the procedure.

0012

The operation to write the vital product data (VPD) to the control panel failed.

Exchange the multiple function I/O processor card. See Locating FRUs for the model you are working on for the location of the card and a link to the remove and replace procedure.

0015

The mirrored load-source disk unit is missing from the disk configuration. Go to step 1 for cause code 0002.

0016

A mirrored protected disk unit is missing. Wait six minutes. If the same reference code appears, go to step 1 for cause code 0002.

0017

One or more disk units have a lower level of mirrored protection than originally configured.

  1. Select Manual mode and perform an IPL to DST for the failing partition. See Performing an IPL to DST.
  2. Review the detailed display, which shows the new and the previous levels of mirrored protection. This ends the procedure.

0018

Load-source configuration problem. The load-source disk unit is using mirrored protection and is configured at an incorrect address. Ensure that the load-source disk unit is in device location 1.

0019

One or more disk units were formatted incorrectly.

The system will continue to operate normally. However, it will not operate at optimum performance. To repair the problem, perform the following:

  1. Record the unit number and serial number of the disk unit that is formatted incorrectly.
  2. Sign on to DST. See Accessing Dedicated Service Tools.
  3. Select Work with disk units -> Work with disk unit configuration -> Remove unit from configuration.
  4. Select the disk unit you recorded earlier in this procedure.
  5. Confirm the option to remove data from the disk unit. This step may take a long time because the data must be moved to other disk units in the auxiliary storage pool (ASP).
  6. When the remove function is complete, select Add unit to configuration.
  7. Select the disk unit you recorded earlier in this procedure.
  8. Confirm the add. The disk unit is formatted during functional operation. This ends the procedure.

001A

The load-source disk unit data is down-level.

The load-source disk unit is mirror protected. The system is using the load-source disk unit that does not have the current level of data.

  1. Select Manual mode and perform an IPL to DST for the failing partition. See Performing an IPL to DST. Does the Disk Configuration Error Report display appear?
  2. Does a "Load source failure" message appear in the list?
  3. Select option 5, press F11, and then press Enter to display details.

    The load-source type, model, and serial number information that the system needs is displayed on the console.

    Is the load-source disk unit (displayed on the console) attached to an MSIOP that cannot be used for a load-source?

001C

The disk units that are needed to update the system configuration are missing.

Perform an IPL by doing the following:

  1. Select Manual mode on the control panel.
  2. Perform an IPL. Use the IPL information to determine the cause of the problem. This ends the procedure.

001D

  1. Is the Disk Configuration Attention Report, or the Disk Configuration Warning Report displayed?
  2. On the Bad Load Source Configuration message line, select 5, and press Enter to rebuild the load-source configuration information. If there are other types of warnings, select option 5 on the warnings, and correct the problem. This ends the procedure.

001E

The load-source data must be restored.

001F

Licensed Internal Code was installed on the wrong disk unit of the load-source mirrored pair.

The system performed an IPL on a load source that may not contain the same level of Licensed Internal Code that was installed on the other load source. The type, model, and address of the active device are displayed in words 4-7 of the SRC.

Choose from the following options:

  1. If the load-source disk unit in position 1 contains the correct level of Licensed Internal Code, perform the following:
    1. Select Manual mode and perform an IPL to DST for the failing partition. See Performing an IPL to DST. Is the Disk Configuration Attention Report or Disk Configuration Warning Report displayed?
      • Yes: Select option 5 on the Incorrect Licensed Internal Code Install message line. When the Display Incorrect Licensed Internal Code Install display appears on the console, press Enter.
      • No: The system is now using the correct load source. This ends the procedure.
  2. If the load-source disk unit in position 1 of the system unit does not contain the correct level of Licensed Internal Code, restore the Licensed Internal Code to the disk unit in position 1 of the system unit. This ends the procedure.

0020

The system appears to be a one disk unit system. Select Manual mode and perform an IPL to DST for the failing partition. See Performing an IPL to DST.

0021

The system password verification failed.

  1. Select Manual mode and perform an IPL to DST for the failing partition. See Performing an IPL to DST.
  2. When prompted, enter the correct system password. If the correct system password is not available perform the following:
    1. Select Bypass the system password.
    2. Have the customer contact the marketing representative immediately to order a new system password from your service provider. This ends the procedure.

0022

A different compression status was expected on a reporting disk unit. Accept the warning. The reported compression status will be used as the current compression status.

0023

There is a problem with a disk unit subsystem. As a result, there are missing disk units in the system. The system is capable of IPLing in this state.

  1. Is the system managed by an HMC?
  2. On the Service Tools display, select Start a Service Tool -> Product activity log -> Analyze log.
  3. On the Select Subsystem Data display, select the option to view All Logs.
    Note:
    You can change the From: and To: Dates and Times from the 24-hour default if the time that the customer reported having the problem was more than 24 hours ago.
  4. Use the defaults on the Select Analysis Report Options display by pressing Enter.
  5. Search the entries on the Log Analysis Report display for system reference codes associated with the missing disk units.
  6. Go to the Reference codes topic and use the SRC information to correct the problem. This ends the procedure.

0024

The system type or system unique ID needs to be entered.

  1. Select Manual mode and perform an IPL to DST for the failing partition. See Performing an IPL to DST.
  2. When prompted, enter the correct system type or system unique ID. This ends the procedure.

0025

Hardware Resource Information Persistence disabled.

  1. Select Manual mode and perform an IPL to DST for the failing partition. See Performing an IPL to DST.
  2. Contact your next level of support for instructions on how to enable the Hardware Resource Information Persistence function. This ends the procedure.

0026

A disk unit is incorrectly configured for an LPAR system.

  1. Select Manual mode and perform an IPL to DST for the failing partition. See Performing an IPL to DST.
  2. On the Service Tools display, select Start a Service Tool -> Product activity log -> Analyze log.
  3. On the Select Subsystem Data display, select the option to view All Logs.
    Note:
    You can change the From: and To: Dates and Times from the 24-hour default if the time that the customer reported having the problem was more than 24 hours ago.
  4. Use the defaults on the Select Analysis Report Options display by pressing Enter.
  5. Search the entries on the Log Analysis Report display for system reference codes (B6xx 53xx) that are associated with the error.
  6. Using the SRC information, look up the reference code. and use the information to correct the problem. This ends the procedure.

0027

The user ASP has overflowed. Contact your next level of support.

0031

A problem was detected with the installation of Licensed Internal Code service displays. The cause may be defective media, the installation media being removed too early, a device problem or a Licensed Internal Code problem.

0033

System model not supported. This model of hardware does not support the System Licensed Internal Code version and release that is being used. Use a supported version and release of the System Licensed Internal Code.

0034

Insufficient main storage capacity.

There is not enough main storage capacity. For details about how much more capacity is required, see the "Insufficient Main Storage Capacity" screen, which is displayed when the system is IPLed in manual mode. Typically, this error occurs when you have moved memory between logical partitions, and one partition no longer has a sufficient amount of main storage.

0035

Data from a User ASP has overflowed into the System ASP (ASP 1). There is not enough free space in the User ASP to move the overflowed data from the System ASP back into the User ASP. The system will continue to run in this condition, but if a disk failure in the System ASP causes the System ASP to be cleared, the data in the User ASP will also be cleared out.

You should delete some files or objects from the User ASP so that enough free space exists in the User ASP to allow the data that is overflowed into the System ASP to be moved back.

0037

One or more functional connections to a disk unit in a multi-path environment have not been detected. The connections to the disk unit were established by running ESS Specialist. If you use the server in this state, you may cause a loss of data. You must ensure that all of the functional connections are still established between the disk and the Input/Output Adapters (IOAs) attached to this server and this logical partition. If there is an IOA which has a connection to the disk unit that has been moved to a different logical partition or different server, you should not continue with the IPL. Notify your next level of support.

0099

A Licensed Internal Code program error occurred. Ask your next level of support for assistance.