As with migration, DFSMShsm refers to the RACF® profile of the active data set for all TSO user interactions with their backups.
To recover a RACF-indicated data set, the corresponding profile must exist. This can be a problem with discrete profiles because deleting the data set also deletes the discrete profile. When the discrete profile has been deleted, a new one must be rebuilt by an appropriately authorized person before the data set can be recovered by a non-DFSMShsm-authorized user.
DFSMShsm provides the capability to back up RACF discrete profiles when a RACF-indicated data set is backed up. If you specify the SETSYS PROFILEBACKUP command, the discrete profiles are backed up. Non-DFSMShsm-authorized users can then recover deleted data sets that had discrete profiles, because DFSMShsm recovers the backup profile if no discrete profile exists for a RACF-indicated data set.
When a cataloged non-VSAM data set is being recovered to another volume, DFSMShsm RECOVER gives some assistance by updating the volume serial information of the original RACF discrete profile, if it still exists, or of the recovered backup profile.
When you specify the NEWNAME and REPLACE parameters to recover a VSAM data set, DFSMShsm deletes any information about newly named data sets from the catalog before it recovers the data set. The newly named data set gets the catalog information that the original data set had, including password and RACF-indication. You must provide the proper RACF protection for the newly named data set.
With generic profiles, most of these considerations do not apply, and no extensive security administration is required. If a generic profile exists that covers data sets that were backed up with discrete profiles, the data sets can be recovered by non-DFSMShsm-authorized users whether the discrete or backup profiles exist, provided the user is authorized access to the data sets.