Explanation
The error occurred during processing of an OPEN
macro instruction for a data set on magnetic tape or on a direct access
device.
In the message text:
- rc
- Associates this message with system completion code 413 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.
Note: This is the mounted volume. The
volume serial number is omitted if there is no volume mounted on the
drive.
- mod
- The name of the module in which the error occurred, if it is available.
- dsname(member)
- The data set name. Member name if specified.
The explanation for the hex return code is as
follows:
- Return Code
- Explanation
- 04
- No device is available for mounting the volume containing the
data set to be opened (dsn), or the allocated device is not available
for one of these reasons:
- The volume already on the allocated device, identified in the
ser field of the message text, is permanently resident, reserved,
or enqueued.
- The requested volume is in use elsewhere.
- Another DCB is open on the device and the device is a magnetic
tape.
- The device type is incompatible with the DSORG in the DCB.
Specify another device in the UNIT parameter of the DD statement.
Notes® - This error can occur if you modify the volume serial number in
the JFCB after the device is allocated but before the data set is
opened. In this case, specifying the DEFER subparameter on the UNIT
parameter of the DD statement might solve the problem.
- This error can be caused by a previous abnormal termination associated
with the same device in the same step. In this case, correct the
error that caused the previous abnormal termination.
- 08
- If this message is not preceded by an IEC710I, IEC711I or IEC712I
message, an I/O error occurred when positioning a magnetic tape volume.
If this message is preceded by an IEC710I, IEC711I or IEC712I message,
the label anomaly exit routine of your installation caused this ABEND.
In the latter case, the system called this exit because of the condition
described in that message.
- 0C
- An I/O error occurred reading the volume label on a magnetic tape
volume or the operator replied 'A' to message IEC514D after a label
error.
- 10
- An I/O error occurred writing a tape mark.
- 18
- The specified data set was opened for input, but no volume serial
number was specified on the DD statement. A recovery attempt request
may be specified in the DCB ABEND exit routine.
- 1C
- An OPEN macro instruction was issued for a data set, but volume
sequence number on the associated DD statement was greater than the
number of volumes containing the data set.
- 20
- One of the following is true:
- An I/O error occurred while reading the volume label on a direct
access volume.
- The label is incorrect.
- An I/O error occurred while reading the format-4 DSCB.
- The format-4 DSCB in the VTOC is incorrect.
- 24
- An OPEN macro instruction was issued for a data set on magnetic
tape. A density was specified in the DCB DEN parameter which was incompatible
with the recording density of the drive allocated to the data set.
Change the DD statement to specify a tape drive with the recording
density specified in the DCB macro instruction.
- 28
- The OPEN DA volume verification module was passed an error return
code in register 15 after issuing the IEFSSREQ macro instruction.
This code indicates the subsystem discovered a functional or logical
error that it could not process.
- 2C
- An error occurred during MOUNT, DEMOUNT, ACQUIRE, or RELINQUISH
operation on an Mass Storage System (MSS) virtual volume.
- 30
- The MSS hardware mounted a virtual volume other than the one requested.
- 34
- LABEL=(n) was specified, where n is greater than 1, and vol=ser
was not specified for a tape data set.
- 38
- During a Read Block ID command to establish the tape position,
an error occurred.
- 3C
- Open detected a bad return code from the Extended Cache Attribute
Selection Facility (CASF).
- 40
- The device does not support the recording mode requested by the
user or determined by the system.
- 44
- The tape volume does not conform to the single recording mode
rules. For input data sets, the violation has occurred during a previous
process in which the rules could not be enforced. For output data
sets, no violation has yet occurred, since the abend prevents this
from happening.
- 48
- A JFCB contained a data set name of blanks. The address of this
JFCB was found during both OPEN TYPE=J processing in the DCB exit
list for a RDJFCB and OPEN TYPE=J,SVC processing.
- 4C
- The job file control block (JFCB) contained an expiration date
of X'FFFFFF', which indicates that expiration date checking
should be bypassed by open processing. However, the application is
not APF authorized, and expiration date checking can only be bypassed
by APF authorized applications. The JFCB address was found during
OPEN TYPE=J processing in the device control block (DCB).
- 50
- Invalid return code from an OCE Tape Installation Exit. See IEC998I
for name of specific exit and value of not valid return code.
- 54
- An OPENJ macro instruction was issued for a data set, but the
volume sequence number in the JFCB provided by the application was
greater than the maximum allowed of 255.
- 58
- The last known volume for the data set could not be located while
reading a multivolume tape data set backward.
- 5C
- The first known volume for the data set could not be located while
reading a multivolume tape data set forward.
- 60
- The task attempted to reprocess a tape volume serial number that
was previously dequeued as requested in JCL DD parameter FREEVOL=EOV
when using the same DD statement.
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
Probable user error unless an I/O error
has occurred. Correct the errors causing abnormal termination as indicated
by the return code in the message text. Rerun the job. The 28 return
code error indicates a subsystem interface problem and your system
programmer should be contacted for advice.
Source
Module
Routing code
Descriptor code