Processor connect recovery *START,main

Function

When the local main has completed initialization, it initiates communication with the global. If this local is online to the global, both mains automatically enter the connection sequence. When the connection sequence is complete, JES3 issues this message on the global main:

IAT2645     ***** main CONNECT COMPLETE *****

If the local main is offline to the global, enter the *F,V,main ON or *V,main,ON command on the global to vary the local main online. The processors now enter the connection sequence.

If the automatic connection sequence fails, the JES3 global issues this message:

IAT2640     CONNECT REJECTED FOR main - error text

To resume the connection sequence, follow the operator response instructions in z/OS JES3 Messages for the error text received with message IAT2640.

If the automatic connection sequence does not take place (if the connection had completed, JES3 would have issued message IAT2645, which is discussed above) and JES3 does not issue any failure messages, try to determine the status of the local main. If JES3 initialization seems to be complete on the local main, use the *START,main,CONNECT command to restart the connection sequence. Use the *START,main,CONNECT command to reestablish communication between the global and a local main.

Recovery of work from a failed or stopped processor

Use the *START,main,FLUSH command to flush active jobs on a JES3 local main processor that has failed or been stopped. Only use this command in the case of a literal failure or stoppage. If jobs remain active on a main processor that has been flushed, errors on the JES3 spool can occur and a cold start would be required. For this reason, you cannot flush the global processor.

Note: JES3 does not allow a FLUSH command to be directed at a local system that is considered operational. If the target system is not down, JES3 will issue the following messages:

IAT2061 SYSTEM sysname IS ACTIVE IN JESXCF GROUP groupname
IAT2064 RESET ALL SYSTEMS SHOWN OR REPLY CANCEL

If you do not expect to restart JES3 on the old global processor immediately after a DSI, issue the *S,main,FLUSH command to:

ensure jobs registered with automatic restart management on the old global processor are restarted on either the new global or another active local processor
tell the new global all work in an on-main state, on the specified main, is to be removed from that state. This will allow JES3 to apply the failure option to all batch jobs and also allow the restarting of FSSs on the new global or another active local processor if the FSS is defined to execute there.

In response to this command, JES3 issues messages IAT2061 and IAT2064. These messages instruct you to reset the local main.

Note: If you decide not to flush the main after entering *S,main,FLUSH, reply CANCEL to message IAT2064.

Syntax


>>-+-*START-+--,--main--+-,--CONNECT-+-------------------------><
   '-*S-----'           '-,--FLUSH---'

Parameters

main: Specifies the name of the local main processor.
CONNECT: Establishes a connection from the local to the global processor.
FLUSH: Specifies that all jobs currently running on the designated main processor are to be flushed.

If the *S,main,CONNECT command does not establish the connection between processors, run the *DUMP command (8DUMP on the local system) on the global and local processors, and provide the results to your system programmer. Once the problem is resolved, end JES3 and restart the local processor.

When the connection is complete, the local main is eligible for jobs to be scheduled to it. From now on the local main is treated as a JES3-managed device and can be varied online or offline.