Explanation: MIGRATIONLEVEL1 and MIGRATIONLEVEL2
are mutually exclusive, optional subparameters of the MIGRATION parameter
that you use to specify the level of the migration volumes.
- MIGRATIONLEVEL1
- specifies that the migration volume receives migrated data sets
from primary volumes. A migration volume specified with this subparameter
is called a migration level 1 volume. If the migration level 1 volume
you are adding or changing is not mounted when you issue the ADDVOL
command, DFSMShsm allocates the volume, which sends a mount request
to the operator.
- MIGRATIONLEVEL2
- specifies that the migration volume receives data sets migrating
automatically from migration level 1 volumes and by command from primary
volumes or migration level 1 volumes. A migration volume specified
with this subparameter is called a migration level 2 volume.
Defaults: If you are adding a migration
volume to DFSMShsm, the default is MIGRATIONLEVEL1. If you are changing
the attributes of a migration volume, it remains at the same level
as it was when it was added to the list of volumes owned or managed
by DFSMShsm. If you are changing the attributes of a migration volume
and you specify the incorrect level, the ADDVOL command fails.
Note: If DFSMShsm migrates data sets from primary volumes
directly to a tape migration level 2 volume, you can decide not to
add additional migration level 1 volumes to this DFSMShsm host. However,
you must have at least one migration level 1 volume added to this
DFSMShsm host if:
- SMS data sets require migration level 1 volumes as specified by
their management class attributes
- You allow backup versions generated using the BACKDS or HBACKDS
commands to be written to migration level 1 volumes.
- You want DFSMShsm to do extent reduction
- You want DFSMShsm to do any type of volume backup and volume dump
when you are keeping dump VTOC copy data sets