Sábado 18 Mai 2024
S001-4 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 file 
Concatenation of files with different record lengths or record formats.
S001-5 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 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 A dummy file with no blocksize.
S013-14 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 A library member was specified in the JCL but was not found.
S013-20 The block size is not a multiple of record length. 
Check record length in program, compare to actual record length of file
S013-34 The block size was found to be 0. 
A new file is being created but block size was not in the JCL.
S013-40 Reading a file whose JCL has SYSOUT=
S047 The program is on a library/PDS that is not authorized, (APF authorizaion) or one of the libraries in the concatenation is not authorized.
S106 The program on the program library was unreadable. Recompile and link.
S122 The job was canceled because it violated some restriction. 
A dump was requested
S137 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 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 The job was cancelled because it violated some restriction. 
No dump was requested.
S237 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 An Input/output error in the VTOC of a disk volume. Inform support staff.
S322 The job used more CPU time than it should have. 
Either the estimate is wrong or the program is in an uncontrollable loop.
S413 A volume was needed that could not be mounted.
S422 Too many job steps.
S513 Two jobs or DDNAMES wanting same tape at same time.
S522 Job was waiting too long.
S613 A bad tape label.
S637 A bad concatenation, different types of devices were used. 
An unreadable tape mark or label.
S706 The program on the library was not executable. 
See linkage editor report that put the program on library.
S713 The tape was unexpired and the operator terminated the job.
S714 Labels on the tape were bad.
S722 Too many lines of print.
S804 Region too small for the program.
S806 Program not on the library. May need a JOBLIB or STEPLIB.
S80A Region too small for the program.
S813 Right tape volume, wrong dataset name. 
Right dataset name, wrong tape volume.
S913 Security violation.
SA13 Label=n states the wrong number.
SB14 No space in a library directory for this member's name.
SB37 Insufficient disk space.
SD37 Insufficient disk space.
SE37 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 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
S042 Read/write to unopened file 
An uncontrolled loop moved data on top of instructions.
S0C4 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 See reasons as for 0C4. 
Falling through into an ENTRY statement 
Transferring control into the middle of a SORT procedure.
S0C6 Bad boundary alignment for binary data. 
See reasons for 0C4
S0C7 Program attempting to do math on illegal data. 
Data is not numeric, but should be. 
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.
S0CB Attempting to divide by 0 and not using ON SIZE ERROR
U1002 Conflicting file attributes. See S013.
U1005 Executing with modules compiled both with RES and NORES
U1006 Subscript out of range
U1017 Missing DD statement in JCL for DISPLAY or ACCEPT verb
U1020 Problem opening or processing a file. 
Check the file status.
U1026 COBOL sort failed.
U1034 Same as SB37 Abend
U1035 Conflicting DCB parameters. Same as S013.
U1037 Program control falls through the last physical statement in program, 
which is not GOBACK/STOP RUN.
U1056 Program didn't close a file before ending
U1066,U1075 Conflicting DCB information for file defined as EXTERNAL
U1072,U1073,U1074 Illegal numbers in reference modification
U3000 COBOL LE intercepted the Abend. Messages in SYSDBOUT.
U4038 COBOL LE intercepted the Abend. Messages in CEEDUMP.