Explanation
The error occurred during end-of-volume.
In
the message text:
- rc
- Associates this message with system completion code B37 and with
the return code.
- jjj
- jobname
- 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.
- diagcode
- The DADSM Extend diagnostic code, if available.
- 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
- 04
- During end-of-volume processing, one of the following occurred:
- For an output data set, all space was used on the current volume
and no more volumes were specified.
- The system had to demount a volume in order to mount the next
volume of the data set. It was unable to demount the volume for one
of the following reasons:
- The volume was permanently resident
- The volume was reserved
- Another job had data sets allocated on the volume
- There were open data sets on the volume for the failing task.
For an output data set on a direct access device, the system
might have needed to demount the volume for one of the following reasons:
- No more space was available on the volume.
- The data set already had the maximum number of extents, but required
more space. The maximum number of extents on each volume for basic
format, large format and partitioned (PDS) data sets is 16. The maximum
number of extents on each volume for extended format or a PDSE is
123.
- The data set has reached the maximum number of tracks
per volume. For basic format and partitioned (PDS) data sets, the
limit is 65,535 tracks. For large format data sets, the limit is 16,777,215
tracks. For extended format and PDSE, the limit is larger than any
currently supported volume. The theoretical limit for a PDSE is 178,956,970
tracks. The theoretical limit for an extended format data set that
is not compressed format is 2,147,483,646 blocks per volume. The theoretical
limit for a compressed format data set is 1,073,741,823 tracks per
volume. These limits are subject to change.
- More space was required, but the volume table of contents (VTOC)
was full. If additional space were allocated, another data set control
block (DSCB) might have been needed, but could not have been written.
For an output data set on magnetic tape, a volume needed
to be demounted because the reflective spot was encountered and more
records were to be written.
For an input data set on more than
one volume, one of the volumes needed to be demounted so that the
next one could be mounted, but the system was unable to demount the
volume.
- 08
- During end-of-volume processing, the system attempted to extend
data set dsname to a volume on which the VSE bit
or the DIRF bit (bits 0 and 5 respectively in the DS4VTOCI byte of
the format-4 DSCB) was set. The VTOC for the volume could not be converted
to standard format for one of the following reasons:
- Two data sets were allocated to the same space on the volume.
- A split cylinder data set was located on cylinder zero, the same
cylinder as the VTOC, or the same cylinder as a non-split cylinder
data set.
- The DADSM VTOC conversion routine had been modified to reject
any space allocation requests on a volume on which the DIRF bit is
set to one. See z/OS DFSMSdfp Diagnosis for
more information.
- Under VSE, the alternate tracks were assigned to cylinder
zero.
- 0C
- The indicated direct access volume ser on device dev was
requested to continue processing the data set, but the unit already
contained 127 users, the maximum number.
System action
The task is ended unless the error is to be ignored
as specified in the DCB ABEND exit routine. If the error is to be
ignored, the system will attempt to close the DCB before returning
to the user.
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. For all cases, allocate
as many units as volumes required.
For return code 04, case
1, specify at least one more volume in the SER, VOL COUNT, or REF
subparameter of the VOLUME parameter of the DD statement.
For
return code 04, case 2a and 2b, if the volume to be demounted is permanently
resident or reserved, set up the JCL to allocate devices that are
removable.
For return code 04, case 2c, change the JCL to request
deferred mounting, or specify more volumes than units to prevent sharing
of required units.
For return code 04, case 2d, rewrite the
program or change the JCL insuring that there are no open data sets
on volumes that must be demounted.
For the next case (first
of 08 return code), scratch one of the data sets that has the overlapping
extent.
For the next case (second of 08 return code), either
scratch or move the split cylinder data set that is causing the error.
For
the next case (third of 08 return code), the VTOC can be converted
by either removing the modification to IGG0325Z or by resetting the
DIRF bit to zero and setting the VSE bit to one and allocating a data
set to the volume.
For the next case (last of 08 return code),
the volume can only be used under z/VSE®.
In
all cases, correct the errors and run the job step again.
Source
Module
Routing code
Descriptor code