Previous Topic: Suppressed Message Routing

Next Topic: Product Activation and Termination Considerations

Cross-system Command Routing

Using the CA MIC LINK command, CA MIC can accept commands from a local CA OPS/MVS subsystem and route them to the designated external systems. CA MIC then returns the command response messages to the local CA OPS/MVS subsystem.

Consider a MICplex consisting of SYSA, SYSB, SYSC, and VME, where you want a CA OPS/MVS subsystem named OPSS to have the ability to issue cross-system commands to SYSB, SYSC, and VME. You would issue the following command that could be placed in the MIMCMNDS member of the CA MIM parmlib:

IFSYS SYSA
      LINK PROD=OPSS SYSID=ALL AUTH=MASTER
ENDIF

This command establishes a cross-system command linkage between the OPSS subsystem on SYSA and SYSB, SYSC, and VME. Once this LINK command executes, the OPSS subsystem can issue commands to any system in the MICplex. The command response messages are returned to the command issuer, recorded in the OPSLOG, and can optionally be acted upon by the subsystem OPSSAOF rules.

Standard CA MIC command routing prefixes can be used by OPSS to direct commands to one or more systems in the MICplex. Here are a few examples using a colon (:) as the CA MIC command prefix character:

:ALL, D A,M*

CA MIC picks up this command issued by OPSS, and the D A,M* command is directed to all systems SYSA, SYSB, SYSC, and VME. CA MIC directs the command responses from each system to the OPSS subsystem.

:EXT, DISPLAY TIME

CA MIC picks up this command issued by OPSS and the DISPLAY TIME command is directed to external systems SYSB, SYSC, and VME. CA MIC returns the command responses from each system to the OPSS subsystem.

:VME, QUERY TAPE

CA MIC picks up this command issued by OPSS and the QUERY TAPE command is directed to system VME. CA MIC returns the command response from VME to the OPSS subsystem.