Explanation
The error occurred during end-of-volume or during allocation of a secondary quantity of direct access storage as requested in the SPACE parameter of the DD statement for the data set.
- rc
- Associates this message with system completion code 737 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.
- Return Code
- Explanation
- 04
- An I/O error occurred while reading the format-1 DSCB, or the format-1 DSCB for the data set could not be found on the first volume (or the volume indexed by the volume sequence number) specified by the DD statement.
- 08
- An I/O error occurred reading a direct access volume label during end-of-volume processing.
- 0C
- An I/O error occurred reading the DSCB for a concatenated partitioned data set.
- 10
- An I/O error occurred writing a file mark for a data set on a direct access device.
- 14
- An I/O error occurred while reading a DSCB preparing for user trailer label processing.
- 1C
- An I/O error occurred while reading a format-3 DSCB.
- 24
- A missing member name was detected by BLDL while searching for the TTR of a concatenated member.
- 28
- The EOV DA module was passed an error return code in register 15 after issuing the IEFSSREQ macro instruction. This indicates the subsystem (JES3) discovered a functional or logical error that it could not process.
- 2C
- The error occurred when a FEOV macro instruction was issued while attempting to write a file mark at the end of the data. The DCBFDAD field in the DCB indicated an extent number in the DEB greater than the number of extents in the data set. Consequently, it could not be determined where the file mark should have been written.
- 34
- An error occurred during a MOUNT, DEMOUNT, ACQUIRE or RELINQUISH operation on a Mass Storage System (MSS) virtual volume. See message IEC066I.
- 38
- The MSS hardware mounted a virtual volume other than the one requested.
- 3C
- The format-1 DSCB not found installation exit module encountered an error.
- 40
- An I/O error occurred reading the format-1 DSCB, or the format-1 DSCB could not be found on the first volume specified on the DD statement or in the catalog for the next data set in the concatenation.
- 44
- EOV failed when switching to a volume after the first volume of
a data set or any volume in a concatenation because the data set type
is large format sequential but the application program could not access
the whole data set on the volume. All of the following are true:
- The access method is either EXCP or BSAM with the NOTE or POINT function requested.
- BLOCKTOKENSIZE=LARGE is not specified on the DCBE macro.
- The data set has more than 65535 tracks allocated on the volume.
- 45
- EOV failed when switching to a volume after the first volume of
a data set or any volume in a concatenation because the data set type
is large format sequential but the application program could not access
the whole data set on the volume. All of the following are true:
- The access method is EXCP, BSAM or EXCP.
- BLOCKTOKENSIZE=LARGE is not specified on the DCBE macro.
- The data set has more than 65535 tracks allocated on the volume.
- BLOCKTOKENSIZE(REQUIRE) is specified in PARMLIB member IGDSMSxx.
48
- FEOV is not supported when open for output to a compressed format
version 2 data set.
System action
The task ends unless the error can be ignored as specified in the DCB ABEND exit routine. If the error can be ignored, the system attempts to close the DCB before returning to the user.
Operator response
TRACE=SYS,USR,SLIPDCB=DIAGNS=TRACESystem 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.
If the format-1 DSCB could not be found or read (as with return codes 04/40), be sure that the DSNAME and VOLUME parameters on the DD statement are correct. A recovery attempt request can be specified in the DCB ABEND exit routine.
The 28 return code error indicates a subsystem interface problem and your system programmer should be contacted for advice.
If return code is 2C, probable user error. Make sure that the DCBFDAD field is not being corrected before the FEOV macro instruction is issued.
For return code 3C, contact your system support personnel.
For return code 44 or 45, (a) update the DCB to point to a DCBE macro with BLOCKTOKENSIZE=LARGE and if necessary modify the program to handle large format data sets as described in z/OS® Using Data Sets, or (b) if the data set contains 65535 or fewer tracks, ensure the OPEN option is INPUT (with BSAM or EXCP) or UPDAT (with BSAM).
Source
DFSMSdfp
Module
IFG0554C, IFG0552X
Routing code
11
Descriptor code
6