$P JES2 - Withdraw JES2 from the system
To withdraw JES2 from the system to which the entering console is attached.
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.
- A call
is made to the recovery termination manager (RTM) to immediately terminate
the JES2 address space. The $HASP095 message displays the $PJF termination
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 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.
- JES2 attempts to withdraw cleanly, regardless of any cross-system activity.
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.
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.
- 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.
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.
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.
1 $p jes2 $pjes2 * *$HASP607 JES2 NOT DORMANT -- MEMBER DRAINING * RC=10 ACTIVE ADDRESS SPACES * RC=11 ACTIVE NETWORKING DEVICES $HASP608 $PJES2 $HASP608 ACTIVE ADDRESS SPACES $HASP608 ASID JOBNAME JOBID $HASP608 -------- -------- -------- $HASP608 001D ZFS STC00003 $HASP608 0022 BPXAS STC00009 $HASP608 0023 BPXAS STC00010 $HASP608 0024 BPXAS STC00011 $HASP608 0025 BPXAS STC00012 $HASP608 ACTIVE NETWORKING DEVICES $HASP608 NAME STATUS $HASP608 -------------------------------- -------- $HASP608 LINE15 ACTIVE $HASP608 LINE16 ACTIVE $HASP608 LINE17 ACTIVE $HASP608 LINE25 ACTIVE $HASP608 LINE26 ACTIVE $HASP608 LINE27 ACTIVE $HASP608 LINE28 ACTIVE $HASP608 LINE29 ACTIVE $HASP608 LINE40 ACTIVE $HASP608 LINE41 ACTIVE $HASP608 LINE42 ACTIVE $HASP608 LINE43 ACTIVE $HASP608 LINE44 ACTIVE $HASP608 LINE50 ACTIVE $HASP608 LINE51 ACTIVE $HASP608 LINE55 ACTIVE $HASP608 LINE59 ACTIVE
JES2 does not terminate because all the JES2 functions are not down. The $HASP607 and $HASP608 messages indicate the reasons why command is rejected.
2 $p jes2 $pjes2 $HASP608 $PJES2 COMMAND ACCEPTED $HASP085 JES2 TERMINATION COMPLETE
JES2 terminates normally.
3 $pjes2,abend * *$HASP095 JES2 CATASTROPHIC ERROR. CODE = $PJ2 $HASP088 JES2 ABEND ANALYSIS $HASP088 ------------------------------------------------------ $HASP088 FMID = HJE7705 LOAD MODULE = HASJES20 $HASP088 SUBSYS = JES2 z/OS 1.2 $HASP088 DATE = 2001.158 TIME = 11.30.58 $HASP088 DESC = OPERATOR ISSUED $PJES2, ABEND $HASP088 MODULE MODULE OFFSET SERVICE ROUTINE EXIT $HASP088 NAME BASE + OF CALL LEVEL CALLED ## $HASP088 -------- -------- ------- ------- ---------- ---- $HASP088 HASPCOMM 00042C00 + 007BC2 NONE *ERROR $PJ2 $HASP088 PCE = COMM (066663E0) $HASP088 R0 = 0004A4AA 00B5D680 00006F5E 00047170 $HASP088 R4 = 00000000 06666D84 00000004 06666D88 $HASP088 R8 = 0004A4AA 0004E266 00000000 00007000 $HASP088 R12 = 00042C50 066663E0 0662A6E8 000C0AC0 $HASP088 ------------------------------------------------------ * *$HASP198 REPLY TO $HASP098 WITH ONE OF THE FOLLOWING: * END - STANDARD ABNORMAL END * END,DUMP - END JES2 WITH A DUMP (WITH AN OPTIONAL TITLE) * END,NOHOTSTART - ABBREVIATED ABNORMAL END (HOT-START IS AT RISK) * SNAP - RE-DISPLAY $HASP088 * DUMP - REQUEST SYSTEM DUMP (WITH AN OPTIONAL TITLE) * *08 $HASP098 ENTER TERMINATION OPTION
JES2 ends and displays a short dump analysis. Following the analysis, JES2 displays message $HASP198 with termination options from which to choose; JES2 then issues $HASP098 and waits for you to enter a termination option.
4 $p jes2,abend,force $HASP553 $PJES2,ABEND,FORCE COMMAND DENIED. ISSUE THE $PJES2, ABEND COMMAND FIRST
JES2 does not terminate because the FORCE parameter has been entered before attempting the $P JES2,ABEND command.