Explanation
The error occurred when the end of a data set was
reached.
In the message text:
- rc
- Associates this message with system completion code 337 and with
the return code.
- jjj
- Job name.
- sss
- Step name.
- ddname[-#]
- DDname (followed by a concatenation number if it is part of a
physical sequential concatenated data set and not the first DD statement
in the concatenation).
- dev
- Device number.
- ser
- Volume serial number.
- mod
- The name of the module in which the error occurred.
- dsname(member)
- Data set name. Member name if specified.
The explanation of the hex return code is as
follows:
- Return Code
- Explanation
- 04
- The end of a data set was reached, but no end- of-data-set routine
(EODAD) was specified in the DCB or DCBE. The EODAD routine pointer
in the DCBE is ignored when the DCBE is not in the same storage key
in which the OPEN was issued.
- 08
- No EODAD specified in the DCB for DD DUMMY data set.
System action
Operator response
Start a generalized trace facility (GTF) trace,
and re-create the problem. Reply to message AHL100A with:
TRACE=SYS,USR,SLIP
On
the DD statement for the data set in error, specify:
DCB=DIAGNS=TRACE
System programmer response
If the error recurs and the program
is not in error, look at the messages in the job log for more information.
Search problem reporting data bases for a fix for the problem. If
no fix exists, contact the IBM® Support
Center. Provide the SYSOUT output for the job.
Programmer response
Probable user error. Correct the errors
causing the abnormal end as indicated by the return code in the message
text. Then rerun the job.
Source
Module
Routing code
Descriptor code