Explanation
The error occurred during processing of an OPEN
macro instruction or an OPEN macro instruction with a TYPE=J operand.
In
the message text:
- rc
- Associates this message with system completion code 113 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(member)
- The data set name. Member name if specified.
The explanation for the hex return code is as
follows:
- Return Code
- Explanation
- 08
- A JFCB extension block was needed for processing a physical sequential
data set but none was available.
If this error occurs while the
system is reading a multivolume tape data set and this abend message
is preceded by one of the following messages: IEC709I, IEC710I, IEC711I,
or IEC712I, then the next volser to process was provided via the LABAN
(Label Anomaly Tape Installation Exit) but either this volume serial
could not be enqueued or no JFCB extension is available to add the
volume.
- 0C
- An OPEN TYPE=J was issued, but no JFCB exit was found in the DCB
exit list. Specify a JFCB exit, supply the JFCB.
- 18
- A JFCB extension block was needed for processing a direct or index
sequential data set.
- 20
- An end-of-volume condition was encountered while processing a
VSAM data set. Multi-volume data sets are not supported when a VSAM
data set is opened with a DCB.
- 24
- An OPEN was issued to a multi-volume VSAM data set. Only single-volume
VSAM data sets can be opened with a DCB.
- 28
- An attempt was made to open a concatenated VSAM data set with
a DCB.
- 2C
- An OPEN was issued for a VSAM data set with a DCB, but the caller
was not APF authorized or not in supervisor state.
- 30
- An incorrect JCL disposition was detected for a VSAM data set
being opened with a DCB. The only valid VSAM data set dispositions
are (OLD,KEEP,KEEP) or (SHR,KEEP,KEEP).
- 34
- An unsupported DCB option was specified for a VSAM data set opened
with a DCB. The only valid options are INPUT and UPDAT.
- 38
- An OPEN was issued for a VSAM data set with a DCB, but the format1
DSCB for the data set does not indicate it is a VSAM data set. Ensure
that the DSNAME specified on the DD statement is correct and that
the program supports opening a VSAM data set with a DCB.
- 3C
- An attempt was made to open a VSAM record level sharing(RLS) control
ACB(CTRLACB=YES specified in ACB macro instruction). VSAM RLS Control
ACBs are not supported by open.
- 40
- An error occurred during VSAM record level sharing(RLS) processing
while attempting to open a VSAM data set with a DCB.
- 44
- An attempt was made to open an EAS eligible data set
that has a format 8 DSCB, but the DCBE flag, DCBEEADSCBOK, indicating
that the caller understands extended attribute (Format 8/9) DSCBs
was not set. This restriction applies only to an EXCP DCB or to a
BDAM DCB that has OPTCD=A. The application program did not set EADSCB=OK
in the DCBE macro. The data set was created with the EATTR=OPT option.
Either change the program to handle 28-bit cylinder numbers and code
EADSCB=OK, or use a data set that does not have EATTR=OPT.
- 48
- An attempt was made to open the VTOC on a volume with more than
65,520 cylinders but the DCBE flag, DCBEEADSCBOK, indicating that
the caller understands extended attribute (Format 8/9) DSCBs was not
set.
- 4C
- A non-VSAM DCB or ACB passed to OPEN is associated with an extended
TIOT DD entry (for example: XTIOT). However the DEVSUPxx parmlib member
does not include the keyword and value: NON_VSAM_XTIOT=YES.
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
Correct the error causing the abnormal end
as indicated by the return code in the message text. Rerun the job.
Source
Module
IFG0194A, IFG0194D, IFG0194E, IFG0195V, IGC0001I
Routing code
Descriptor code