JCL Abend codes

S001-4 ABEND
- Input file record length is not equal to the length stated in the DD or the FD.
- Wrong length record.
- IO error, damaged tape, device malfunction.
- With disk, reading a dataset that was allocated but never written to.
- Writing to input files Concatenation of files with different record lengths or record
formats.
S001-5 ABEND
- Reading after the end of the file by non-COBOL program.
- COBOL intercepts this and displays "QSAM error, status 92".
- Out of space on output disk file.
S002 ABEND
- With variable format files used for output.
- The record is larger than the track size.
- The record length is greater than allowed maximum 32,768.
- The wrong record length is being used on output.
- The 4-byte record length indicator is wrong.
- Record greater than 32,768 bytes
S013-10 ABEND
- A dummy file with no block size
S013-14 ABEND
- A library has run out of space in its directory.
- You have to backup, delete, and restore the library with IEBCOPY.
- A dataset is sequential, but the JCL indicates that it is a library/PDS.
S013-18 ABEND
- A library member was specified in the JCL but was not found
S013-20 ABEND
- The block size is not a multiple of record length.
- Check record length in program, compare to actual record length of file
S013-34 ABEND
- The block size was found to be 0.
- A new file is being created but block size was not in the JCL.
S013-40 ABEND
- Reading a file who’s JCL has SYSOUT=
S106 ABEND
- The program on the program library was unreadable. Recompile and link.
S122 ABEND
- The job was canceled because it violated some restriction.
- A dump was requested

1
JCL Abend codes

S137 ABEND
- A tape has a bad trailer label.
- Copy the file with IEBGENER, ignoring the error. The copy will be good.
- Using LABEL=2 when there's only one dataset on the tape.
S213 ABEND
- A disk dataset was not actually on the volume stated in the VOL=SER=.
- A disk dataset was not actually on the volume indicated in the catalog.
S222 ABEND
- The job was cancelled because it violated some restriction.
- No dump was requested.
S237 ABEND
- The block count on a tape trailer label is wrong.
- Probably caused by hardware error.
- Copy the file with IEBGENER, ignoring the error. The copy will be good.
- A problem with the second volume of tape or disk.
S313, 314 ABEND
- An Input/output error in the VTOC of a disk volume. Inform support staff.
S322 ABEND
- The job used more CPU time than it should have.
- Either the estimate is wrong or the program is in an uncontrollable loop.
S413 ABEND
A volume was needed that could not be mounted.
S422 ABEND
- Too many job steps.
S513 ABEND
- Two jobs or DDNAMES wanting same tape at same time.
S522 ABEND
- Job was waiting too long.
S613 ABEND
- A bad tape label.
S637 ABEND
- A bad concatenation, different types of devices was used.
- An unreadable tape mark or label.
S706 ABEND
- The program on the library was not executable.
- See linkage editor report that put the program on library.
S713 ABEND
- The tape was unexpired and the operator terminated the job.

2
JCL Abend codes

S714 ABEND
- Labels on the tape were bad.
S722 ABEND
- Too many lines of print.
S804 ABEND
- Region too small for the program.
S806 ABEND
- Program not on the library. Load module not found. May need a JOBLIB or STEPLIB.
S80A ABEND
- Region too small for the program.
S813 ABEND
- Right tape volume, wrong dataset name.
- Right dataset name, wrong tape volume.
S837 ABEND
- Space problem, allotted space is not enough for data set
S913 ABEND
- Security violation.
- You are trying to access a dataset which you are not authorized to use.
SA13 ABEND
- Label=n states the wrong number.
SB14 ABEND
- No space in a library directory for this member's name.
SB37 ABEND
- Insufficient disk space.
SE37 ABEND
- Insufficient disk space. The maximum number of extents would be exceeded. For
instance, when exceeding 16 extents of a PDS.
- An E37 on tape datasets is most often caused when the number of requested volumes is
exceeded. The default is 5; therefore a request for the sixth volume will fail with a E37.
S0C1 ABEND
- Executing a program with an unresolved external reference.
- Calling a program and the program was not included during link edit.
- An uncontrolled loop moved data on top of instructions.
- Reading a file that is not open
- Your SORTIN DCB was not correct
- Mixing compile options RES and NORES in different modules

3
 JCL Abend codes

S0C2Privileged Operation ABEND

- Read/write to unopened file
- An uncontrolled loop moved data on top of instructions.
SOC4 ABEND
- Index exceeds the size of table
- Trying to use File Section variables without opening the file
S0C4 Protection ABEND
- An uncontrolled loop moved data on top of instructions.
- Referencing a field in a record of a closed file.
- Referencing an item in Linkage-Section when there was no PARM= in the JCL.
- Calling/called programs have different length for items passed in Linkage Section
with COBOL Sort, doing a STOP RUN or GOBACK while an input or output
procedure is still running.
S0C5 Addressing ABEND
- Falling through into an ENTRY statement
- Transferring control into the middle of a SORT procedure.
S0C6 Specification ABEND
- Bad boundary alignment for binary data.
S0C7 ABEND
- Program attempting to do mathematic calculations on illegal data.
- Moving non-numeric value to numeric field
- Not initializing the numeric variables before first use
- Moving ZEROS to group item whose subordinate items are packed-decimal
- Uninitialized packed-decimal fields.
- Record description is wrong. Field starts or ends in the wrong place in the record.
- Find record description of creating program.
S0C8 ABEND
- Attempting to divide by 0 and not using ON SIZE ERROR
U1002 ABEND
- Conflicting file attributes.
U1005 ABEND
- Executing with modules compiled both with RES and NORES
U1006 ABEND
- Subscript out of range
U1017 ABEND
- Missing DD statement in JCL for DISPLAY or ACCEPT verb
U1020 ABEND
- Problem opening or processing a file.
- Check the file status.

4
JCL Abend codes

U1026 ABEND
- COBOL sort failed.
U1034 ABEND
- Insufficient disk space (Same as SB37 Abend)
U1035 ABEND
- Conflicting DCB parameters (Same as S013)
U1037 ABEND
- Program control falls through the last physical statement in program,
which is not GOBACK/STOP RUN.
U1056 ABEND
- Program didn't close a file before ending
U1066, U1075 ABEND
- Conflicting DCB information for file defined as EXTERNAL
U1072, U1073, U1074 ABEND
- Illegal numbers in reference modification
U3000 ABEND
- COBOL LE intercepted the Abend. Messages in SYSDBOUT.
U4038 ABEND
- COBOL LE intercepted the Abend. Messages in CEEDUMP