Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Terminating Xchange


Xchange can be terminated from the operator console. An Xchange administrator can also terminate Xchange from the batch facility. For information on designating Xchange administrators, see Task-8-3-5-Designating-Xchange-administrators. We recommend you not use the MVS CANCEL command to terminate Xchange.

If Xchange save/restore processing is enabled, a final checkpoint save of the Xchange requests data set will be done as part of shutdown. This ensures that all Xchange requests are retained, even though the normal save interval may not have elapsed. This checkpoint save does not take place, however, if Xchange is terminated with an MVS CANCEL or if Xchange abends.

Important

If CICS transaction support is active, an authorized user must enter the STOP primary command on the Simulated Date Time Settings screen for CICS before terminating Xchange. See Primary Commands.

Terminating Xchange From the Operator Console

If the REPLY parameter of the Xchange CMSC PARMLIB member is set to YES as described in Task 3.2.2: Specify Xchange parameters, Xchange will leave the following Write-To-Operator with Reply (WTOR) message outstanding on the master console:

nn XG9999 ssid ENTER XCHANGE COMMAND

where nn is the message sequence number required for the SHUTDOWN operator command and ssid is the subsystem ID.

You can terminate Xchange by terminating the Xchange address space with the SHUTDOWN operator command. Type the SHUTDOWN command on the master console in the following format:

R nn,SHUTDOWN xxxxxx

In this command line, nn is the message sequence number from the outstanding WTOR message described above and xxxxxx is either NORMAL (the default) or IMMED.

The NORMAL parameter terminates Xchange when all queued and active jobs have ended or have been deleted from the Simulated Date Time Setting screen (For more information, see Specifying-Requests-in-ISPF). Xchange does not terminate until these conditions are met.

The IMMED parameter immediately terminates Xchange. Active jobs continue to run. After Xchange terminates, any dates and times that are requested revert to the current system values.

You can also specify SHUTDOWN with an MVS MODIFY or STOP command. Specify SHUTDOWN as a MODIFY (F) command in the format as follows:

F jobname,SHUTDOWN xxxxxx

Specify SHUTDOWN as an MVS STOP (P) command in the format P jobname.

In these MVS examples, jobname is the name of the Xchange batch job or started task and xxxxxx is either NORMAL (the default) or IMMED.

Terminating Xchange From the Batch Facility

If you are an Xchange administrator, you can terminate Xchange by using a batch job to input the SHUTDOWN command as a parameter. The SHUTDOWN command is processed as if it were entered by the console operator. Invoke the batch facility with the JCL shown in the following figure:

JCL to Terminate Xchange

//STEPNAME EXEC PGM=XGBOPCMD,PARM=’request’
//SYSPRINT DD   SYSOUT=*
//STEPLIB  DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR
//

You must provide information for the request variable, according to the following syntax:

SUBSYS=ssid,OPCMD=SHUTDOWN xxxxxx

where ssid is a four-character subsystem ID and xxxxxx is either NORMAL or IMMED.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*