z/OS DFSMShsm Managing Your Own Data
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Recovering a backup version or a dump copy of a data set

z/OS DFSMShsm Managing Your Own Data
SC23-6870-00

Task: Recover a backup version or a dump copy of one or more data sets.

When recovering SMS-managed or non-SMS-managed data sets, you can do any of the following tasks:
  • Replace an existing version or damaged data set with the recovered version of the data set.
  • Recover the backup version of a cataloged non-VSAM data set that is currently migrated, as specified in the computing system catalog or the MCDS, if the HRECOVER command is issued with NEWNAME specified, and the NEWNAME data set is not a migrated data set.
  • Rename the recovered version of the data set and have two versions of the same data set on DFSMShsm-managed volumes.

You cannot recover the backup version of a cataloged VSAM data set that is currently migrated, as specified in the computing system catalog or the MCDS, until DFSMShsm recalls or deletes the migrated VSAM data set.

The copy of a data set to be recovered can be either a backup version or a dump copy created by DFSMSdss. If your installation uses both incremental backup and the DFSMSdss dump function, an HRECOVER command may result in DFSMShsm invoking DFSMSdss to do a restore of the data set. You can read about the decisions that DFSMShsm makes to select the DFSMSdss copy in z/OS DFSMShsm Storage Administration. In most cases, it will be transparent to you whether the HRECOVER command results in using a backup version or a dump copy. Usually, the most recent copy of your data set will be made available based on the DFSMShsm options set by your installation’s system programmer and on the optional parameters that you specify on the HRECOVER command.

RACF® authority: To recover a RACF-protected data set and you issue the HRECOVER command:
  • Without the NEWNAME parameter, you must have RACF ALTER authority to the data set.
  • With the NEWNAME parameter:
    • You must have RACF READ authority to the data set being recovered.
    • In addition, if the newname data set exists and is RACF-protected and you specify REPLACE, you must have RACF ALTER authority to the newname data set.
RACF profile requirements: The following are RACF profile requirements when you issue the HRECOVER command with the NEWNAME parameter:
  • A RACF profile must exist for the original data set if the original data set was RACF-indicated at the time of backup or recovery.
  • A RACF profile must exist for the newname data set if the newname data set exists and is RACF indicated.
Note: In either case, it does not matter if the original data set exists as long as the profile exists.

Abbreviation: The minimum abbreviation for the HRECOVER command is HRECOV.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014