LICIP12

Use this procedure to isolate an Independent Auxiliary Storage Pool (IASP) vary on failure.

Message CPDB8E0 occurred if the user attempted to vary on the IASP. Read the Danger notices in Licensed Internal Code isolation procedures before continuing with this procedure.
Parent topic: Licensed Internal Code isolation procedures

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 whether the system has logical partitions before continuing with this procedure.
  2. Were you given a cause code by another procedure?
    • No: Continue with the next step.
    • Yes: Use the cause code given by the other procedure. Then go to step 4.
  3. Look at the characters in word 3. You can obtain these characters by doing the following:
    1. On the command line, enter the Start System Service Tools (STRSST) command. If you cannot get to SST, use function 21 to get to DST. Do not IPL the system to get to DST.
    2. On the Start Service Tools Sign On display, type in a User ID with service authority and password.
    3. Select Start a Service Tool > Hardware Service Manager > Work with service action log.
    4. On the Select Timeframe display, change the From: Date and Time to a date and time prior to when the user attempted to vary on the IASP.
    5. Search for a B6005094 system reference code that occurred at the time the user attempted to vary on the IASP. Display the failing item information for this entry.
    6. Select the function key for Additional details.
    7. The 4 leftmost characters of word 3 is the cause code to be used in this procedure.
  4. Find the cause code below:

0002

Disk units are missing from the IASP disk configuration.
  1. Have you installed a new disk enclosure in a disk unit and not restored the data to the disk unit?
    • No: Continue with the next step.
    • Yes: Ignore SRC A600 5094.

      Continue with the disk unit exchange recovery procedure. This ends the procedure.

  2. Use words 1-9 from the information in the Service Action Log to determine the disk unit that is missing from the configuration:
    • Word 4 contains the IOP direct select address.
    • Word 5 contains the unit address.
    • Word 6 contains the disk unit type, level and model number.
    • Word 7 contains the disk unit serial number.
    • Word 8 contains the number of missing disk units.

    Are the problem disk units 432x, 660x, or 671x Disk Units?

    • Yes: Continue with the next step.
    • No: Attempt to get all devices attached to the IOP to Ready status by performing the following:
      1. The IOP address (IOP Direct Select Address) to use is Word 4.
      2. Verify the following, and correct if necessary:
        • Ensure all cable connections are made correctly and are tight.
        • Ensure the configuration within the device is correct.
        • Ensure all storage devices are powered on and ready.
      3. Continue with the next step.
  3. Perform the following steps:

    Select System Service Tools (SST) > Work with disk units > Display disk configuration > Display disk configuration status.

    Are any disk units missing-indicated with an asterisk (*)- from the IASP configuration?

    • Yes: Continue with the next step.
    • No: This ends the procedure.
  4. Use the Service Action Log to determine if there are any entries other than B6xx 5094 for the missing disk units or the IOA or IOP that is controlling them. See Using the product activity log.

    Are there any entries in the Service Action Log other than B6xx 5094 for the missing disk units or the IOA or IOP that is controlling them?

    • No: Continue with the next step.
    • Yes: Use the information in the Service Action Log to solve the problem. See Using the product activity log. This ends the procedure.
  5. Did you enter this procedure because there was a B6xx 5094 cause code of 0030?
    • No: Continue with the next step.
    • Yes: Work with the customer to recover the unknown configuration source disk unit.

      Use a workstation with System i® Navigator installed to select the disk pool with the problem, and then select Recover unknown configuration source for this disk pool. This ends the procedure.

  6. Use Hardware Service Manager to display logical resources connected to the IOP. See Hardware service manager.
  7. Is every device attached to the IOP failing?
    • Yes: Continue with the next step.
    • No: Are all of the disk units that are attached to one IOA missing?
      • No: Continue with the next step.
      • Yes: Exchange the IOA. Use the IOP direct select address and the first character of the unit address from step 2 to find the location. See Part locations and location codes. This ends the procedure.
  8. Is there more than one storage IOA attached to the IOP?
  9. Go to the service information for the specific disk unit that is listed below and perform the action indicated. Then return here and answer the following question.
    • 2105 Disk Units: Use SRC 3002 exchange the FRUs shown one at a time.
    • 432x, 660x, 671x Disk Units: Use SRC 3002 and exchange the FRUs shown one at a time.

    Did the disk unit service information correct the problem?

    • No: Continue with the next step.
    • Yes: This ends the procedure.
  10. Perform the following steps:
    1. Exchange the IOA. Use the IOP direct select address and the first character of the unit address from step 2 to find the location. See Part locations and location codes.
    2. If exchanging the IOA does not correct the problem, exchange the IOP. Use the IOP direct select address from step 2 to find the location. See Part locations and location codes.
    3. If exchanging the IOP does not correct the problem, exchange the failing items in the following FRU list starting with the first item in the list.
      1. FI01140
      2. System backplane
      3. FI00580
      4. AJDG301
      This ends the procedure.

0004

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

Direct the customer to take the actions necessary to start protection on these disk units. This ends the procedure.

0007

Some of the configured disk units have device parity protection disabled when the system expected device parity protection to be enabled.
  1. Select Manual mode and perform an IPL to DST. See Performing an IPL to dedicated service tools.
  2. Correct the problem by doing the following:
    1. Select Work with disk units > Work with disk unit recovery > Correct device parity protection mismatch.
    2. Follow the on-line 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 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, 660x 102E, 671x 102E 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. This ends the procedure.

000A

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

Use the Service Action Log to find system reference codes associated with the missing disk units by changing the From: Date and Time on the Select Timeframe display to a date and time prior to when the user attempted to vary on the IASP. For information about how to use the Service Action Log, see Searching the service action log. This ends the procedure.

000B

Some system IOPs require cache storage be reclaimed.
  1. Start SST.
  2. Reclaim the cache adapter card storage by performing the following:
    1. Select Work with disk units > Work with disk unit recovery > Reclaim IOP Cache Storage.
    2. Follow the on-line instructions to reclaim cache storage.
    3. After you complete the repair, the system operator may want to restore data from the most recently saved tape. This ends the procedure.

000D

The system disk capacity has been exceeded.

For more information about disk capacity, see the iSeries Handbook. This ends the procedure.

000E

Start compression failure.
  1. Select Manual mode and perform an IPL to DST. See Performing an IPL to dedicated service tools.
  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.

002C

A Licensed Internal Code program error occurred.

Ask your next level of support for assistance. This ends the procedure.

002D

The IASP configuration source disk unit data is down-level.

The system is using the IASP configuration source disk unit that does not have the current level of data.

Work with the customer to recover the configuration. On a workstation with System i Navigator installed, select the disk pool with the problem, and then select Recover configuration. This ends the procedure.

002E

The Independent ASP is assigned to another system or a Licensed Internal Code program error occurred.

Work with the customer to check other systems to determine if the Independent ASP has been assigned to it. If the Independent ASP has not been assigned to another system, ask your next level of support for assistance. This ends the procedure.

002F

The system version and release are at a different level than the IASP version and release.

The system version and release must be upgraded to be the same as the system version and release in which the IASP was created. This ends the procedure.

0030

The mirrored IASP configuration source disk unit has a disk configuration status of unknown and is missing from the disk configuration.

Go to step 1 for cause code 0002.

0032

A Licensed Internal Code program error occurred.

Ask your next level of support for assistance. This ends the procedure.

0099

A Licensed Internal Code program error occurred.

Ask your next level of support for assistance. This ends the procedure.



Last updated: Wed, June 19, 2019