$P JES2 - Withdraw JES2 from the system

Function

To withdraw JES2 from the system to which the entering console is attached.

Parameters

ABEND

JES2 terminates immediately, with one exception, regardless of any JES2 or system activity. The $HASP095 message displays the $PJ2 termination code. The exception occurs 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 JES2,ABEND command until the checkpoint write has completed.

Note: If $P JES2, ABEND does not succeed, specify FORCE.

FORCE

A call is made to the recovery termination manager (RTM) to immediately terminate the JES2 address space. The $HASP095 message displays the $PJF termination code.

Use this parameter only if the JES2 main task is not responding to the

$P JES2, ABEND.

If you enter the FORCE parameter without first attempting a $P JES2,ABEND command, JES2 issues the $HASP553 message and ignores the command until you try the ABEND option. Specifying the FORCE parameter can cause unpredictable results.

Note: The $PJES2,ABEND,FORCE command must be specified as a string of characters. Blanks are not permitted within either the command verb or the individual parameters of the command.

JES2

JES2 terminates. If $P JES2 does not successfully remove JES2 from the system, specify ABEND or TERM.

Note: If JES2 is processing any jobs, or any devices are active, you cannot remove JES2 from the system unless you specify the ABEND or TERM operand. Started RJE and NJE linesalso prevent withdrawal, even if no remotes or NJE nodes are active on those lines. In this case, the JES2 operand is ignored, and the $PJES2 command merely stops JES2 processing (which can be restarted by $S) and drains JES2 work from the system. You may display any activity using the $D A or $D U commands.

QUICK

JES2 attempts to withdraw cleanly, regardless of any cross-system activity.

TERM

JES2 terminates but does not terminate active programs and devices. A JES2 hot start will not be permitted. It is recommended that the JES2 address space be terminated prior to bringing down MVS™. The preferred method to do this is by a clean shutdown of JES2 using the $PJES2 command. If this is not possible, a $PJES2,TERM should be used.

Note: This termination option ensures that track groups are not lost.

Authority Required

This command requires system authority. The description of the $T RDRnn command explains how to ensure that the authority of the appropriate MVS system command group is assigned.

This command requires control security access authority. For a description of assigning command input authority, see z/OS JES2 Initialization and Tuning Guide.

Processing Considerations

• The $P JES2 command deactivates event tracing with the same results as specifying $T TRACEDEF,ACTIVE=N.
• After the $P JES2 command completes its processing, you should 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 for further information regarding system action.
• You can return JES2 to the system by issuing an MVS START command which invokes a procedure in SYS1.PROCLIB that contains the JCL necessary to start JES2.
• Since the QUICK keyword ignores cross-system users while deciding whether to end the JES2 program, those applications (cross-system users) can abnormally end.

Scope

Single member. This command will be in effect for this member only.

However, you might want this command to be applied to all members of the MAS (to ensure a consistent environment across the MAS). If so, you can use the MVS ROUTE *ALL command to issue this command to all active members (if the JES2 command character is the same on all members). See z/OS MVS System Commands for more information on using the ROUTE *ALL command.

Messages

The $HASP085 message indicates JES2 termination is complete.

The $HASP607 message indicates that you have attempted to withdraw from the system before all JES2 functions are down. See z/OS JES2 Messages for an explanation of the return codes.

The $HASP608 message lists the specific reasons why JES2 cannot be withdrawn as a response to a $DJES2 command or as a response when a $PJES2 command is rejected.

If the JES2 main task encountered an error, JES2 issues message $HASP088 to describe the error. Message $HASP198 (an informational message) lists the termination options and precedes the $HASP098 message.

The $HASP098 message requests a termination option.

The $HASP552 message informs the operator that JES2 is writing to a checkpoint data set; the JES2 member cannot terminate until the checkpoint write has completed.

The $HASP553 message informs the operator that a $P JES2,ABEND,FORCE command was entered before attempting a $P JES2,ABEND command. You must specify the $P JES2,ABEND command to bring the JES2 member down.