Once JES2 processing is complete, you can issue the $P JES2 command to withdraw JES2 from the system to which the entering console is attached. Specifying $P JES2 also turns off event tracing with essentially the same results as specifying $T TRACEDEF,ACTIVE=NO. You can later return JES2 to the system by issuing the MVS™ START command, which invokes a procedure in SYS1.PROCLIB that contains the JCL necessary to start JES2. If any jobs are being processed or any devices active, the $P JES2 command is processed as a $P command (which can be restarted by $S) and drains JES2 work from the system.

When it is not possible to drain the JES2 member, the command response ($HASP608 message) from a $P JES2 command will provide a detailed list of reasons why JES2 was not withdrawn. However, it is not necessary to issue the $P JES2 command to obtain this list. You can issue the $D JES2 command to obtain the same list of reasons why JES2 is not withdrawn as a result of a $P JES2 command. If no activity is detected, the $HASP608 message will display ALL AVAILABLE FUNCTIONS COMPLETE.

After a successful $P JES2 command, JES2 termination processing may still need to wait for processes to complete. One item is that JES2 termination will wait for request jobid address spaces to perform the corresponding return jobid. The $HASP715 message will display request jobid address spaces that must perform a return jobid before JES2 termination processing may proceed.

After a successful $P JES2 command, it is also possible for you to receive a $HASP714 message that indicates there are nnnnnnnn address space(s) other than JES2 which are preventing JES2 termination. This message will continue to be displayed until JES2 is able to shut down, or until JES2 detects that there is no progress being made in address space termination. In this case, a dump is taken of the address space(s) that are preventing JES2 termination. Note that if you receive the "DUMP INITIATED" form of $HASP714 and a dump was not taken, this indicates that JES2 termination is proceeding as intended.

If it is not possible or reasonable to drain the JES2 member (for example, due to large numbers of lines, jobs, and remotes; or, if you plan to restart JES2 using a hot start) you can specify $P JES2,ABEND. The ABEND parameter forces JES2 termination regardless of any JES2 or system activity. If the checkpoint resides on a coupling facility structure and the member is processing a write request, JES2 issues the $HASP552 message and delays the $P command until the checkpoint write has completed. Before issuing the $P JES2,ABEND command, you may wish to display current activity using the $D A or $D U commands.

If the $P JES2,ABEND command does not successfully terminate JES2, you can also specify the FORCE parameter. The $PJES2,ABEND,FORCE command results in a call to the recovery termination manager (RTM) to terminate the JES2 address space. Because the FORCE parameter can cause unpredictable results, always attempt to enter the $P JES2,ABEND command first. If you enter the $P JES2,ABEND,FORCE command before entering $P JES2,ABEND, JES2 issues the $HASP553 message and ignores the entire command.

To withdraw JES2 from a system involved in cross-system activity, you can issue the $P JES2, QUICK command. Cross-system activity occurs when a user on one JES2 subsystem requests a cross-system function from another JES2 subsystem within the same poly-JES2 environment (An MVS system in which more than one JES2 is running concurrently). This option deletes the control blocks for the request submitted by the user who requested cross-system function. Before using the QUICK keyword on the $P JES2 command, you should send a message to the user asking them to end their cross-system activity.

After the $P JES2 command completes processing,issue the HALT EOD command if you are planning to turn the system over for software or hardware maintenance. Issuing the HALT EOD command ensures that important statistics and data records in storage are not permanently lost. Refer to z/OS MVS System Commands, SA38-0666 for further information regarding system action.