MAS migration restrictions

The following restrictions apply to spool migrations in a MAS environment:

The MAS must be running in z11 checkpoint mode. Otherwise, the $MSPL command is rejected and an error message is returned.
All active members of the MAS must be running z/OS 1.13. Otherwise, the $MSPL command is rejected and an error message is returned. Once the spool migration is complete, a down level member can be warm-started and join the MAS.
No inactive member can warm-start and join the MAS while a spool migration is active. In this case, a HASP447 WARM start denied - Active spool migration detected message is issued. Because all active members of the MAS participate in a spool migration, the MAS configuration must remain constant while a spool migration is active. Once the spool migration is complete, an inactive member can warm-start and join the MAS.
If an active MAS member becomes hot-startable during a spool migration, the migration waits until the member is hot-started before proceeding. All active members of the MAS participate in a spool migration, so if a member becomes hot-startable, the spool migration must wait until that member is hot-started and rejoins the MAS. If the status for a JES2 MAS member becomes MVS GONE during a migration (during an MVS IPL, for example), spool migration recovery starts and the spool migration proceeds without the member.
A down level member cannot warm-start and join the MAS if any spool volumes are in the MAPPED state, or are mapped targets.
Spool migration requires available BERTs, so the MAS must not have a BERT shortage that is preventing jobs from starting. In this case, the $MSPL command is rejected and an error message is returned.