abends reference

8/12/2019 Abends Reference

1/17


2/17

o RECFM=F was specified and the logical record length was not the sameas the block size.

Solution:

o Check the DCB attributes of the problem data set and correct anyinconsistencies. Check for inconsistencies between the program, the JCL,

and the data set DCB characteristics.o Verify that all the DCB information required for the data set is specified.o Recreate the partitioned data set specifying a value for directory blocks in

the space parameter.

o Specify a BLKSIZE that matches the program DCB information.o Check the spelling for any programs to be executed.o Verify that the appropriate STEPLIB data sets have been provided.

S002

Possible causes:

o An error occurred in processing a sequential or indexed sequential dataset, or in creating a direct access data set.

o The record being processed exceeded the allowable size.An error occurred in reading a sequential data set.

o The variable record length was less than 4.o

The LRECL was greater than the DCB record length.o An error occurred in sequential processing of variable length spanned

records which were not in sequence.

o In writing to a sequential or direct access data set, the record length wasgreater than 32,767 bytes.

o In writing to a sequential or direct access data set, the record length wasgreater than the track capacity.

o In writing to a sequential or direct access data set, the variable lengthrecord was longer than 32,752 bytes (the data set used track overflow).

o In writing to a sequential or direct access data set, the record lengthexceeded the DCB block size.

o In writing to a sequential data set with variable length records, an invalidlength field was encountered:1. It was less than 4 (or 5 with ASA control characters)

2. It was greater than the DCB blocksize or 32,767 bytes.

o An error occurred in writing a record longer than the track capacity (thedata set did not use track overflow).


3/17

o An error occurred in obtaining a secondary extent, when writing to a directaccess file. There was not enough secondary space to hold the block being

written.

Other causes:

An error occurred in writing a block larger than the primary extent on the pre-

allocated direct access data set in opening a direct data set, it was determined thatthe blocksize was larger than the primary extent.

An error occurred in opening an indexed sequential data set:1. Too many tracks were requested for cylinder overflow.

2. The DCB BLKSIZE was not a multiple of the DCB LRECL.

Solution:

1. Change the JCL and/or program DCB information to be consistent with that of

the data set.

2. Recreate the data set specifying the correct DCB information.3. Recreate the data set so that the spanned records are in the correct sequence.

4. Verify the record definition, particularly the number of occurrences in an

occurs clause.

5. If the record length exceeds the track length, specify a different device in theunit parameter.

S03B

An error occurred in opening an indexed sequential data set.

Possible causes:

1. A write to the data set was attempted when DISP=SHR was coded in the JCL.

2. A write to the file was attempted when it was not opened for output.3. The data set was not created or it was not closed after it was created.

4. The block sizes or logical record lengths in the program were inconsistent withthe JCL.

5. The data set was already open.


4/17


5/17

S031

An error occurred while sequentially processing an indexed sequential

data set.

Possible causes:

1. A stop run or goback was executed before a data set was closed.

2. An out-of-sequence or duplicate key was detected while loading the data set.3. An attempt was made to write an invalid length record or block.

4. There was a hardware malfunction.

5. The recording medium was defective.

Solution

1. Change the program logic so that the data set is closed before the stop run orgoback is executed.

2. Recreate the data set ensuring that the keys are in proper sequence.

3. Be sure that the JCL LRECL is consistent with the program and data set label.

S04E

DB2 related abend. Check the messages in SYSPRINT.

Possible causes & Solution:

oResource unavailable.

o A decimal packed field contained non-numeric data when an INSERT oran UPDATE SQL statement was executed.

o An SQL WHERE clause in a cursor contains a packed numeric workingstorage field that contains non-numeric data when the OPEN CURSOR

statement is executed. Initialize the field or remove it from the SQL

statement if not used.

S0CAThe result of an arithmetic operation was too large for the receiving field.


1. An attempt was made to divide by too small of a number. 2. An attempt was

made to multiply by too large of a number.3. A program loop containing an arithmetic instruction caused an invalid result.


6/17

S0CB

An invalid divide was attempted.


1. The divisor was zero.

2. The quotient exceeded the allowed data field size.

1. Determine why the divisor is zero.

2. Expand the size of the dividend field, or reduce the size of the divisor field.Note: a comp-3 field may not exceed 15 digits.

S0C1

The current machine instruction was invalid.


1. A JCL DD statement was either invalid or missing.

