S001:

Check/Get/Put I/O error (BSAM, BISAM, BDAM, OSAM) 1. Wrong record length or block size specified 2. No EOF marker on input DASD dataset 3. Actual I/O error; damaged tape, track; malfunctioning device 4. Attempted to read from dataset after EOF

S002:
Error while processing, creating, or opening a dataset 1. Attempting to write a record larger than track length no overflow specified 2. Record length greater than allowed (maximum = 32,768) 3. For variable length output records, 4-byte length field at beginning of record contained value larger than maximum allowed for that dataset; either value was calculated incorrectly or not at all or the wrong field is pointed to

S038:
Error during open processing (QISAM) 1. Dataset has not closed after creation 2. Dataset had not been created 3. Indexed sequential creation and retrieval not specified 4. DCB was opened for PUT operation, but OPEN didnt specify OUTPUT 5. Error in LRECL or BLKSIZE information; LRECL was zero or BLKSIZE less than LRECL or not multiple of LRECL 6. Key length specified as zero 7. DISP=SHR specified for QISAM dataset opened for OUTPUT

S03D:
Error during OPEN processing; error in VOLUME parameter of DD statement 1. Not all Volumes specified or specified in incorrect order; VOLUME containing INDEX must be listed first 2. DCB parameter on DD card did not specify DSORG=ISU for Indexed Sequential organization; this is required on the DD statement even if specified in program 3. OPEN was issued for a direct dataset but the datasets organization is Indexed Sequential

S0C1:
Operation exception

1. Program branched to data area 2. Instruction was destroyed by uncontrolled loop moving data to area preceding instruction 3. An attempt was made to access an unopened dataset. The dataset may be unopened for one of the following reasons: A. No OPEN was issued for the dataset B. The dataset was accessed after it was closed C. The DD statement was missing D. The DD statement contained a ddname different from that referenced in the program 4. Calling a module which was not included in the load module. Check Link Edit messages for unresolved external reference

S0C2:
Privileged operation exception (same as S0C1)

S0C3:
Execute exception

S0C4:
Protection exception or virtual add could not be translated into real add 1. Incorrect index or subscript because it was un-initialized or it exceeded its maximum 2. Uncontrolled loop caused reference to area outside program 3. Reading from or writing to an unopened dataset (may also cause S0C1); User 16 is file open 4. Incorrect value in register used as base or index (e.g. L instead of LA or vice versa) 5. Filling area outside of predetermined table area (POSSIBLY IN A CALLED MODULE!!!) Missing or incorrect DD statement Check system messages from abending step. Tried to reference record area before file opened. Indexing or subscripting outside defined limits. Linkage section incorrectly placed or omitted. Linkage section referenced without coding using clause on 'PROCEDURE DIVISION' or 'ENTRY' statement. Mismatched parameter list between calling program and subroutine. STOP RUN or GOBACK used in sort input procedure or output procedure. PERFORM or GOTO outside of section from sort input procedure or output procedure.

S0C5:
Addressing exception

1. Index or subscript was not initialized properly or exceeded its limits 2. Reference made to an input or output area before OPEN issued 3. Using an incorrectly initialized register as a base register for an instruction or a branch register

S0C6:
Specification exception 1. A data area or instruction that needed to be aligned on a particular boundary wasnt 2. Multiplier or divisor in decimal arithmetic exceeded 15 digits and a sign 3. The operand field is shorter than or equal to the second field in decimal multiplication or division 4. Odd register specified instead of even register or even/odd pair 5. Floating-point register other than 0, 2, 4, or 6 was specified 6. Missing or incorrect DD statement. 7. Duplicate close or writing to a closed file. 8. Referenced an I/O area before read, write, or open. 9. Tried to write on file opened as input. 10. Decimal multiplier or divisor exceeds 15 digits. 11. Address, data or instruction on improper boundary. 12. Subscript exceeded limit and overlaid instruction.

S0C7:
Data exception 1. One of the fields involved in a packed decimal operation did not contain valid packed decimal data 2. Data field was not initialized or was initialized incorrectly 3. Input data was incorrect 4. Uncontrolled loop operating on decimal fields 5. Record description does not match actual record fields 6. Fields in decimal arithmetic operation overlap incorrectly

S0C8:
Fixed-point overflow exception

S0C9:
Fixed-point divide exception

S0CA:
Decimal-overflow exception

S0CB:
Decimal-divide exception (attempting to divide by zero)

S0CC:
Exponent-overflow exception

S0CD:
Exponent-underflow exception

S0CE:
Significance exception

S0CF:
Floating-point divide exception

S102:
Post macro encountered an invalid ECB address

S106:
Link, load, attach, or XCTL macro requested program

S122:
Operator cancelled job and requested a dump 1. Program requested unavailable volume or device 2. Program appeared to be in a loop 3. Operations scheduling determined that something else had a higher priority or emergency status and had to be run; normally in this case, the operator should simply re-queue your job and should not cancel it 4. The program was producing incorrect output or an abnormal amount of output 5. The operator erred

S137:
I/O error occurred during end-of-volume on magnetic tape, or invalid header or trailer label was read 1. Most likely a valid I/O error 2. Contents of header or trailer label may be incorrect 3. Second or subsequent volume on output dataset may contain unexpired dataset and operator did not specify to use it

