Explanation
The error occurred during processing of a CLOSE
macro instruction for a data set on magnetic tape.
In the message
text:
- rc
- Associates this message with system completion code X'714' and
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 I/O error occurred writing trailer label 1 for a data set on
magnetic tape during processing of CLOSE macro instruction.
- 08
- An I/O error occurred writing trailer label 2 for a data set on
magnetic tape.
- 0C
- If opened for output processing, an I/O error occurred writing
a tape mark during processing of a CLOSE macro instruction. If opened
for input processing, a previous positioning error has been detected
in volume disposition processing during processing of a CLOSE macro
instruction. A possible cause is that ERP detected a permanent error
and the tape position was unknown.
- 10
- For a QSAM data set, either an I/O error occurred while flushing
the buffers during close processing or a close was issued in the caller's
SYNAD routine.
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
If an I/O error has occurred, a defective
volume or device may be the cause. Save the output from the failing
job to aid in the analysis of the problem.
Rerun the job specifying
a different volume or device. If a scratch volume was being used
when the I/O error occurred, request a different volume. If that
does not solve the problem, request a different device in the UNIT
parameter of the DD statement. If a specific volume is needed, try
requesting a different device in the UNIT parameter of the DD statement.
Rerun the job.
Source
Module
Routing code
Descriptor code