Performing an Action on Another System ctoug3

Control-O DO statements that support communication can be sent to Control-O on other systems. A Control-O rule on one system can request that an action be performed by Control-O on a remote system.

If both Control-Os are active in the same Sysplex environment, the Sysplex communication function is used. If the Control-Os are active on systems connected by VTAM or TCP, Control-O will use IOAGATE for communication. For more information about IOAGATE, see the Control-O Communication step in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

The target remote system can be specified as follows:

• For any DO statement that supports communication, the target remote system can be specified using the %%$COMMSYS reserved user-defined variable in a preceding DO SET statement.

  The following DO statements support communication (that is, this method applies to the following DO statements):

  — DO COMMAND

  — DO COND

  — DO DISPLAY

  — DO FORCEJOB

  — DO RESOURCE

  — DO RULE

  — DO SHOUT

• Several of the above DO statements have a SYSTEM subparameter. The target remote system can alternatively be specified in this subparameter. If a remote system is specified both through %%$COMMSYS in a preceding DO SET statement and through the SYSTEM subparameter, the specification in the SYSTEM subparameter takes precedence.

The following DO statements support communication by either %%$COMMSYS or the SYSTEM subparameter:

• DO COMMAND
• DO DISPLAY
• DO SHOUT

For information regarding %%$COMMSYS, see the description of the variable in Reserved User-Defined Variables.

Note the following regarding other DO statements:

• DO SET does not support communication. Therefore, the DO SET statement cannot be sent to Control-O on another system, although it is used to identify the remote system (through %%$COMMSYS) for the DO statements mentioned above.
• For the DO RULE statement, only System variables are transferred to other systems.

Example 1

In the example in Figure 115, when CICS ends on its own system, Control-O requests that a Control-O installation on the MVS1 system issue a START CICS command to the MVS1 system.

Figure 115 Performing an Action on Another System – Example 1

ON JOBEND    = CICS       JTYPE S SMFID        SYSTEM                And/Or/Not

OWNER  N25      GROUP                             MODE PROD     RUNTSEC

THRESHOLD

DESCRIPTION

===========================================================================

DO COMMAND  = S CICS

   WAIT        CONSOLEID    CONSOLE          SYSTEM MVS1

   WAITMODE   Y             WAITRESP Y            TIMEOUT

   RESPMSG DFH*

Explanation

ON JOBEND=CICS

When CICS is ended

DO COMMAND=S CICS

 WAIT        CONSOLEID    CONSOLE         SYSTEM MVS1

start CICS on the MVS1 system.

 WAITMODE   Y              WAITRESP Y           TIMEOUT

 RESPMSG DFH*

Wait for messages prefixed by DFH.

In a Sysplex environment, Control-O sends the S CICS command to the MVS1 system through the extended MCS console.

For a remote system connected by VTAM or TCP, the request is passed to the local IOAGATE that sends it to the remote IOAGATE. The remote IOAGATE then issues the command. This remote IOAGATE waits for the response messages (prefixed by DFH) and sends the messages back to the local IOAGATE.

Example 2

In the example in Figure 116, Control-O requests that the FORCEJOB command be performed to start CICS through Control-O on the SYSBKUP system.

Figure 116 Performing an Action on Another System – Example 2

ON JOBEND   = CICS     JTYPE S SMFID      SYSTEM               And/Or/Not

   OWNER CICSADMN GROUP                         MODE PROD    RUNTSEC

   THRESHOLD

   DESCRIPTION WHEN CICS ENDS - FORCEJOB ON THE CONTROL-M ON THE

   DESCRIPTION ALTERNATE SYSTEM TO START CICS.

   DESCRIPTION

   ===========================================================================

   DO SET      = %%$COMMSYS=SYSBKUP                              GLOBAL  N

   DO FORCEJOB = TABLE   CICS     JOB CICSALT   UFLOW N    DATE ODAT

                 LIBRARY CTM.PROD.SHEDULE

   DO

   ===========================================================================

Explanation

ON JOBEND=CICS

When CICS is ended

DO SET=%%$COMMSYS=SYSBKUP                              GLOBAL  N

sets %%$ COMMSYS to the name of the remote system

DO FORCEJOB=TABLE   CICS       JOB CICSALT   UFLOW N    DATE ODAT

 LIBRARY CTM.PROD.SHEDULE

Control-O on the CICSADMN system requests that a Control-O rule on the SYSBKUP system issue the FORCEJOB command for the CICSALT job.

Example 3

In the example in Figure 117, Control-O on the CICSADMN system requests that the START CICS command be performed on the SYSBKUP system.

Figure 117 Performing an Action on Another System – Example 3

ON JOBEND    = CICS       JTYPE S SMFID        SYSTEM    And/Or/Not

   OWNER  CICSADMN      GROUP            MODE PROD     RUNTSEC

   THRESHOLD

   DESCRIPTION

   ===========================================================================

   DO SET      = %%$COMMSYS=%%SYSBKUP                              GLOBAL  N

   DO COMMAND  = S CICS

      WAIT        CONSOLEID    CONSOLE          SYSTEM

     WAITMODE   Y             WAITRESP Y            TIMEOUT

      RESPMSG DFH*

Explanation

ON JOBEND=CICS

When CICS is ended

DO SET=%%$COMMSYS=%%SYSBKUP                            GLOBAL  N

set %%$COMMSYS to the backup system previously named, using the %%SYSBKUP Global AutoEdit variable.

DO COMMAND=S CICS

 WAIT        CONSOLEID    CONSOLE         SYSTEM

Then, START CICS on the SYSBKUP system.

WAITMODE   N              WAITRESP             TIMEOUT

Do not wait for a response.