POWER7 information

Licensed Internal Code initialization

This topic provides information about Licensed Internal Code initialization.

Functions performed

The following list is a high-level description of the functions that are performed by Licensed Internal Code during an initial program load (IPL):
  1. Licensed Internal Code sets the internal processing unit registers and arrays.
  2. When the initialization is complete, Licensed Internal Code signals the service processor of the event.
  3. Licensed Internal Code enters the disabled state (task dispatcher is disabled). After the service processor starts the processing unit, the earlier constructed queue is made ready. The Licensed Internal Code then does its normal work-time functions.

See IPL status SRCs for information that is displayed on the control panel during an IPL.

Abnormal ending

Licensed Internal Code ends an IPL when a condition is detected that prevents the machine from doing work. The service processor sends the correct SRC to the control panel.

Conditions that cause Licensed Internal Code initialization to fail are:
  • Licensed Internal Code hangs (loops or waits), causing a Licensed Internal Code initialization time-out. The processor gives control to the service processor which, in turn, ends the IPL.
  • Licensed Internal Code that is not compatible with the control storage.

    Some of the Licensed Internal Code is in main storage in an area that is known as the Licensed Internal Code overlay area. If this code is not compatible with resident code in control storage, the IPL might end during the Licensed Internal Code initialization phase.

  • Bad data on file.

    If bad data is not detected when read from the file but is detected by the Licensed Internal Code initialization routine, the IPL ends with an SRC. If bad data is on the file, use the Main storage dump manager option from the Start a Service Tool display under DST to save the main storage dump to removable media. You must install the Licensed Internal Code again to correct this problem. If the system does not complete an IPL after initializing the Licensed Internal Code again, the Licensed Internal Code tape is bad.

  • Hardware errors.

    If hardware errors occur during the Licensed Internal Code initialization step, the IPL ends. If the hardware error is associated with the file, you might need to install the Licensed Internal Code again.

At any point in the Licensed Internal Code initialization phase, errors that end machine processing during an IPL can occur. If this occurs, indicators are set to the data function. The machine check error log buffer, Licensed Internal Code log, or the product activity log contain information about the condition that caused the ending.

Initialization output

The output that is created when the Licensed Internal Code is initialized consists of the following:
  • Machine status information saved in the machine initialization status record (MISR).
  • Status codes for an initial program load displayed on the control panel for long-running IPL functions.
  • Product activity log and Licensed Internal Code log information that service personnel need to service the machine.

Data descriptions

  • Preceding stopped data
  • Bad page table
Parent topic: Platform IPL sequence

Send feedback Rate this page

Last updated: Wed, September 28, 2016