2. An attempt was made to open a data set which was already open.

3. A read/write was attempted to an unopened data set.4. An attempt was made to execute a subroutine which was not link edited into

the load module.5. The select clause was invalid for an isam data set.

S0C2


The current machine instruction was invalid.


2. An attempt was made to open a data set that was already open.

3. A read/write was attempted to an unopened data set.

4. The select clause in the file-control paragraph did not specify an indexsequential data set, when in fact the data set was indexed sequential.

5. A subscript or index contained an invalid value.


7/17


8/17

S0C6

An attempt was made to execute a machine instruction which had invalidoperands.


1. The program fields and/or data sets were incorrectly defined.

2. A multiplier or divisor was too large.3. A subscript or index contained an invalid value.


5. The blocksize and record size were specified as equal for variable length

records.6. An attempt was made read/write to an unopened data set.

7. An attempt was made to read after end-of-file.

8. A stop run occurred before all opened data sets were closed.B.

In the input or output procedure of a sort.

9. An attempt was made to reference an input/output area, but no open or read hadoccurred for the data set.

10. Invalid parameters were passed through the linkage section.

11. The file-control select clause was missing for the data set that was being

processed.

S0C7

A numeric field contained non-numeric data.


1. Numeric data was not initialized.2. A subscript or index contained an invalid value.

3. A comp-3 field had an invalid sign.

4. A group move overlaid a numeric field with non-numeric data.

S0C8

The result of an arithmetic operation was too large for the receiving field.



9/17

1. An attempt was made to divide by too small of a number.

2. An attempt was made to multiply by too large of a number.

3. A program loop containing an arithmetic instruction caused an invalid result.

S0C9

A division gave a quotient which was too large for the program defined

field.


1. An attempt was made to divide by zero.

2. An attempt was made to divide by too small of a number.

3. A program loop containing an arithmetic instruction caused an invalid result.

4. A sort operation was missing a SORTIN or SORTOUT JCL DD card.

An error occurred in end-of-volume processing on a magnetic tape volume.

1. An error occurred in header or trailer label processing.2. An error occurred in positioning the magnetic tape.


An I/O error occurred while writing a tapemark or an end-of-volume label.An I/O error occurred while the tape was being positioned for label processing an

I/O error occurred in reading the trailer label of an input or inout data set.

An I/O error occurred while positioning at the end of a magnetic tape volume.

An I/O error occurred in reading the header label for an input or inout data set.An I/O error occurred while positioning for the first data record of a magnetic

tape data set.An invalid trailer label was encountered in end-of-volume processing.An invalid header label was encountered in end-of-volume processing.

A specific vol=ser was specified for a multi-volume output data set.

One of the volumes contained a data set whose expiration date had not yetpassed.

1. Resubmit the job specifying a different volume or device.

If this does not correct the problem, recreate the data set on a different volume or

device.Recreate the data set on a different volume or device.

For multi-volume data sets, be sure the labeling is consistent.

1. If the label format is incorrect, recreate the data set and resubmit the job.2. If the label appears correct, specify a different volume or device.

If there is not a tapemark after the data, recreate the data set, specifying a different

volume or device.1. If the label format is incorrect, recreate the data set and resubmit the job.

2. If the label appears correct, specify a different volume or device.

3. For multi-volume data sets, recreate the data set, ensuring that the labeling is

consistent.


10/17

1. Verify that the data on the data set appears correct. If so, specify a different

volume or device, and recreate the data set.

2. If there is no data on the data set, recreate the data set, and resubmit the job.

1. If the trailer label is invalid, recreate the data set, and resubmit the job.

For multi-volume data sets, be sure that the labeling is consistent.2. If the label appears correct, specify a different device.If this does not correct the problem, recreate the data set on a different volume.

1. If the header label is invalid, recreate the data set, and resubmit the job.

For multi-volume data sets, be sure that the labeling is consistent.2. If the label appears correct, specify a different device.

If this does not correct the problem, recreate the data set on a different volume.

If the correct volume was definitely specified, tell the operator that the volume is

to be used even though the expiration date has not passed.

S213

An error occurred in opening a data set on a direct access device.


1. A specific data set could not be located.

2. DISP=OLD or DISP=SHR was specified for an output data set.

3. DISP=MOD was specified but the data set did not exist.

1. Ensure that the data set name and volume serial number are correct and that the

