Explanation
The RECOVER command was issued with the FROMDUMP
and APPLYINCREMENTAL parameters. The volume requested to be restored
has a valid dump copy, but DFSMShsm determined the application of incremental
recoveries cannot be performed. Therefore, only the restore from the
dump copy is performed.
The
reascode value
gives the reason the incremental recoveries could not be done. Valid
values for
reascode are:
- Reascode
- Meaning
- 4
- A read error occurred reading a control data set record describing
the source backup or dump information, or the record was not found.
See message ARC0184I for the type and key of the record, and the type
of error.
- 6
- An error occurred in reading the JFCB while processing the backup
VTOC copy data set.
- 8
- A volume allocation error occurred.
- 10
- Recovery of a more recent backup version of an OS CVOL failed.
This recovery is attempted first. Since further processing may depend
on the contents of this catalog, the process ends.
- 12
- An error occurred in allocating the backup or dump VTOC copy data
set.
- 14
- An error occurred in reading the backup or dump VTOC copy data
set.
- 15
- Obtain of the format-1/format-8 DSCB of the VTOC copy data set
failed.
- 16
- An error occurred in opening the backup or dump VTOC copy data
set.
- 18
- The VTOC copy data set has a format-8 DSCB.
- 20
- The required backup or dump tape volumes are not available.
- 22
- The volume does not have both backup and dump VTOC copy data sets
to use to build a list of candidate data sets for recovery.
- 24
- An invalid or unsupported device type was found for the source
backup, dump volume, or the migration level 1 volume where the VTOC
copy data set resides, in its control data set record.
- 25
- APPLYINCREMENTAL processing is not allowed because the volume
contained a VSAM catalog the last time DFSMShsm dumped or backed up the volume.
- 26
- APPLYINCREMENTAL processing is not allowed for DFSMShsm owned volumes because
these volumes are not supported for the volume backup function.
- 27
- APPLYINCREMENTAL processing is not allowed because the correct
level of the Data Facility Product (DFP) is not installed on the system.
The correct level of the DFP required to support this function is
Release 2 Version 3 or subsequent releases, unless otherwise noted.
- 28
- The MCV record that describes the volume on where the dump VTOC
copy resides indicates that the volume is not a migration level 1
volume.
- 30
- SMS has not been active in the system when DFSMShsm has attempted to process
SMS-managed volumes.
- 32
- DFSMShsm cannot
determine if the volume being processed is an SMS-managed volume.
The SMS volume definition and the volume VTOC entry do not agree.
- 34
- An error has occurred while retrieving an SMS volume definition. DFSMShsm has
invoked SMS to retrieve an SMS volume definition. SMS has failed to
retrieve it.
- 52
- A GETMAIN error occurred in getting storage for the recovery queue
elements.
- 60
- An error occurred in establishing an ESTAE environment.
- 66
- An internal error occurred in sorting the queue of recovery queue
elements (RQEs). The queue was broken.
System action
The restore process is performed. The incremental
volume recovery is not performed. DFSMShsm processing continues.
Programmer response
If the volume contains an owning VSAM catalog,
ensure that the catalog has been recovered with the latest backup
copy and is in a usable state. DFSMShsm does not back up and recover VSAM
catalogs. If the volume has been processed by volume backup, a volume
recovery can be requested when the state of the catalog has been verified.
If
the recovery of a catalog failed, determine if the catalog is usable
and recent enough. If it is not, issue the RECOVER command for the
catalog. If the catalog is usable or a later RECOVER command for the
catalog succeeded, issue the RECOVER command for the volume again
without the FROMDUMP and APPLYINCREMENTAL parameters and specify the
date the volume was restored.
Use V1R12 or higher
to recover volume if VTOC copy data set has a format-8 DSCB.