ERASEONSCRATCH and NOERASEONSCRATCH: Specifying to check for erasure of DFSMShsm-owned data sets

Explanation: ERASEONSCRATCH | NOERASEONSCRATCH are mutually exclusive, optional parameters specifying whether DFSMShsm should check for erasure of DFSMShsm-owned data sets that have migrated or been backed up to DFSMShsm-owned volumes.

ERASEONSCRATCH specifies that DFSMShsm asks RACF® for the erase status of the user’s data set when backup versions and migration copies are scratched from DFSMShsm-owned DASD volumes. The data set is deleted, and if RACF indicates erase-on-scratch, the DASD residual data is overwritten by data management.

NOERASEONSCRATCH specifies that DFSMShsm does not ask RACF for the erase status of the user’s data set when backup versions and migration copies are scratched from DFSMShsm-owned DASD volumes. The data set is deleted but the DASD residual data is not overwritten by data management.

SMS relationship: Parameter differs in meaning when applied to SMS-managed or non-SMS-managed DASD volumes or data sets.

SETSYS default: None.

DFSMShsm default: If you do not specify either parameter on any SETSYS command, the DFSMShsm default is NOERASEONSCRATCH.

Note:
  1. DFSMShsm always allows data management to perform erase-on-scratch functions for user-owned data sets.
  2. ERASEONSCRATCH and NOERASEONSCRATCH affect only backup versions and migration copies of data sets.
Parent topic: Optional parameters of the SETSYS command