Space management of non-SMS-managed storage
Eligibility for DFSMShsm space management of non-SMS-managed storage is determined on a volume basis. Non-SMS-managed volumes that are to be automatically managed by DFSMShsm are known as primary volumes. That is, all the data sets on a volume are managed to the same specification, whether for days-not-used on the primary volume, age for deletion, or permission for automatic migration. In addition, DFSMShsm chooses the volume to receive the recalled data sets based on the volume pools you have defined, as well as the characteristics given the volumes when you defined them.
Differences between processing for SMS-managed and non-SMS-managed
data sets are as follows:
- Two additional space management functions are available for non-SMS-managed
volumes:
- Deletion (delete by age)
- Retirement (delete if backed up)
- Deletion of list and utility data sets.
- Level 1 to level 2 migration is controlled on a processing-unit-wide basis rather than on a data set management class basis.
- Target volumes for recall are selected by DFSMShsm rather than by DFSMSdfp.
- Volumes are individually identified to DFSMShsm using the ADDVOL command.
Related reading
- Before performing space management functions on extended address volumes (EAVs) you need to understand how EAV space is managed. For details, see Space management of extended address volumes (EAVs) and review recommendations in Recommendations for using extended address volumes (EAVs).
- For information about using DFSMShsm with Linux, see Linux-z/OS DFSMShsm dump or restore how-to.