Explanation
DFSMSdss allocated
or located the target data set on a DASD device with the indicated
track capacity (track_size). This was done because
the block size of the source data set was less than the track capacity
of the target device. However, during processing, DFSMSdss encountered a data
block (block_size) from the source data set that
was larger than the track capacity of the target device. The data
block cannot be placed on the target device, so the DFSMSdss function fails for
the data set.
This situation can occur only when the track capacity
of the target device is less than that of the source device. DFSMSdss allocates
to such a device only when target volumes of same, like, or larger
track capacity are not specified or are specified but do not have
space available.
System action
The specified data set is not processed. If DFSMSdss allocated
the target data set, it is deleted. The return code is 8.
Operator response
Programmer response
Perform one of the following actions, and
rerun the job:
- Provide DFSMSdss with a target DASD device with
a track capacity large enough to contain the block size specified
in the message, by using OUTDD or OUTDYNAM. Specify only target volumes
that have a track capacity larger than the block size specified in
the message. This includes volumes of the same or a like device type
as the source and any volumes of a device type with a large track
capacity. You must also eliminate the REPLACE or REPLACEUNCONDITIONAL
keyword if a pre-allocated target is located on a device with a smaller
track capacity than the block size indicated in the message.
- pre-allocate a target data set on a volume with a track
capacity large enough to contain the block size specified in the message.
Specify the volume to DFSMSdss by using OUTDD or OUTDYNAM and
use the REPLACE or REPLACEUNCONDITIONAL keyword to force DFSMSdss to
use the pre-allocated target. The target device should meet the conditions
specified in the preceding solution.
- Specify the REBLOCK keyword. If the source data set can be reblocked
and the source data set logical record length is less than the target
track capacity, DFSMSdss reblocks
the data set as it is copied or restored. Certain data sets cannot
be reblocked, so you must use one of the solutions described previously.
You can test whether or not the data set can be reblocked by specifying
REBLOCK and rerunning. If the function fails again, use one of the
preceding solutions.
- If you were performing a COPY, you can update the source VTOC
entry to reflect the block size specified in the message by using
AMASPZAP if you are authorized to use it. When the job is rerun, DFSMSdss selects
a usable target volume based on the updated block size.
Source