Interpreting wait-state codes

DFSMSdss stores a code in the six right-most bytes of the programming status word (PSW). The following wait-state codes can occur during the Stand-Alone Services IPL:
Code
Explanation
 
 
000033
A program check occurred while Stand-Alone Services was being loaded. Contact your software service representative.
000044
The IPL device is not operational. Contact your hardware service representative. If the IPL device is a tape drive, try to IPL from another tape drive.
000055
An I/O error occurred on the IPL device or channel while Stand-Alone Services was being loaded. Contact your hardware service representative to correct the cause of the problem.
000066
The IPL loader is unable to determine if the entire Stand-Alone Services core image has been loaded. This could be due to a software or hardware error. Determine the cause of the problem and contact the appropriate service representative.
000077
The IPL loader is unable to locate the SYS1.ADR.SAIPLD.Vvolser data set on the IPL volume.
000088
The device type being used to IPL is not a supported DASD device for IPLing the Stand-Alone Services.
0000AA
An attempt was made to IPL a processor that could not switch to zArchitecture. zArchitecture is required on this release of Stand-Alone Services.
0000AE
An external interrupt occurred while Stand-Alone Services was being loaded. Contact your software service representative.
0000AF
A supervisor call instruction (SVC) interrupt occurred while Stand-Alone Services was being loaded. Contact your software service representative.
0000E2
A machine check has occurred. Contact your hardware service representative.
111111
Stand-Alone Services is waiting for an I/O interrupt. If the processor stops with this code loaded it may be necessary to re-IPL and rerun the command. Contact your hardware service representative if the problem persists.
888888
A temporary wait for a service-signal interrupt.
999999
A temporary wait for a service-signal interrupt.
BBBBBB
Stand-Alone Services is waiting for the operator to enter the input in response to a prompting message on the service console.
DDDDDD
Stand-Alone Services has detected an error related to the predefined console, and is waiting for the operator to identify another console to be used as the operator console. Possible reasons for the error with the predefined console and actions to take are listed in Running stand-alone services with a predefined console.
EE4990
Stand-Alone Services cannot find a required module. Refer to message ADRY4990I for more information.
EEEEnn
The processor is in a wait-state. The error is indicated by nn as follows:
nn
Indicates:
13
An SVC interrupt has occurred. Run the SADMP* service aid to dump the contents of real storage to tape, and contact your software service representative.
14
A program interrupt has occurred. Run the SADMP* service aid to dump the contents of real storage to tape, and contact your software service representative.
15
There is insufficient main storage. Stand-Alone Services requires 2MB of storage.
16
An I/O error has occurred.
17
Stand-Alone Services is unable to open a data set or access a device, possibly because the device type is not supported.
18
Stand-Alone Services cannot send an operator message because the console is either not defined or is unavailable.
19
An end-of-data routine is missing. Run the SADMP* service aid to dump the contents of real storage to tape, and contact your software service representative.
1A
The predefined console is not attached or is not operational. Possible reasons for this error are listed in Running stand-alone services with a predefined console.
1B
Stand-Alone Services is unable to communicate with the predefined service console. This may be due to an error, or because the necessary features do not exist on the processor to communicate with the predefined console.
Note: See z/OS MVS Diagnosis: Tools and Service Aids for information on creating a stand-alone dump with the AMDSADMP (SADMP) service aid.
EECC03
A condition code 3 (not operational) has been received when attempting to communicate with the service console. Contact your hardware service representative.
EECCCC
An error occurred while trying to communicate with the service console. This can result from a hardware or a software problem.
F1F1F1
Waiting for an I/O interrupt while Stand-Alone Services is being loaded. This may also indicate a hardware problem with the device you are IPL'ing from.
FFFFFF
Stand-Alone Services is waiting for the operator to identify the operator console. Generate an interrupt from the console that is to be used as the operator console.