Explanation

>>-MIGRATION OF SOURCE=--SPOOL1--VOLUME------------------------->
>--TO TARGET=--SPOOL2--VOLUME--result--------------------------><
The operator entered a
$MSPL command to migrate source spool volume
SPOOL1 to target spool volume
SPOOL2.
The command
result is one of the following
for a merge migration (for a move migration,
-MERGE would be replaced with
-MOVE):
- 3
- Initiated start of target volume.
- 4
- Initiated drain of source volume.
- 5
- Completed allocation of target volume.
- 7
- BACKOUT processing completed unallocation of the target volume.
- 10
- Migrator and spool assistant subtasks have been attached.
- 24
- Migration phase SETUP-MERGE is starting.
- 25
- Migration phase SETUP-MERGE is complete.
- 26
- Migration phase COPY-MERGE is starting.
- 27
- Migration phase COPY-MERGE is complete.
- 28
- Migration phase CATCHUP-MERGE is starting.
- 29
- Migration phase CATCHUP-MERGE is complete.
- 30
- Migration phase CLEANUP-MERGE is starting.
- 31
- Migration phase CLEANUP-MERGE is complete.
- 32
- Migration phase SETUP-MERGE is starting.
- 38
- Migration cancelled. Phase CANCEL-MERGE is starting.
- 40
- Migration cancelled. Phase BACKOUT-MERGE is starting.
- 41
- Migration cancelled. Phase BACKOUT-MERGE is starting.
- 42
- Migration cancelled. Phase CLEANUP-MERGE is starting.
- 43
- Migration phase CANCEL-MERGE is complete.
- 44
- Migration cancelled. Phase BACKOUT-MERGE is starting.
- 45
- Migration cancelled. Phase BACKOUT-MERGE is starting.
- 46
- Migration completed. Target volume exceeded maximum number of
track groups that can be mapped.
- 47
- Migration phase CLEANUP-MERGE is starting.
- 49
- Migration phase INITIALIZING is complete. Migrator and spool assistant
subtasks have been attached.
System action
Operator response
If the migration completed successfully,
you can remove the source volume from the JES2 environment. If the
migration was not successful, you can rerun the $MSPL command once
the problem has been resolved.
Module
HASPSPOL
Routing Code: 1,2
Descriptor
Code: 4