Space management of VSAM data sets

DFSMShsm migration functions that exist for non-VSAM data sets also exist for VSAM data sets that are listed in the integrated catalog facility catalog.

The migration of a VSAM data set is performed only on a complete VSAM sphere. The base cluster and all alternate index clusters defined on the base cluster are migrated as part of the data set and are not specified separately. Paths are included automatically in the data set migration command.

When DFSMShsm migrates a VSAM data set, it tracks a maximum of eight component names for that data set. See Figure 1, which shows component name limitations when DFSMShsm is recalling a migrated VSAM data set.

Figure 1. Component Name Limitations when Recalling Migrated VSAM Data Sets
Component name limitations when recalling migrated VSAM data sets.

DFSMShsm can migrate multiple-volume SMS-managed VSAM data sets when it processes the volume containing the base data component. DFSMShsm does not migrate a sphere that has a component that needs to be verified.

Data sets cataloged in the integrated catalog facility catalog with more than one alternate index (AIX), more than one path on the base, or more than one path defined on the AIX are not selected for migration during volume processing. These data sets can be migrated by data set command.

DFSMShsm does not migrate a VSAM data set marked for forward recovery, or one with retained locks.