Data set considerations

Before using zDMF to perform data migrations, you should review this section for details that may affect your data sets.

The following topics are included in this section:

zDMF data set selection planning
Data sets created after activation
Data set extent and multi-volume data set handling
Data sets persistently held by applications
Supported storage subsystems and data set types

zDMF data set selection planning
zDMF includes many data set selection criteria, from a single data set to thousands of data sets and multiple groups. When using selection criteria that go beyond a fully qualified data set name, it is recommended that a listing utility be used that has the same selection criteria as zDMF.
Data sets created after activation
Data sets matching the Source DSN masks that are catalogued after Activation are not included in the data sets population of the group being migrated. If the migration objective is to depopulate the source volumes, you should prevent allocations of data sets on these volumes.
Data set extent and multi-volume data set handling
When migrating data sets that have multiple extents, zDMF images the target data set to be an exact reflection of the source data set. This means that if the source data set in a migration currently is in six extents, then the target data set is allocated with six identically sized extents.
Data sets persistently held by applications
If you intend to migrate data sets that are persistently held by applications, you may have to stop and restart those applications in order to complete the migration process.
Supported storage subsystems and data set types
The supported storage devices and arrays are all 3380 and 3390 z/OS formatted volumes supporting the Count Key Data/Extended (CKD/E) format.

Parent topic: Planning and implementation