Steps for diagnosing a coded disabled wait state
- Obtain the disabled wait state code from the from the stand-alone
dump, if obtained or the Hardware Management Console (HMC). The IPCS STATUS
WORKSHEET report from a stand-alone dump often contains a corresponding
wait state message. For example:
Figure 1. IPCS STATUS WORKSHEET report from a stand-alone dump MVS Diagnostic Worksheet Dump Title: WAIT 0A2 REASON 15A ZOS 1.7 INSTALAC SYSPLEX CPU Model 2066 Version 00 Serial no. 0123B4 Address 00 Date: 05/22/2006 Time: 20:48:49.817141 Local Wait State Message Issued at 20:43:48 on Day 142 of 2006: IXC436W THIS SYSTEM HAS LOST TIME SYNCHRONIZATION WITH THE OTHER SYSTEMS IN THE SYSPLEX AND HAS BEEN PLACED INTO A NON-RESTARTABLE WAIT STATE CODE: 0A2 REASON CODE: 15A SYSTEM RELATED DATA CVT SNAME (154) IEASYSFI VERID (-18) CUCB (64) 00FD5140 PVTP (164) 00FFB108 GDA (230) 0210A278 RTMCT (23C) 00F4FB20 ASMVT (2C0) 00FD75D8 RCEP (490) 01907F18 CSD Available CPU mask: 8000 Alive CPU mask: 80000000 00000000 Number of active CPUs: 00000001 PROCESSOR RELATED DATA NAME OFFSET | CPU 00 --------------------------+----------------------------------------- PSW at time of dump | 00020000 | 80000000 | 00000000 | 0015A0A2 - Find the wait state code using z/OS MVS System Codes. If there is no recommended action:
- Look up the wait state code in the System completion code to module table in z/OS MVS System Codes.
- Use the module name to identify the component using the Identifying modules, components, and products table in z/OS MVS Diagnosis: Reference.
- Perform a search using the wait state code, reason code, module name and component identifier to look for a known problem. If you cannot find a match, report the problem to IBM®.
| Wait state code | Reason code | Explanation | More information: |
|---|---|---|---|
| X'01B' | This is a restartable wait state that is
loaded when an active SLIP trap requests an action of WAIT. The conditions
specified on the SLIP command are met. The system
enters a wait state, as requested. Information about the environment
when the slip trap matches is presented in message IEE844W. For example: |
The topic on SLIP problem data in the SLIP work area in z/OS MVS Diagnosis: Tools and Service Aids. | |
| X'040' | The system ended a task during nucleus initialization program (NIP) processing. | Diagnosing an abend | |
| X'064' | X'005' | Indicates that an ABEND was issued during NIP. To diagnose using a SADUMP, do a SYSTRACE ALL, max PF8 to the bottom of the output and do a 'F *SVC PREV' to locate the ABEND issued. | |
EXAMPLE: WAITX'064' RSNX'005' |
|||
| X'064' | X'009' | A program check occurred during nucleus
initialization program (NIP). Message IEA304W explains the 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 the z/OS Internet library. To diagnose using a stand-alone dump, format the LCCA by entering the CBFormat LCCAx command (where x is the CPU ID). |
Diagnosing an abend |
| X'0A2' | X'004' | The operator entered the VARY XCF,sysname,OFFLINE command to remove the system from the sysplex. | Ask the operator or system programmer why the system was varied out of the sysplex before continuing with diagnosis. |
| X'104' | I/O is prevented because a system is fenced. | Go to Diagnosing a system partitioned from a sysplex because of status update missing | |
| X'10C' | Cross-system coupling facility (XCF) or cross-system extended services (XES) encountered an unrecoverable error and stopped the system. The system also issues this wait state in response to an operator request to stop the system. For information about diagnosing sysplex problems see, z/OS MVS Diagnosis: Reference. | Diagnosing an enabled wait state | |