EMM 1997 INDIETRO

Common System Codes

Original page hosted in Clemson Univ. | Clemson Home |
Clemson Univ. is legitimate propetary of this page, I only put this page in my home for better reference.

This document contains a brief explanation of the more common system completion codes. When a program abends, the corresponding system message and/or system code is printed in the JCL listing. The system abend code may appear as part of the system message that begins with IECxxxI; it is located in the JES2 job log and in the JCL expansion at the step where the abend occurred. The general form of all system messages related to system codes is as follows: 

IECyyyI XXX-RC,MOD,JJJ,SSS,DDN(#),DDD,SER,DSN

where:

IECYYYI
is the SYSTEM MESSAGE NUMBER
XXX
is the THREE DIGIT SYSTEM CODE
RC
is the TWO DIGIT RETURN CODE
MOD
is the MODULE NAME (Program ID)
JJJ
is the JOB NAME
SSS
is the STEP NAME
DDN(#)
is the DD NAME followed by a concatenation number if it is part of a concatenation and not the first DD name
DDD
is the DEVICE ADDRESS
SER
is the VOLUME SERIAL NUMBER
DSN
is the DATASET NAME

Together these fields show the type of error that occurred, the job and step that abended, and the file that caused the problem (pinpointed by the device address, volume serial number, and dataset name).

The system abend code may also appear in both the JES2 job log (ABEND Sxxx) and in the JCL listing (COMPLETION CODE SYSTEM=xxx).

For more information and for codes not included in this document, see the MVS/ESA SYSTEM CODES manual and the MVS/ESA SYSTEM MESSAGES VOLUME 2: IEA - IEE manual. These manuals are available for reference at the Help Desk, located in M-3 Martin Hall.

001

An I/O error condition was encountered. This could be the result of trying to read more data than was supplied to the program. This code also appears when the LRECL and BLKSIZE in the DD statement differ from the logical record length and blocksize that occur in the dataset.

Make sure you are providing the correct amount of data. When using COBOL, make sure that the file description in the file section is the same as the actual dataset. If the dataset is blocked, be sure to specify BLOCK CONTAINS x RECORDS in the file description.

002

The error occurred while processing a sequential dataset. This code is accompanied by the message IEC036I and appears in this message in the form 002-xx, where xx is one of the following return codes:

04
The dataset consists of variable format records, and the length is less than 4 or greater than the LRECL value that was specified when the dataset was opened. This code also occurs when segments of variable spanned records are not in sequence. Ensure that the LRECL includes the maximum data length plus 4.
08
The record or block length plus the key length and the required overhead add up to more than 32,767 bytes. Verify that the record size passed to the access method is correct.
0C
The record or block length plus the key length and required overhead is greater than the track capacity. Use a smaller blocksize, or specify track overflow.
10
The dataset uses the track overflow feature; the LRECL specifies a length greater than 32,752. Verify that the record size passed to the access method is correct.
14
The record length is greater than the blocksize specified in the DCB. Verify that the record size passed to the access method is correct. Increase the blocksize to accommodate the largest logical record.
1C
The error occurred during the creation of a direct access dataset. A record is larger than track capacity, and the record format does not use the track overflow feature. Use a smaller blocksize, or specify track overflow.
20
During creation of a direct access dataset, a secondary extent was requested. The block will not fit on the amount of space allocated for the secondary extent. Allocate a larger primary or secondary extent or specify a smaller blocksize.
24
During creation of a direct access dataset, an attempt was made to write out a block larger than the primary extent on the pre-allocated dataset. This could also occur if allocation of the primary extent was split and any of the secondary extents were smaller than the block. Allocate a larger primary or secondary extent or specify a smaller blocksize.
28
During creation of a direct access dataset, an attempt was made to OPEN with a blocksize that was larger than the primary extent. Allocate a larger primary or secondary extent or specify a smaller blocksize.
2C
Too many tracks were specified for cylinder overflow, or the DCB BLKSIZE is not a multiple of DCB LRECL. Specify the CONTIG subparameter on the SPACE parameter, or correct the DCB BLKSIZE.

013

The error occurred during the execution of an OPEN macro instruction. This code is accompanied by the message IEC141I and appears in this message in the form 013-xx, where xx is one of the following return codes:

04
American National Standard (ANS) labels were specified in the LABEL parameter of the DD statement but are not supported by the system. Correct the LABEL parameter of the DD statement.
08
American National Standard (ANS) labels were specified in the LABEL parameter of the DD statement, and the UNIT parameter specified a 7-track tape drive. ANS labels are valid only for nine-track tape drives. Our system has only nine-track tape drives.
18
The DSN parameter on the DD statement specified a member of a partitioned dataset that could not be located. Make sure that you specify the correct member name and that the particular member does exist in the specified partitioned dataset.
1C
An I/O error was encountered when searching the directory of a partitioned dataset. The directory of your partitioned dataset is unusable. Re-create or restore the partitioned dataset.
20
For a sequential dataset, the BLKSIZE is not a multiple of LRECL, LRECL=0 when RECFM=FB or FBS, or BLKSIZE is not 4 bytes greater than LRECL when RECFM=VB. Correct BLKSIZE to be an integer multiple of LRECL if RECFM=FB or make BLKSIZE four bytes larger than LRECL if RECFM=VB.
60
The BLKSIZE is not equal to LRECL for a dataset with a DCB specifying RECFM=F. Correct the DCB parameters to specify RECFM=FB or make LRECL=BLKSIZE.
68
The DCB for a dataset specified a BLKSIZE greater than the maximum (32,760). Decrease your BLKSIZE to 32,760 or less.
8C
RECFM was not specified for a direct organization (BDAM) dataset. Specify the correct RECFM in the DCB.
A4
A DCB was opened for a SYSIN or SYSOUT dataset but DSORG was not PS. Change the DCB parameter to DSORG=PS.
A8
An invalid record format was requested for a SYSIN or SYSOUT dataset. Either RECFM=D was specified, or RECFM=VS or VBS was specified for a SYSIN dataset. Change RECFM to something other than D, VS, or VBS.

0C1

OPERATION EXCEPTION. An OP CODE is not assigned or the assigned operation is not available at this installation. In FORTRAN, check for unmatched lengths of COMMON blocks. For COBOL or ASSEMBLER, check for writing to an unopened or closed output file. For COBOL, check for misspelled or missing DDNAMES; for every ASSIGN there must be a matching DD statement.

0C2

PRIVILEGED-OPERATION EXCEPTION. You cannot use the OP CODE specified; it is a privileged instruction.

0C4

PROTECTION EXCEPTION. A virtual address could not be translated into a real address. You tried to access a storage location that is not available to your program. Check the spelling of variable names, for zero or negative subscripts, and check for subscripts that may exceed the dimension size of an array.

0C7

DATA EXCEPTION. The sign or digit codes of operands in decimal arithmetic, editing operations, or in convert to binary are incorrect, or fields in decimal arithmetic overlap incorrectly.

You have an invalid packed decimal number; the sign code is invalid or missing, or a non-decimal character appears in the digit code portion of the number.

Make sure your addresses point to the beginning of the packed decimal number and be sure to use the correct lengths. The low order bytes of overlapping fields must coincide. Also make sure that you have properly initialized packed decimal numbers (for example, COMP-3 in COBOL). For COBOL, non-numeric data in a numeric field was being used arithmetically, or a field with non-numeric data was transferred to a numeric specified area.

0C8

FIXED-POINT OVERFLOW EXCEPTION. This occurs when a fixed-point number becomes so large that the high-order significant digits are lost because there is no place for these digits to be stored.

0C9

FIXED-POINT DIVIDE EXCEPTION. This is caused by an excessively large fixed-point number obtained as the result of a decimal division operation. You may have tried to divide by zero or convert a packed decimal number of more than eight significant digits to binary. You may have divided by a number so small that the quotient was too large to fit in the register reserved for it.

0CA

DECIMAL-OVERFLOW EXCEPTION. The destination field is too small to contain the result of a decimal operation.

0CB

DECIMAL-DIVIDE EXCEPTION. A quotient exceeds the specified data field size, or an attempt was made to divide by zero.

222

The operator canceled your job for one of the following reasons:

  1. it was waiting for resources that were not immediately available. Resubmit the job.

  2. it appeared to be in a loop. Check your program logic to make sure there are not infinite loops.

  3. it was canceled to correct a system interlock condition. Resubmit the job.

  4. it may have violated a procedure established for our installation. Contact DCIT for assistance.

  5. it was canceled for any other reason(s) specified in the message from the operator in your job log. Use this information to determine the appropriate action to take.

322

Execution of job, job step, or catalogued procedure step took longer than the time specified in the time parameter of the JOB statement, or execution took longer than the system default value.

Check your program logic for infinite loops; if no errors are found, specify more time in your JOB statement.

722

The specified SYSOUT (lines and/or cards) limit was exceeded.

Check for any I/O loops in your program to be certain you are not getting unwanted printed or plot (cards) output. If you need more lines or cards, then increase the lines or cards parameter on your JOBPARM statement.

806

The program to be executed was not found in a specified private library, job library, or link library; or an uncorrectable I/O error occurred which may be the result of an uninitialized partitioned dataset.

Make sure the specified library contains the requested program or subroutine. Make sure that the specified PDS is initialized. Check for correct spelling of program and library names.

80A

There was space available to load your program, but not enough space to run it. If you have a REGION parameter on your JOB statement or on your EXEC statement, and it is less than 32M, remove it. The default REGION size is 32M.

913

The error occurred during an open or during end-of-volume for a RACF protected dataset. This code is accompanied by the message IEC150I and appears in this message in the form 913-xx, where xx is one of the following return codes:

04,08
A detection was made when opening a magnetic tape dataset with American National Standard (ANS) labels that indicates the label was not written on an IBM-compatible system or that it was written by the user. Make sure that the correct volume is mounted; if so, it must be re-created for use on an IBM-compatible system.
0C
An OPEN was issued for a RACF protected dataset but your userid did not have the proper RACF authority for that dataset. See O292 "RACF and Datasets" for more information. Note: You may also receive a 913 for other RACF errors. Contact the Help Desk for assistance.
10
An unauthorized job step or job step task attempted to OPEN a VTOC for output processing.
18
LABEL=BLP (Bypass Label Processing) was indicated and the task was not authorized. Make sure that you have specified CLASS=T on your JOB statement. Systems must authorize your use of BLP.
1C
A direct access dataset was not available to the job because
  1. the dataset was opened for input and some other job had exclusive control of the dataset (DISP=OLD or MOD), or
  2. the dataset was opened with DISP=OLD or MOD and some other job was using the dataset.
2C
An OPEN or OPEN TYPE=J was issued to an ISAM dataset defined by two or three DD statements. Either the dataset names were not all the same or the JFCB passed to OPEN TYPE=J has a dataset name different from that coded on the DD statement. Correct the dataset name on the DD statement(s) or do not alter the dataset name in the JFCB before issuing the OPEN TYPE=J.
30
An OPEN was issued to write a dataset on magnetic tape containing one or more previous datasets. The protection mode of the dataset to be written was different than the protection mode of the previous dataset. All datasets on a tape volume must have the same security level. Change the security level to match the previous dataset(s) and rerun the job.

B37

The error occurred during end-of-volume. This code is accompanied by the message IEC030I and appears in the message in the form B37-04. For an output dataset on a direct access device, the error occurred because (1) no more space was available on the volume, or (2) the dataset already had 16 extents, but required more space.

D37

The error occurred when an output operation to a direct access device was specified. This code is accompanied by the message IEC031I and appears in this message in the form D37-04. A dataset opened for OUTPUT used all the primary space and no secondary space was requested.

Either re-create the dataset specifying more space on the DD statement or compress the partitioned dataset to free embedded space. If the problem persists, contact DCIT.

E37

The error occurred when an output operation was requested for a dataset on a direct access or magnetic tape device. This code is accompanied by the message IEC032I and appears in this message in the form E37-xx, where xx is one of the following return codes:

04
A dataset opened for OUTPUT used all space available to or on the current volume, and no more volumes were available. Not enough volumes were specified for the dataset through the SER, volume count, or REF subparameter of the VOL parameter in the DD statement. For a partitioned dataset (PDS) on a direct access device, all space was filled when the program attempted to write another record (A PDS can reside only on one volume). Change your JCL to provide more volumes. In the case of a PDS, specify a different volume. For MAKEDS-created datasets, you have reached your size limit. Compress the dataset to get back unused space. If the compress still does not give you enough space, you will have to request (via the CRS command or on the CRS Web Page) that the dataset be enlarged.
08
A multi-volume physical sequential dataset was being written on a direct access device. All space was filled on the volume, and an attempt was made to obtain space on the next specified volume. Either the space was not available on that volume or the dataset already existed on that volume. Either specify a new volume to continue the dataset or make sure that enough space is available on both of the current volumes. Make sure the dataset does not already exist.