ARC1128I
BACKUP/DUMP COPY DOES NOT EXIST

Explanation

A RECOVER or HRECOVER command was issued, but no backup version or dump copy exists for the specified data set or volume. Message ARC1001I precedes this message giving the data set name or volume serial number. The reascode in message ARC1001I gives an indication of the conditions and the necessary action to take to correct the situation.
Reascode
Meaning
0
A BCDS record describing the data set or volume was not found. You may also get this reascode when the data set recovered has only a physical dump copy and the device type of the original volume that was dumped is not similar to the device type of the target volume selected for the restore.
4
The BCDS entry was found for the data set or volume. However, one of the following occurred:
  • A backup version or dump copy of the data set or volume is not available.
  • A backup version or dump copy of the data set or volume does not meet the date, generation, or version requirements. You may also get this reason code if a dump copy exists for the data set, but DFSMShsm cannot find it because:
    • The data set is not currently cataloged to the source volume of the dump copy.
    • There is no incremental backup version that meets the date or generation specified to allow DFSMShsm to determine where the dump copy is.
  • A dump copy does not meet the date, data set restore, dump generation, dump volume, or dump class requirements.
  • The data set was not found in a dump VTOC copy data set.
  • A cataloged backup version was not found for the data set when FROMVOLUME was not specified.
12
A recover request was issued without specifying FROMDUMP(DUMPVOLUME(volser)) for a multivolume data set. A BCDS backup version was not found for the data set.

A dump copy is used to restore a multivolume data set only if FROMDUMP(DUMPVOLUME(volser)) was specified by a DFSMShsm authorized user. If FROMDUMP(DUMPVOLUME(volser)) was not specified, DFSMShsm only recovers a multivolume SMS-managed data set using an incremental backup version. This ensures the entire data set is recovered as one entity, or to verify an authorized user knows which piece of the data set is restored from which dump copy. DFSMShsm does not back up multivolume non-SMS-managed data sets.

16
A recover request was issued for a VSAM SMS key range data set. A BCDS backup version was not found for the data set. Since DFSMSdss does not support key range data sets, only the backup version is used to recover a VSAM SMS key range data set.
20
The NEWNAME parameter was specified for a VSAM data set when the original data set exists and no backup copy exists (only a DUMP COPY exists). DFSMSdss does not support the NEWNAME parameter for VSAM data sets, so the restore must use the original data set name.
24
A recovery command specified with the RCVRQD keyword was issued for a data set. A BCDS backup version was not found for the data set. DFSMShsm does not support the recovery of a physical dump copy of a data set if the RCVRQD keyword was specified.

System action

The recovery operation of this data set ends. DFSMShsm processing continues.

Programmer response

Consider the following actions and reissue the command:
Reascode
Meaning
0
If this occurred due to dissimilar unit types, reissue the command directing the data set to the correct unit type.
4
Issue a LIST or HLIST command with the BACKUPCONTROLDATASET and DATASETNAME parameters to retrieve information about backup versions of the data set and then perform one of the following:
  • Be sure you specify the correct data set name.
  • If the data set was cataloged at the time it was backed up, do not specify the FROMVOLUME parameter.
  • If the data set was uncataloged at the time it was backed up, specify the FROMVOLUME parameter with the volume serial number of the volume from which it was backed up.
  • If the DATE parameter was specified, a backup version created on or before the date specified does not exist. Specify a correct date.
    If there is an eligible dump copy, but no eligible incremental backup version, perform one of the following:
    • Reissue the RECOVER or HRECOVER command with the FROMVOLUME parameter.
    • Reissue the RECOVER or HRECOVER command with the REPLACE parameter after the data set is cataloged to the source volume of the dump copy.
  • If the GENERATION parameter was specified and a backup version of the specified relative generation number does not exist, specify a correct generation number.
  • If the VERSION parameter was specified and the specified version number does not exist, specify a correct version number.
12
Issue a LIST command with PVOL BCDS ALLDUMPS to retrieve the information about dump copies and dump volumes of the primary volume. Then issue a LIST command with DVOL DUMPCONTENTS to retrieve information about each dump copy of the data set. Perform one of the following:
  • Reissue the command with:
    FROMDUMP(DUMPVOLUME(volser))
    if a dump copy exists for a piece of the data set and only one piece of the data set is to be restored.
  • Reissue several commands:
    RECOVER FROMDUMP(DUMPVOLUME(volser))
    to restore several pieces of the data set if dump copies exist for the data set.
16
No action required.
20
If you want to retain the original data set, copy the original data set to a new data set name. Then restore the dump copy of the data set to the original data set name by issuing the RECOVER command without the NEWNAME parameter.
24
Reissue the recovery command without the RCVRQD keyword.

If a corresponding ARC1069I message precedes this message, see the ARC1069I application programmer response.

Source

DFSMShsm