Usage notes for SMHSMUTL
These control cards are formatted for execution by TSO.
For the migration control data set, the general format of the control card is
HSEND DELETE dsn
For the backup control data set, the general format of the control card is
HSEND BDELETE dsn
SMHSMUTL processing is controlled by DELETE requests. Each DELETE request specifies the following information:
Data set name or name mask
Type of DFSMShsm control data set to be affected (migration or backup)
Aging specification (number of days after which the data set is to be deleted)
These criteria are compared to DFSMShsm control data set entries; for eligible data sets, a DFSMShsm delete control card is generated. For example, the following SMHSMUTL DELETE request
DELETE CDS=MCDS DSN=TD*.SPFTEMP*./ MIGDAYS=10
might generate the following control cards:
HSEND DELETE TDMOORE.SPFTEMP2.CNTL HSEND DELETE TDCAREY.SPFTEMP1.LIST HSEND DELETE TDJOHNSN.SPFTEMP0.CNTL HSEND DELETE TDJOHNSN.SPFTEMP1.CNTL HSEND DELETE TDJOHNSN.SPFTEMP2.CNTL
Up to 3,140 DELETE requests can be submitted in a single run.
MainView SRM must be active for SMHSMUTL to run. The generated control cards must be submitted to TSO to actually change the DFSMShsm control data sets.
The DFSMShsm DELETE command deletes a migrated data set without recalling it. Both the MCDS entry and the migrated data set are deleted. The DFSMShsm DELETE command does not delete backup versions of the data set. The DFSMShsm BDELETE command deletes all backup versions or specific backup versions of a data set.