LICIP01

Licensed Internal Code detected an IOP programming problem.

You will need to gather data to determine the cause of the problem. If using OptiConnect, and the IOP is connected to another system, then collect this information from both systems. Read the Licensed internal code isolation procedures before continuing with this procedure.
  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 before continuing with this procedure.
  2. Is the system operational: Did the SRC come from the Service Action Log, Product Activity Log, problem log, or system operator message?
    • No: Go to step 9.
    • Yes: Is this a x6xx5121 SRC?
      • No: Continue with the next step.
      • Yes: Go to step 4.
  3. If the IOP has DASD attached to it, then the IOP dump is in SID87 (or SID187 if the DASD is mirrored). Copy the IOP dump. See Storage dumps .
  4. Print the Product Activity Log, including any IOP dumps, to removable media for the day which the problem occurred. Select the option to obtain HEX data.
  5. Use the "Licensed Internal Code log" service function under DST/SST to copy the LIC log entries to removable media for the day that the problem occurred.
  6. Copy the system configuration list. See System configuration list .
  7. Provide the dumps to Service Support.
  8. Check the Logical Hardware Resource STATUS field using Hardware Service Manager. If the status is not Operational then IPL the IOP using the I/O Debug option. Ignore resources with a status of not connected.

    To IPL a failed IOP, the following command can be used: VRYCFG CFGOBJ(XXXX) CFGTYPE(*CTL) STATUS(*RESET) or use DST/SST Hardware Service Manager.

    If the IPL does not work:
    • Check the Service Action Log for new SRC entries. See Searching the service action log . Use the new SRC and perform problem analysis to correct the problem.
    • If there are no new SRCs in the Service Action Log, contact your next level of support. This ends the procedure.
  9. Has the system stopped but the DST console is still active: Did the SRC come from the Main Storage Dump manager screen on the DST console?
    • Yes: Continue with the next step.
    • No: Go to step 15.
  10. Complete a Problem Summary Form using the information in words 1-9 from the control panel, or from the DST Main Storage Dump screen.
  11. The system has already taken a partial main storage dump for this SRC and automatically re-IPLed to DST.
  12. Copy the main storage dump to tape. See Storage dumps .
  13. When the dump is completed, the system will re-IPL automatically. Sign on to DST or SST. Obtain the data in steps 3, 4, 5, and 6.
  14. Provide the dumps to Service Support. This ends the procedure.
  15. Has the system stopped with an SRC at the control panel?
    • Yes: Continue with the next step.
    • No: Go to step 2.
  16. Complete a Problem Summary Form using the information in words 1-9 from the control panel, or from the DST Main storage dump screen.
  17. Do NOT power off the system. Perform a manual IPL to DST, and start the Main storage dump manager service function.
  18. Copy the main storage dump to tape.
  19. Obtain the data in steps 3, 4, 5, and 6.
  20. Re-IPL the system.
  21. Has the system stopped with an SRC at the control panel?
    • Yes: Using the new SRC, perform problem analysis to correct the problem. This ends the procedure.
    • No: Provide the dumps to Service Support. This ends the procedure.