Deleting migrated data sets

To delete migrated SMS-managed data sets, you can use one of the following methods:

DFSMShsm DELETE command
Access Method Services DELETE command
TSO DELETE command
IEHPROGM utility

Table 1 shows what happens when you specify one of these commands or use the IEHPROGM utility to delete a migrated data set.

Table 1. Commands for Deleting Migrated Data Sets
Command or Utility	Result
DFSMShsm DELETE, Access Method Services DELETE, TSO DELETE or IEHPROGM utility SCRATCH function for SMS-managed data set	Scratches a data set on a DASD migration volume without recalling the data set or marks the data set not valid in the TTOC for any tape ML2 volumes that contain the data set. DFSMShsm then uncatalogs the data set. DFSMShsm deletes all control data set records related to the migration copy. If the data set is migrated to an SDSP, the MCD is updated to indicate that the migration copy needs to be scratched. If a discrete RACF® data set profile exists, DFSMShsm deletes it. Note: If the optional parameter NON-VSAM is specified on the Access Method Services DELETE command, the migrated data set is recalled before deletion. If you specify the optional parameters GDG FORCE on the Access Method Services DELETE command, IDCAMS does not invoke DFSMShsm. You must then issue the DFSMShsm DELETE command for each of the now-uncataloged migration copies.
IEHPROGM utility SCRATCH function for non-SMS-managed data set	Scratches a migrated data set if: The specified volume is the same one the data set migrated from The volume is not SMS managed The data set is not SMS managed DFSMShsm scratches the migration copy of the data set and deletes the MCDS data set record. The data set remains cataloged.

If the deleted data set has backup versions, DFSMShsm keeps the backup versions.

If a data set has been deleted by one of the preceding commands and you want to recover a backup version of the data set, see Data set recovery and restore.