Migration considerations for the control data sets and the journal

Ensure that the control data sets, control data set backup copies, journal data set, and journal data set backup copies are not allowed to migrate. Migration of any of the preceding data sets could make recovery impossible.

If your control data sets are on SMS-managed volumes, ensure that they do not migrate by:

Placing them on volumes that are defined in a storage class with
AUTO MIGRATION ===>NO

or
Associating the control data sets with a management class whose attributes are
COMMAND OR AUTO MIGRATE ===> NONE

If your control data sets are on non-SMS-managed volumes, ensure that they do not migrate by specifying the NOMIGRATION parameter of the SETMIG command.

Refer to the following publications for more information about preventing data set migration in SMS and non-SMS environments:

For SMS, see the topic about specifying migration attributes in z/OS DFSMShsm Storage Administration.
For non-SMS, see the topic about controlling the migration of data sets and volumes in z/OS DFSMShsm Storage Administration.