Explanation
The RECOVER command has been issued with the FROMDUMP
parameter, but DFSMShsm has
determined that restore cannot be performed. Message ARC1001I precedes
this message, giving the data set name and the reascode.
The
reascode value
gives the reason the restore cannot be done. Valid values for
reascode are:
- Reascode
- Meaning
- 2
- The device type of the original volume that has been dumped is
not of a similar device type as the target volume of the restore.
- 4
- A read error has occurred in reading the control data set record
describing the source backup or dump volume. See message ARC0184I
preceding this message for the type and key of the record.
Notify
the storage administrator or system programmer.
- 6
- An SMS-managed data set cannot be restored to a non-SMS-managed
volume. The data set being recovered has been determined by ACS routines
to be SMS managed, but the target volume is a non-SMS-managed volume.
- 8
- An error has occurred in allocating the dump VTOC copy data set.
- 10
- The DUMPVOLUME subparameter has been specified for a volume restore,
and the specified dump volume does not contain valid data.
- 14
- An error has occurred in reading the backup or dump VTOC copy
data set.
- 16
- An error has occurred in opening the dump VTOC copy data set.
- 22
- One of the following has occurred: Either the volume on which
the data set is currently cataloged or the volume from which the latest
backup version has been made, does not have a dump VTOC copy data
set to verify that the data set has been dumped to the existing dump
copy.
- The volume specified with the FROMVOLUME parameter has not been
processed by full volume dump, thus does not have a dump VTOC copy
data set to verify that the data set has been dumped to the existing
dump copy.
- No dump copy is found that has the data set restore attribute.
- 24
- An invalid or unsupported device type is found in the control
data set record for the source backup, dump volume, or migration level
1 volume where the VTOC copy data set resides.
- 30
- The data set is not currently cataloged, no backup version exists,
and there is no DUMPVOLUME subparameter provided to indicate what
dump copy is required.
- 32
- DUMPCLASS and DUMPVOLUME parameters has not been specified, and
no dump copy is found that has a retention date other than NOLIMIT.
- 34
- Restore of an unmovable data set has failed because not enough
information is available to preallocate the data set. For an unmovable
data set to be successfully restored by DFSMSdss, the data set must exist on the
target volume before the restore occurs.
- 36
- The DUMPCLASS parameter has been specified, and a dump copy is
not found in the specified dump class, or there is no dump VTOC copy
data set to verify that the data set has been dumped to the existing
dump copy.
- 38
- No VTOC copy data set entry is found for the requested data set.
- 40
- The DUMP generation that has been specified is not found or is
invalid.
- 44
- The DATE parameter has been specified, and no eligible dump copy
is found that meets the specified date requirements.
- 48
- The volume that has been specified with the FROMVOLUME parameter
is not the same as the original dump source volume recorded in the
dump volume (DVL) record.
- 50
- The DUMPVOLUME parameter has been specified, but the dump generation
(DGN) record does not indicate that the specified dump volume contains
part of a valid dump copy for the volume to be restored.
- 52
- The RECOVER data set name command was issued with the FROMDUMP
parameter. The dump volume needed has two or more valid dump copies
stacked on it, of two or more different volumes. DFSMShsm cannot tell which dump
copy is needed; the FROMVOLUME parameter is not specified or is specified
incorrectly; the data set is not cataloged or is migrated, and it
has not been backed up; and the SOURCEVOLUME parameter is not specified
or is specified incorrectly.
- 54
- The DUMPVOLUME parameter has been specified. The DGN record has
been found that lists the specified dump volume. This dump generation
is not listed as a valid dump generation in the MCP record for the
volume to be restored.
- 56
- For a VSAM data set restore of a cluster, the data component name
has not been found in the dump VTOC copy data set. If there has been
an index component in the data set, it is found in the VTOC copy.
- 58
- For a VSAM data set restore of a cluster, the index component
name has not been found in the dump VTOC copy data set. The data component
is found in the VTOC copy.
- 60
- An error has occurred in establishing an ESTAE environment.
- 62
- Both NEWNAME and FROMDUMP parameters have been requested on the
RECOVER command for a VSAM data set, and the original data set exists. DFSMSdss does
not support the NEWNAME parameter for VSAM data sets, so the restore
must use the original data set name. Two versions of the same data
set (one with the original name and one with the new name that contains
the restored data after the restore is done) cannot exist when FROMDUMP
has been specified. If FROMDUMP and NEWNAME have been specified, the
existing data set with the original name must be deleted.
- 64
- The dump copy needed for restoring is contained in file two or
higher on a dump volume. DFSMShsm encountered an error trying to
read or update the JFCB intended to represent the dump copy when opened
by DFSMSdss.
- 70
- DFSMShsm cannot
restore an integrated catalog facility (ICF) catalog data set.
- 72
- DFSMSdss does
not support key range VSAM data sets.
- 74
- FROMDUMP has been specified without DUMPVOLUME for a multivolume
VSAM data set. A dump copy is used to restore a multivolume data set
only if DUMPVOLUME has been specified with the FROMDUMP parameter
by a DFSMShsm authorized
user. If FROMDUMP has been specified without any subparameter or with
a subparameter other than DUMPVOLUME, DFSMShsm does not restore the data set.
This is to ensure that an authorized user knows which piece of the
data set is being restored from which dump copy.
- 76
- DFSMSdss does
not support data set restore for a VSAM data set currently cataloged
in a non-ICF catalog.
System action
The RECOVER command ends. DFSMShsm processing continues.
Programmer response
Use the LIST command to list the contents
of a dump VTOC copy data set, the dump copy information for a given
source volume, or the information concerning a dump volume. Correct
the information for the RECOVER command and reissue it. If an allocation,
open, or read error has occurred, take appropriate corrective action;
then, resubmit the command.
For reascode 6,
issue a data set RECOVER command with the TOVOLUME parameter specifying
an SMS-managed volume that has a device type similar to the original
volume that has been dumped. This restores the data set from a physical
dump copy to an SMS-managed volume.
For reason code 52, specify
or correct the FROMVOLUME parameter, or specify or correct the SOURCEVOLUME
parameter and reissue the command.
For reason code 62, to restore
a data set with the NEWNAME option, rename the existing data set with
the original name.
If a backup version exists for the data
set and you wish to explicitly recover it, use the GENERATION parameter
on either RECOVER or HRECOVER command.
If an ICF catalog data
set is to be restored from a dump copy made through DFSMShsm, a DFSMShsm LIST command can be
used to find the dump tape volumes that contain the dump copy of the
catalog data set. The restore will follow the steps documented in z/OS DFSMShsm Storage Administration, in topic, "Availability
Management Procedures" under, "Backing Up and Recovering an ICF
Catalog".
For reason code 64, reissue the RECOVER command.
For reascode 72
or 76, reissue the RECOVER command without specifying the FROMDUMP
keyword if an incremental backup version exists for the data set.
For reascode 74,
issue a LIST command with the PVOL BCDS ALLDUMPS parameter to retrieve
the information about dump copies and dump volumes of the primary
volume. Then issue a LIST command with DVOL DUMPCONTENTS parameter
to retrieve the information about the dump copies of the data set.