disposition of the data set is consistent with its usage.2. If a data set is used from a preceding job step, be sure that the data set was

created and passed correctly.

S214

An error occurred in volume disposition or in tape positioning when

closing a magnetic tape data set.


1. There was an invalid user label.2. There was no tapemark following the data.

3. A hardware error occurred.


1. Verify that the label formats are correct.

If they are invalid, recreate the data set.2. Determine if there is a tapemark following the data.


11/17

If not, recreate the data set.

3. Rerun the job specifying a different volume or device.

S237

An error occurred in end-of-volume processing of a magnetic tape data set.


1. The block count of the tape label did not agree with that of the DCB.One or more blocks may have been skipped during processing.

2. An incorrect volume serial number was specified in the volume parameter of

the DD statement.

3. An incorrect volume was mounted.4. The DSN was misspelled.

1. Verify that the DSN is spelled correctly, and that the correct volume(s) arespecified and mounted. Correct any errors, and resubmit the job.

2. If all the data set information appears correct, resubmit the job specifying a

different device in the unit parameter of the JCL.If this does not correct the error, re-create the data set.

S314

An input/output error occurred in closing a data set on a direct access device.

Possible causes:The volume or the device was defective.

Resolution:Rerun the job specifying another volume or device.

S322

Description: The time limit was exceeded for a job or job step.

Possible causes:

1. An endless loop occurred in the executing program.2. The time parameter on the job card did not allow enough time for the job to

complete.3. The time parameter on the exec card did not allow enough time for the step to

complete.

4. If the time parameter was not specified, the default time limit was exceeded.


12/17

Resolution:1. Check for program errors, especially endless loops that cause the job or job stepto exceed the time limit.

2. Verify that the time limits for the given job are realistic.

If necessary, specify a longer time in the time parameter, and rerun the job.

S30A

Memory error1. The EZTVFM file is not large enough for the report being generated.

2. You have a subscript or index that is going out-of-bounds on an table or occurs

clause .3. A file or table size is greater than the JCL/file LRECL.

4. DCB mismatch.

S413

An error occurred in opening either a direct access or a magnetic tape data set.1. An input/output error occurred in processing a tape data set.

2. The specified data set could not be located.

3. The label or DCB parameters were incorrect.

4. A requested device was unavailable.

1. No unit was available for mounting the volume which contained the data set

being opened.2. The volume on the allocated unit (as specified by ser) could not be demountedbecause it was either reserved or permanently resident.

The volume serial number was not specified on the DD statement for a data set

which was opened for input.An invalid volume sequence number in the JCL specified a value greater than the

number of volumes contained on the data set.

An error occurred while opening a magnetic tape data set.

The density specified in the DEN subparameter was incompatible with therecording density of the device allocated.

An error was caused by a subsystem interface problem.

The mass storage system did not mount the requested volume.Tape data set sequence number was specified greater than 1, but the volume

serial number did not specify a tape data set.

1. Verify that the JCL is correct.2. Rerun the job specifying a new volume or device.

Specify another device in the unit parameter of the DD statement. Determine how

many volumes the data set spans, and request the appropriate volume.


13/17

S513

An error occurred in opening two data sets on the same magnetic tape volume.This only works with SYSOUT data sets.

1. Two data sets were assigned to the same device.

2. An open was issued for a second data set on the same tape device before thefirst one was closed.

1. Verify that the JCL is correct

2. Check the file usage in the program.

S522

The wait time limit was exceeded for a job or job step.

1. The operator did not respond to a console request.2. The program was waiting for a resource that was not available at execution

time.3. The CPU resource was not available at execution time.

4. The user request was invalid.

1. Check with the operator to determine if there were any outstanding requests for

your job.2. Check with the operator to determine if there were any problem jobs running at

the same time as yours.

S613

An error occurred in tape related input/output.1. The JCL DD statement was incorrect.2. An input/output error occurred in label processing.

3. The standard header labels were missing for an input data set.

4. There was a hardware malfunction.

An error occurred in tape positioning.An error occurred in reading a tape label.

The tape label was invalid.

An error occurred in writing a tape label.An error occurred in writing a tapemark after the header labels.

1. Verify that the JCL specifies the correct volume and device.

2. Verify that the volume contains standard labels.3. Resubmit the job specifying a different volume or device.

S637

An error occurred in end-of-volume processing.

