During HBDELETE processing, DFSMShsm uses RACF® to determine the user’s authorization to process the data set. First, DFSMShsm makes an authorization check against the original data set name. If either a generic profile or a discrete profile cannot be found for a cataloged data set that was RACF-indicated at the time of backup, DFSMShsm determines whether a backup profile exists. If a backup profile exists, DFSMShsm makes a second authorization check with the backup profile name. If the second authorization check fails, the HBDELETE processing fails.