DFSMShsm data movement usage scenarios

DFSMShsm data movement functions assist in your management of data storage in several scenarios.

To apply current SMS management policies to existing ML2 data sets

This data has management policies defined years or decades ago. Over time, the acquisition of new storage options such as cloud has resulted in the definition of new policies. DFSMScdm uses DFSMShsm to recall migrated data sets, and to remigrate them to long-term storage. The current management policies of the data sets determine the destination of the remigration.

To accommodate an IBM z/OS environment moving from disk and tape to disk only

Regulatory or business considerations require existing data on ML2 data sets to be retained. Before removing the tape subsystem, these ML2 data sets must be moved to new storage.

To move infrequently accessed ML2 data sets to cloud objects

Cloud migration eliminates recycles for infrequently accessed data, avoiding CPU processing and reduces tape storage resources needed. DFSMScdm can select ML2 data sets by the last migration date to prioritize which data to move. When DFSMScdm migrates a data set to a cloud object, the date last referenced and the migration date remain unchanged, retaining critical historical accuracy about the data set. DFSMScdm provides user-customizable parameters to set the pace of migration to avoid bottlenecks with other DFSMShsm work on the system.