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


Restrictions

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

  • If you want to keep both versions of the data set, you must specify NEWNAME when a data set exists with the same name as the data set you are recovering.
  • It is inconsistent to specify the NEWNAME parameter when you are recovering more than one data set with each HRECOVER command.
  • When you specify NEWNAME, you may have to consider the following conditions:
    If Then
    You are recovering a VSAM data set and you specify NEWNAME, The new data set name and the original data set name must be cataloged in the same catalog. Additionally, the catalog entry for the original data set name must exist so that the original data and index component names can be found. The base cluster data component name and the base cluster index component name of the data set being recovered must be the same as the base cluster data component name and the base cluster index name exported.
    You specify TOVOLUME with NEWNAME and the VSAM data set is cataloged in a non-ICF catalog, The volume must be owned by the catalog where the VSAM data set being recovered will be cataloged.
    The newname data set is an already existing VSAM data set, DFSMShsm uses the base cluster data component and base cluster index component name when creating the newname data set.
    The newname data set does not exist, DFSMShsm generates a name for the base cluster data component and the base index component.
    There is a path defined on the base cluster of a VSAM data set, You cannot rename the VSAM data set.
    If you are recovering a VSAM data set and the original data set exists, but no backup copy exists (only a dump copy exists), and you specify NEWNAME, The recover command fails. DFSMSdss does not support the NEWNAME parameter for VSAM data sets, so the restore function must use the original data set name.
    If you are recovering a non-VSAM data set and you specify NEWNAME, The new data set name should be cataloged and must have the same data set organization as the backup version.
  • DFSMShsm does not process individual partitioned data set members. If you specify a partitioned data set with a member name, DFSMShsm fails the HRECOVER request.
Note: When you issue the following command:
  • HRECOVER dsname NEWNAME (newdsname) REPLACE
consider the following:
  • If the original data set and newname data set are both VSAM data sets, password-protected, RACF-protected, and you have the proper RACF® authority to the data sets, this HRECOVER command will delete the newname data set (including the catalog entry and the RACF profile of the newname data set) and rename the recovered version to the newname data set.
  • If the original data set and the newname data set are both non-VSAM data sets, this HRECOVER command will not change the protection of the original data set. The data set VTOC entry of the newname data set indicates that the newname data set now has the combined protection of the original data set and the newname data set.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014