Explanation
A recall or recovery of a data set with a DAOPTION
specified was received by DFSMShsm. An error was encountered while
processing the DAOPTION. The preceding ARC1001I message contains the
data set name, operation in progress, and the
reascode.
Reascode has
the following meanings:
- Reascode
- Meaning
- 2
- DAOPTION(SAMETRK) was specified but either the VOLUME specified
has a dif- ferent track length than the track length of the L0 device
on which the data set last existed, or the TOVOLUME specified or the
volume selected for a recover has a different track length than that
of the L0 device on which the data set last existed.
- 4
- DAOPTION(RELTRK) was specified but either the VOLUME specified
has a track length less than the track length of the L0 device on
which the data set last existed, or the TOVOLUME specified or the
volume selected for a recover has a track length less than the track
length than that of the L0 device on which the data set last existed.
- 10
- Data set is to be SMS-managed upon completion of the request.
Only non-SMS-managed data sets are supported in conjunction with the
DAOPTION parameter.
- 13
- DAOPTION(RELBLK) was specified but the data set block size is
greater than 32K.
- 14
- A DAOPTION was specified for a recall or recover command but the
data set organization of the data set specified is not direct access.
- 16
- The data set record format must be fixed or fixed-blocked when
using DAOPTION(RELBLK).
- 18
- DAOPTION(RELBLK) cannot be specified when a data set is to be
restored from a dump copy.
The following reascodes represent
internal DFSMShsm errors.
All errors due to an inconsistent user request are identified in the
previous reascode definitions.
- 20
- DAOPTION(SAMETRK) was specified but the target volume track size
is not equal to the last L0 volume's track size. This indicates an
internal DFSMShsm programming
error.
- 22
- DAOPTION(RELTRK) was specified but the target volume track size
is smaller than the last L0 volume's track size. This indicates an
internal DFSMShsm programming
error.
- 26
- No DAOPTION was specified but the target volume track size is
smaller than the last L0 volume's track size. This indicates an internal DFSMShsm programming
error.
- 28
- This is possibly the result of the user entering a volume(xxxxxx)
with a device type inconsistent with what was specified on the unit(yyyy)
parameter for a directed recall. Otherwise, this indicates an inconsistent
track length mix for the target or last L0 volume.
- 30
- An invalid device type was detected in a BCDS MCT record while DFSMShsm was
recovering a data set. This indicates an internal DFSMShsm programming error.
- 34
- A recover is to be done but an MCC record does exist. This indicates
an internal DFSMShsm programming
error.
System action
The recall or recovery operation ends. DFSMShsm processing
continues.
Programmer response
For reason codes 2, and 4, verify consistency
between DAOPTION and the selected target volume. Retry the function
after corrective actions have been taken.
For reason codes
10, 13, 14, 16 and 18, verify the request and retry the function.
For
reason codes 20, 22, 26, 28, 30 and 34, follow the problem determination
steps.