DFSMShsm migration functions that exist for non-VSAM data sets also exist for VSAM data sets cataloged in the integrated catalog facility catalog.
The migration of a non-SMS-managed 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 command migration.
When DFSMShsm migrates a VSAM data set, it tracks a maximum of eight component names for that data set. Figure 1 shows component name limitations when DFSMShsm is recalling a migrated VSAM data set.
A non-SMS-managed VSAM data set can be migrated only if it is completely contained on one volume. 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 migration.
DFSMShsm does not migrate a VSAM data set marked for forward recovery, or one with retained locks.
Related reading
For more information about the data sets not supported by space management, see z/OS DFSMShsm Implementation and Customization Guide.