>>-UNACTIVATE REQUEST FAILED,--reason--------------------------><

OTHER MEMBERS ACTIVE

JES2 was warm started with PARM=UNACT specified; however, there are other members of the MAS that are active. PARM=UNACT can only be used on an all member warm start or an all member hot start (a hot start where there are no active JES2 address spaces). The effect is that the PARM=UNACT is ignored and JES2 starts in z/OS® 1.2 mode.

MEMBER NOT ALLOCATED TO BOTH CHECKPOINT DATA SETS

JES2 was warm started with PARM=UNACT specified; however, this member is not allocated to both checkpoint data sets (they have specified CKPT1 and CKPT2 as INUSE=YES, indicated MODE=DUPLEX and DUPLEX=OFF). You must be allocated to both checkpoint data sets to specify PARM=UNACT. The effect is that the PARM=UNACT is ignored and JES2 starts in z/OS 1.2 mode.

SPOOL MIGRATION IS IN PROGRESS OR A MAPPED VOLUME WAS FOUND

One of the following conditions prevented the unactivate request from succeeding:

• A JES2 spool migration is in progress and cannot be cancelled by the issued command. To run the issued command, you must first cancel the active spool migration by issuing the $MSPL volser CANCEL command.
• One or more mapped spool volumes exist in the current configuration. Make sure that all mapped volumes are drained and removed from configuration and retry the command.

A SPOOL IS USING NON-DEFAULT DATA SET NAME

Either JES2 was warm started with PARM=UNACT or an $ACTIVATE,LEVEL=Z2 command was issued, and JES2 detected at least one SPOOL volume with a non-default data set name. Z2 mode does not support non-default data set names, so the SPOOL data set must be removed and created with the default SPOOL data set, as specified by SPOOLDEF DSNAME=, before switching to Z2 mode. The effect is that JES2 remains in z/OS Z11 mode.

A greater than 1 character batch job class exists

Either JES2 was warm started with PARM=UNACT or an $ACTIVATE,LEVEL=Z2 command was issued, and JES2 detected at least one job class of greater than one character. Z2 mode does not support greater than one character job class names, so the greater than one character job class must be deleted before switching to Z2 mode. The effect is that JES2 remains in z/OS Z11 mode.