Specifying when data sets become eligible for level 1 to level 2 migration

For non-SMS-managed storage, the age at which data sets become eligible for migration from level 1 to level 2 is the same for all non-SMS-managed data sets in the system. The MIGRATIONLEVEL1DAYS parameter of the SETSYS command specifies the minimum time that a data set must remain unused on the combination of level 0 and level 1 before it becomes eligible to migrate from level 1 to level 2. For example, for a MIGRATIONLEVEL1DAYS value of 31, a data set might stay unused on level 0 for 31 days, or it could stay on level 0 until it is eligible to migrate to level 1 and reside on level 1 until it was unused for a total of 31 days. In the example system, the following command is added to the ARCCMDxx member in DFSMShsm host 2:
SETSYS MIGRATIONLEVEL1DAYS(60)

(The command is added only in DFSMShsm host 2 because only DFSMShsm host 2 does automatic level 1 to level 2 migration.)

If you want DFSMShsm to do automatic migration from ML1 to ML2 volumes, you must specify the thresholds of occupancy parameter (of the ADDVOL command) for the ML1 volumes.