Explanation
The error occurred during processing of an OPEN
macro instruction for a data set on magnetic tape.
In the message
text:
- rc
- Associates this message with system completion code A13 and with
the return code.
- jjj
- The job name.
- sss
- The step name.
- ddname[-#]
- DDname (followed by a concatenation number if it is part of a
concatenation and not the first DD statement in the concatenation).
- dev
- The device number.
- ser
- The volume serial number.
- mod
- The name of the module in which the error occurred.
- dsname
- The data set name.
The explanation for the hex return code is as
follows:
- Return Code
- Explanation
- 04
- An unexpected load point was encountered while positioning a tape.
For NL tape this is probably a user error associated with the use
of multivolume multifile NL tape. Check the file sequence number
and whether the tape was demounted during the job.
- 08
- The requested file sequence number is less than that of the first
file on the SL or AL tape during an open to the start of the file.
Probable user error. Check the file sequence number and volume serial
numbers.
- 0C
- The requested file sequence number is less than that of the first
file on the SL or AL tape during an open to the end of a file. Probable
user error. Check the file sequence number and volume serial numbers.
- 10
- A tape mark was read instead of a HDR1 label while forward spacing
to the desired file on an SL or AL tape. Thus, the multifile tape
ends before the desired file. When positioning to the end of file
1, this means the vol label is followed by a tape mark. Probable user
error. Check the file sequence number and volume serial numbers and
that the job that wrote the tape wrote all the files.
- 14
- A tape mark was read instead of HDR1 label while opening for input
to the start of the desired file on an SL or AL tape. Thus, the tape
ends just before the desired file. Probable user error. Check the
file sequence number and volume serial numbers and that the job that
wrote the tape wrote all the files.
- 18
- An EOV1 label was read on the last SL or AL tape volume while
forward spacing to the desired file or just before the desired file.
There are two possible conditions:
- If opening to the end of the file, it could not be treated as
the end of the data set because it was for a previous file sequence
number. Probable user error.
- If the user is trying to extend a data set that had abended during
EOV, it is necessary to specify a volume count on the DISP=MOD DD
statement. This volume count must exceed the number of known volumes
for the data set.
System action
The task is ended unless the error is to be ignored
as specified in the DCB ABEND exit routine.
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
The three most common causes of this problem
are:
- Invalid volume refer backs where the DD statement referred-back-to
has extended to a new volume.
- EOV Abends (ABENDX37) occurred the last time this data set was
updated. This would cause the last tape in the data set to be left
with EOV labels instead of EOF labels.
- The wrong VOLSER is specified as the last VOLSER in the data set.
Probable user error. Correct the errors causing abnormal
end as indicated by the return code in the message text. Rerun the
job.
Source
Module
Routing code
Descriptor code