DEFINE MIGRATION LEVEL 2 REJECTED - {TAPE VOLUME CANNOT BE
ASSOCIATED WITH KEY RANGE | I/O ERROR | MIGRATION TO LEVEL 2 DASD
IN PROCESS | DRAIN ATTRIBUTE | TOO MANY KEYS PREVIOUSLY SPECIFIED
FOR VOLUME=volser}
Explanation
A DEFINE command was issued to define the structure
of migration level 2 storage to DFSMShsm, but one of the following conditions
occurred:
- An attempt was made to associate one or more tape migration level
2 volumes to key ranges, which is not allowed.
- An I/O error occurred when positioning or reading the migration
control record in a multiple processing unit environment. See the
preceding message ARC0187I for the I/O error.
- One of the following types of migration was in process:
- Migration of a migration level 1 or level 2 volume to level 2
DASD.
- Migration of all level 1 to level 2 DASD.
- An ADDVOL command with the DRAIN parameter was previously processed
for the volume. The volume is no longer eligible to be a target volume
for migration. The volume specified in the message is the first volume
with the DRAIN attribute in the list of volumes specified in the DEFINE
command. There may be others with the same problem.
- An attempt was made to define more than 61 key ranges.
System action
The MIGRATIONLEVEL2 parameter is ignored. Processing
continues for the POOL, MIGRATIONCLEANUPCYCLE, and BACKUP parameters.
Programmer response
- If the error is TAPE VOLUME CANNOT BE ASSOCIATED WITH KEY RANGE,
reenter the command specifying only DASD migration level 2 volumes.
- If the error is I/O ERROR, reenter the DEFINE command with the
MIGRATIONLEVEL2 parameter after the I/O error is fixed as described
in the preceding message ARC0187I.
- If the error is MIGRATION TO LEVEL 2 DASD IN PROCESS, wait until
the migration is complete and reenter the DEFINE command with the
MIGRATIONLEVEL2 parameter. If DFSMShsm is in a multiple processing unit
environment and the processing of the migration to level 2 DASD fails
before the migration completes, DFSMShsm will not allow a DEFINE command
to be issued on any processor until DFSMShsm is started up in the processor
that failed. If the processor will be unavailable for an extended
time and you want to issue a DEFINE command with the MIGRATIONLEVEL2
parameter, the DFSMShsm migration
control data set migration control record (MCR) for the inoperative
processor must be modified. Enter a FIXCDS command for the MCR record
for the inoperative processor so that DFSMShsm will set off the indicator that
migration to level 2 DASD is running. This indicator is MCRFML2. Once
the migration to level 2 DASD indicator is set off in the MCR of the
inoperative processor, DFSMShsm will allow a DEFINE command with
the MIGRATIONLEVEL2 parameter to be processed.
- If the error is DRAIN ATTRIBUTE, reenter the command specifying
only DASD migration level 2 volumes that do not have the DRAIN attribute
already turned on. Use the LIST command to find those volumes that
do not have the drain attribute turned on.
- If the error is TOO MANY KEYS PREVIOUSLY SPECIFIED FOR VOLUME
= volser, 61 or less key ranges must be specified
for VOLUME = volser.