Wait State Codes from SAR
SAR issues wait states indicating an action is required or an error has occurred. Most wait states are preceded by an explanatory message. The wait state code is the last four digits of the current PSW. On many CPUs the PSW is automatically displayed on the hardware console when the STOP key is pressed; consult your hardware operating spaces for details.
Wait State
Number | Description |
|---|---|
00E2 | MACHINE CHECK Explanation: A machine-check (CPU error) has occurred and SAR is unable to continue. Action: Display storage location 232 (x'E8') to get the machine check interrupt code, which can be interpreted using information in the Principles of Operation and/or Reference Summary for your CPU. Contact your hardware maintenance vendor for assistance. |
1111 | I/O WAIT AND RETRY PSW Explanation: A normal wait state during I/O operations. |
3333 | CONSOLE ERROR Explanation: An I/O error has occurred reading or writing from the master console. This is not preceded by a message. Action: ReIPL SAR and retry using a different console. |
5555 | PROGRAM CHECK Explanation: A program check occurred before SAR identified the console. SAR was not able to issue a message. Action: Contact BMC Support for assistance. |
9997 | TERMINATE WAIT STATE Explanation: An I/O error or other error has abnormally terminated SAR. An FDR9xx message detailing the error should have been printed. |
9999 | EOJ WAIT STATE Explanation: Normal wait state indicating end of job. An FDR99x message should have been printed. |
FFFF | OPERATOR CONSOLE WAIT STATE Explanation: This wait state indicates that SAR has been successfully loaded. SAR is now waiting for the interrupt that identifies the device to be used as the console. 1. If you are executing a SNAP, SPLIT, PSPLIT, or FCOPY function, message FDR152 with the indicated reason codes prevents the function from completing. If you want the function to complete despite the message, add the operand SMSPROT=NONE to the SNAP, SPLIT, PSPLIT, or FCOPY statement. 2. For the indicated reason codes, FDR prints a mini-dump displaying the VVR (VSAM Volume Record) from the backup file and from the cluster on DASD. In the registers at the top of the dump, register 14 points to a cell within the DASD VVR and register 15 points to a cell within the backup VVR. Those registers plus the hex displacements shown above for the appropriate reason codes point to the fields that did not compare. 3. If you are executing a SNAP, SPLIT, PSPLIT, or FCOPY function, message FDR152 with the indicated reason codes prevents the function from completing. If you want the function to complete despite the message, add the operand SMSPROT=NONE to the SNAP, SPLIT, PSPLIT, or FCOPY statement. 4. For the indicated reason codes, FDR prints a mini-dump displaying the VVR (VSAM Volume Record) from the backup file and from the cluster on DASD. In the registers at the top of the dump, register 14 points to a cell within the DASD VVR and register 15 points to a cell within the backup VVR. Those registers plus the hex displacements shown above for the appropriate reason codes point to the fields that did not compare. 5. For the indicated reason codes, FDR prints a mini-dump displaying the VVR (VSAM Volume Record) from the backup file and from the cluster on DASD. In the registers at the top of the dump, register 14 points to a cell within the DASD VVR and register 15 points to a cell within the backup VVR. Those registers plus the hex displacements shown above for the appropriate reason codes point to the fields that did not compare. 6. For the indicated reason codes, FDR prints a mini-dump displaying the VVR (VSAM Volume Record) from the backup file and from the cluster on DASD. In the registers at the top of the dump, register 14 points to a cell within the DASD VVR and register 15 points to a cell within the backup VVR. Those registers plus the hex displacements shown above for the appropriate reason codes point to the fields that did not compare. |