Advanced Topics › CA OPS/MVS Considerations › Cross-system Message Routing

Cross-system Message Routing

Using the CA MIC COLLECT command, CA MIC can import (collect) messages to a local CA OPS/MVS subsystem using any number of message selection or exclusion criteria.

Consider a MICplex consisting of SYSA, SYSB, SYSC, and VME. You want a CA OPS/MVS subsystem named “OPSS” to receive messages from 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
COLLECT PROD=OPSS SYSID=EXT ROUTCDE=ALL ACTION WTOR
                            MONITOR(JOBNAME,SESSION,STATUS)
ENDIF

After this command is executed on SYSA, the CA OPS/MVS subsystem named OPSS on SYSA would begin receiving messages from system SYSB, SYSC, and VME that meet the message criteria defined on the COLLECT command. Note that the SYSID parameter should not be set to “ALL”, nor should it include the local system name. The reason for this is that since the local CA OPS/MVS subsystem is already receiving local messages itself, it does not need CA MIC to present it with local messages as well. Therefore the SYSID value only needs to include the external system names (or EXT) from which you want CA MIC to import messages.

You may have a need to collect messages from external systems using different message criteria based on the originating system. The SETNAME= parameter on the COLLECT command can be used to define multiple collection sets for a single CA OPS/MVS subsystem:

IFSYS SYSA
      COLLECT PROD=OPSS SETNAME=SETB SYSID=SYSB ROUTCDE=ALL
      COLLECT PROD=OPSS SETNAME=SETC SYSID=SYSC ROUTCDE=(3,5) WTOR
      COLLECT PROD=OPSS SETNAME=SETE SYSID=VME  MSGID=HCP*
ENDIF

After these COLLECT commands are executed on SYSA, the CA OPS/MVS subsystem named OPSS on SYSA would begin receiving unique messages from each external system. SYSB would send messages with any route code (1-128); SYSC would send only messages with route codes of 3 or 5, and any WTOR; and VME would send only messages starting with the text of “HCP.”

Another possible configuration is where you have not one CA OPS/MVS subsystem on SYSA, but two or more, and you want CA MIC to import messages to each local CA OPS/MVS subsystem. Since all local CA OPS/MVS subsystems must have unique subsystem names that begin with “OPS”, there are two ways to have CA MIC import messages to multiple local CA OPS/MVS subsystems. The PROD= keyword on the COLLECT command can be used to direct imported CA MIC messages to all local CA OPS/MVS subsystems, or to direct imported messages to only one or more individual CA OPS/MVS subsystems. When COLLECT PROD=OPSS is specified, imported messages are routed only to the CA OPS/MVS subsystem named “OPSS.” When COLLECT PROD=OPS is specified, imported messages are routed to all locally active CA OPS/MVS subsystems. Note that when using the COLLECT PROD=OPS method, you should not also define COLLECT commands for individual CA OPS/MVS subsystems. Otherwise, those individual CA OPS/MVS subsystems will receive duplicate imported messages.