S13E:
Attaching task issued detach for subtask before subtask was completed

S201:
Wait macro expansion contained invalid ECB address

S206:
Link, load, XCTL or delete macro had error in its parameter list

S213:
Error during OPEN for dataset on direct access; dataset could not be found 1. Dataset name misspelled on DD card 2. DISP specifies OLD or SHR when dataset is being created 3. Incorrect volume serial number specified on DD card or in catalog 4. Dataset scratched but not removed from catalog (this happens if delete is specified for disposition and unit and volume information are provided on the DD card so the cataloged dataset is not referenced) 5. Dataset was cataloged but not created 6. OPEN issued for password-protected dataset but password dataset could not be found on SYSRES volume

S214:
I/O error during CLOSE for dataset on magnetic tape

S222:
Operator cancelled job without dump 1. Program requested unavailable volume or device 2. Program appeared to be in a loop 3. Operations scheduling determined that something else had a higher priority or emergency status and had to be run; normally in this case, the operator should simply re-queue your job and should not cancel it 4. The program was producing incorrect output or an abnormal amount of output 5. The operator erred

S237:
Invalid block count or dataset name 1. Trailer label block count doesnt match block count in DCB; most likely hardware error skipped block 2. Dataset name on second or subsequent volume doesnt match dataset name on DD card

S301:
Wait macro specified ECB whose wait flag was already on

S306:
Link, load, XCTL or attach specified program that needed to be in authorized library but wasnt

S322:
Job or job step exceeded specified CPU time

1. Incorrect time parameter on JOB or EXEC card 2. Program loop 3. Estimated time exceeded (TIME=1440 is unlimited time or change CLASS T to A)

S337:
DCB for input dataset specified had no EODAD routine

S400:
DCB address in DEB differs from DCB address in IOB

S413:
Error during OPEN for dataset on magnetic tape or DASD 1. Volume could not be mounted on specified unit because volume already on that unit is permanently resident or reserved or has an open data set on it 2. I/O error reading volume label, positioning tape or writing tape mark 3. No volume serial specified for input dataset 4. Volume sequence number specified was larger than the number of volumes containing the dataset

S43E:
Attach macro specified invalid ECB address

S513:
Tape device specified by OPEN already has open dataset on it 1. Trying to open 2 datasets on the same magnetic tape volume at the same 2. Previous abend associated with same service in same step

S522:
ECB specified in wait was never posted; maximum allowed wait time was exceeded 1. Operator may not have mounted volume or replied to WTOR related to job step 2. Wait or post issued for wrong ECB; may be referencing the address of the ECB rather than the ECB itself

S706:
Module requested was marked non-executable (errors during link edit of load module caused it to be marked non-executable)

S713:
Error during open; expiration date not passed (operator caused job to terminate since the expiration date had not yet passed)

S714:
I/O error during close while writing trailer label or tape mark (generally a genuine

hardware malfunction or problem with tape)

S722:
Estimated lines exceeded (TIME=1440 is unlimited time)

S737:
I/O error during end-of-volume or during allocation of secondary storage

S804:
Not enough storage available to satisfy get-main request

S806:
Specified program could not be found or I/O error occurred while processing link, load XCTL or attach macro (try adding REGION=8M PARM to job card)

S813:
Dataset name on DD card doesnt match dataset name in tape header label 1. Wrong volume mounted 2. Dataset name misspelled on DD card 3. Dataset was not created on that volume or was scratched and written over 4. Incorrect volume serial number specified on DD card or in catalog

S913:
Error during open of password-protected or checkpoint dataset 1. Open issued for checkpoint dataset with organization other than BSAM or BDAM 2. OPEN issued for password-protected dataset and incorrect password was supplied 3. OPEN issued for VTOC and program was not authorized 4. OPEN TYPE=J issued for ISAM dataset and dataset names in DD statements defining dataset were not all the same or did not match dataset name in JFCB passed to OPEN 5. OPEN TYPE=J issued for dataset on DASD and dataset name was not available because it was being used by other job

S814:
Error during CLOSE for partitioned dataset opened for output to a member 1. No space left in directory 2. An attempt was made to stow member in directory, but name already exists there 3. An I/O error occurred while member name was being stowed

S837:
Direct access dataset required more tapes 1. Put in VOLUMES parameter

SB37:
Direct access dataset required more space but had already used 16 extents

1. WRITE loop 2. Insufficient space specified in the SPACE parameter particularly in the primary allocation

SC03:
Dataset could not be closed by end-of-task processing 1. Program allows task termination routines to close datasets; DCB for open dataset is in a segment of an overlay structure that is not in virtual storage at the time of termination, or in a load module that gave up control through an XCTL 2. DCB for a dataset open at task termination was in an area of virtual storage already freed up

SC13:
Error occurred during OPEN for concatenated partitioned dataset (output dataset cannot be concatenated)

SC37:
Next volume of input dataset on DASD contained more than 16 extents

SD37:
More space was requested by the dataset but no secondary space was requested in the SPACE parameter

SE37:
No more volumes available or DASD dataset with duplicate name was specified as additional volume 1. Not enough volumes requested 2. More space required for partitioned dataset but all 16 extents used 3. No more space on volume when writing to partitioned dataset; all partitioned datasets must reside on one volume 4. WRITE loop in program

SOCB Error:
1. Division by Zero