An input/output error was encountered in1. Writing a tapemark.


14/17

2. Positioning the tape.

3. Reading a label.4. Sensing for a file protection ring.

An error occurred in either:

1. Reading a tape label.

2. Writing a tapemark.3. Positioning a tape volume. The user trailer label processing caused a tape

positioning error.

Data sets with unlike attributes were concatenated.A tape positioning error occurred for a data set to be read backwards.

If the tape contained labels, the error occurred in positioning the labels;

otherwise, the error occurred in positioning the data. The error occurred in theopen instruction with the leave option specified.

An error occurred in tape positioning for a data set using the reread option.

An error occurred while rewinding a tape prior to verifying the volume label.

An error occurred in reading a tape volume label.

An error occurred because the tape had nonstandard labels or none at all.An error occurred while positioning at the labels, (or if there were no labels, while

positioning at the data) of a concatenated data set.An error occurred while positioning at the labels, (or if there were no labels, while

positioning at the data) of a data set opened with input or inout to be read forward.

An I/O error occurred in sensing for a file protection ring.An error occurred in tape positioning following header label processing.

1. Check the JCL for any inconsistencies in the label, the vol=ser, or the dsn.

2. Rerun the job specifying another volume or device.

3. Make sure that the file protection ring is available for an output data set.

S706

A non-executable load module was requested by the program. The module did not

link edit successfully.

Link edit the offending module again, and resubmit the job.

S713

An error occurred in opening a data set on tape.

1. An attempt was made to output to the data set, before the expiration date

specified had been reached.

2. The incorrect volume was requested.

1. Verify that the correct data set and volume will be accessed.


15/17

S714

An error occurred in closing a tape data set.1. An I/O error occurred while writing a trailer label or tapemark.

Rerun the job specifying another volume or device.

S722

The maximum number or output lines has been exceeded.

1. The program contained an invalid write loop.

2. The number of output lines was underestimated in the JCL.

1. Check for and fix program logic error causing a loop.

S80A

The storage needed to execute the program was not available.1. The region parameter did not specify enough storage.2. The region parameter was omitted, and the default storage amount was too

small to run the correct program.

3. Block sizes were increased or buffers were added, and the region size was not

increased.

4. A logic error caused excessive storage to be obtained but not freed.

1. Increase the region size.

2. Look for logic errors which may cause excessive calls to other programs or

requests for storage.

S804

The storage needed to execute the program was not available.

1. The region parameter did not specify enough storage.

2. The region parameter was omitted, and the default storage amount was toosmall to run the correct program.

3. Block sizes were increased or buffers were added, and the region size was notincreased.

4. A logic error caused excessive storage to be obtained but not freed.

1.

Increase the region size.2. Look for logic errors which may cause excessive f calls to other programs

or requests for storage.


16/17

S806

A module requested by the program could not be found.1. The module requested did not exist in the data sets specified in the STEPLIB or

JOBLIB.

2. A JCL STEPLIB or JOBLIB DD statement was missing or incorrect.3. The module name was misspelled.

4. An I/O error occurred in searching for the module in the library directory.

1. Verify that the correct program is being requested.

2. Ensure that the appropriate STEPLIB or JOBLIB DD statements are in theJCL.

3. If necessary, recreate the data set.

S813

The data set name in the JCL did not match the data set name on the tape.1. The JCL volume serial number was wrong.2. The data set name in the JCL was misspelled.

3. The wrong tape was mounted.

4. The incorrect data set sequence number was specified in the label parameter.5. The data set does not exist on the magnetic tape.

Verify that the JCL is correct, and resubmit the job.

S913

An error occurred in opening a magnetic tape data set.

1. The error occurred during open or end-of-volume processing.The data set was password protected, and a correct password was not entered.

2. The error occurred in opening a checkpoint data set which was concatenated to

a non-checkpoint data set.

1. Supply the correct password, and resubmit the job.

2. Eliminate any concatenations of checkpoint and non-checkpoint data sets.

SA13

An error occurred in opening a tape data set.

1. The file sequence number was wrong on a multi-volume tape data set.2. The file sequence number was wrong, or it was less than that of the first data

set on the tape.3. The volume serial number was wrong.

4. The job which wrote the tape did not write all the data sets.

1. Verify that the JCL is correct, and resubmit the job.

2. If the desired data set does not exist on the tape, recreate the tape.


17/17

abends reference

Documents