Migrating an SMS-managed volume

You can cause data sets to migrate from an SMS-managed volume by using the MIGRATE command. The MIGRATE VOLUME command can override some management class attributes that control when an SMS-managed data set is eligible to migrate, depending on the form of the command. The MIGRATE VOLUME command migrates data sets for which the management class COMMAND OR AUTO MIGRATE attribute has the value of BOTH only.

When you issue a MIGRATE VOLUME command for an SMS-managed volume:

migration is from level 0 volumes to ML1 or ML2 volumes only.
the volume is considered to be DFSMShsm-managed. DFSMShsm maintains control records for the volume until a DELVOL command is issued for that volume.
a list of the management class definitions required for processing the SMS-managed data sets on the volume is obtained.

Table 1 summarizes the various conditions that can be encountered when obtaining a list of management class definitions and the system action taken as a result.

Table 1. Conditions that can be encountered when obtaining a list of management class definitions during migration of an SMS-managed data set
If...	Then...
the list cannot be obtained.	the command fails and an error message is issued.
the management class definition for a data set cannot be found in the list.	the data set is not processed and an error message is issued.
the data set does not have a management class associated with it.	the default management class is used.

Fast subsequent migration can be performed when a data set is migrated as a result of a MIGRATE VOLUME command. If fast subsequent migration fails, the data set is migrated in the normal method.

Example commands used to migrate data sets SMS-managed volumes

The commands in Figure 1 are examples of commands that can be used to migrate data sets from an SMS-managed volume.

Figure 1. Example commands used to migrate data sets from SMS-managed volumes

MIGRATE VOLUME(SG1001)
MIGRATE VOLUME(SG2003 MIGRATE(0))
MIGRATE VOLUME(SG1002) DAYS(0)

Consider the first the command in the example: MIGRATE VOLUME(SG1001). This command requests DFSMShsm to process the volume in the same method as described in Automatic primary space management.

Next, consider the second and third commands in the example: MIGRATE VOLUME(SG2003 MIGRAGE(0)) and MIGRATE VOLUME(SG1002) DAYS(0). These commands override the PRIMARY DAYS NON-USAGE attribute of the management class so that all data sets on the volume that have the COMMAND OR AUTO MIGRATE attribute value of BOTH migrate. Any data set with a LEVEL 1 DAYS NON-USAGE attribute value of 1–9999 or NOLIMIT migrates to an ML1 volume. Any data set with a LEVEL 1 DAYS NON-USAGE attribute value of 0 migrates to an ML2 tape volume. If an attempt to migrate a data set fails, error message is issued and data set remain on the SMS-managed volume. If a nonzero value or no value is specified for the MIGRATE or DAYS parameter, the command fails and an error message issued.

Note: Class transitions are not performed during command-driven space management.

Migrating an SMS-managed volume

Example commands used to migrate data sets SMS-managed volumes

Related reading