064   

Explanation

During nucleus initialization program (NIP) processing, NIP detected a software or hardware error. An attempt was made to enter the recovery termination manager (RTM). This was trapped by NIP because the system is in a variable state of initialization and, in particular, RTM is not fully initialized.

The right-most four bytes of the program status word (PSW) have the following format: 
x0rrrwww
where:
x
Irrelevant information.
rrr
A hexadecimal reason code indicating the reason for the failure.
www
The wait state code.
The reason code (rrr) is one of the following:
001
A module branched to abnormal ending processing.
002
A dynamic address translation (DAT) error occurred.
003
The operator pressed the RESTART key instead of the time-of-day (TOD) key.
004
A machine check occurred. This can be caused by:
  • An I/O interrupt from a device that was not defined in the I/O configuration program (IOCP). The channel subsystem presents the interruption as a machine check.
  • The system is changing the state of a resource during system initialization.
005
A Supervisor Call (SVC) instruction was issued in an incorrect mode. However, this is not usually the actual error, because it is common for system routines to issue an abend while holding a lock.
Code X'05' can occur when:
  • NIP is reading from SYS1.PARMLIB
  • NIP is trying to process an incorrect load module
  • I/O errors occurred on the system residence volume
006
A paging I/O error occurred.
007
A call to abnormal ending processing was issued without providing an address space identifier (ASID).
008
A request for memory ending occurred.
009
A program check occurred. Accompanying message IEA304W further explains this wait state and entry code. If the message does not appear on the console, you can find the message in the wait state message area (WSMA). The WSMA is described in z/OS MVS™ Data Areas in z/OS® Internet Library at http://www.ibm.com/systems/z/os/zos/bkserv/.
00A
NIP called the alternate CPU recovery (ACR) component.
00B
A call to cross-memory abend processing was issued with the address space identification (ASID) provided.
00C
A routine entered RTM holding a cross memory local (CML) lock.
00D
A module specified the ITERM option on the CALLRTM macro.
00E
A module specified the SABEND option on the CALLRTM macro.
00F
A call to ABTERM processing was issued with RETRY=NO.
010
A call to cross-memory ABTERM processing was issued with RETRY=NO.

System action

The system issues messages about the problem. The system may issue message IEA304A. The system enters a restartable wait state.

Operator response

Do one of the following:
  • For table entry code X'003' reIPL the system.
  • For table entry code X'004', do the following:
    • Use the hardware Problem Determination facilities to see if any unexpected events occurred during the IPL process.
    • Check that the system is using the correct I/O configuration data set (IOCDS).
    • Notify the system programmer and provide the text of the message.
    Do not:
    • Detach, attach, or define any I/O service during system initialization.
    • Configure on or offline any channel path identifiers (CHPID) to the logical partition where the system is initialized if the system is running in logically partitioned (LPAR) mode.
  • For table entry code X'009', try restarting the system, specifying CLPA in the reply to accompanying message IEA101A. Table entry code X'009' may occur on a warm or quick start if the previous cold start failed before or during master scheduler initialization.
  • For other entry codes, check the READ/WRITE switch on direct access storage devices (DASD) before reporting this wait state code to the system programmer.

If the system programmer requests it, obtain a stand-alone dump.

System programmer response

Search problem reporting databases for a fix for the problem. If no fix exists, do the following before contacting the IBM® Support Center:
  • For table entry code X'005', determine if an SVC 13 was the last SVC issued by looking at the SVC OLD PSW or the trace table in a stand-alone dump. If this is the case, register 1 in the trace table contains the abend codes and register 15 contains the reason code. The abend code may indicate which SVC issued the abend. If it does, the trace table may show the module that issued the SVC.
    If SVC 13 was not the last SVC issued, then it is a true SVC error. The problem could be:
    • A module is incorrectly issuing an SVC while holding a lock.
    • A routine that was in control returned to its caller without releasing a lock. In this case, the SVC-issuer is not at fault.
  • For table entry code X'009', the program check OLD PSW indicates the type of exception and where it occurred. The registers at the time of the exception are saved at displacement X'48' into the logical configuration communication area (LCCA). If it was a translation exception (program interrupt code X'10' or X'11'), location X'90' contains the address that could not be translated. The system trace also contains this information.

Search problem reporting databases for a fix. If no fix exists, contact the IBM Support Center. Provide the information that you gathered, including the wait state PSW.

Source

Nucleus initialization program (NIP)

Parent topic: Wait state codes