|
|
|
|
|
In this section, the term "remote verification" is used to include the following: remote verification, enforcement and reformat processing.
Intra SYSPLEX diagram
A remote verification request can be sent from any Control-M JCL Verify monitor (CTJMON) in the SYSPLEX to any other CTJMON in the same SYSPLEX, without any special set up and without an IOAGATE. Using XCF, a CTJMON in a SYSPLEX can communicate automatically with any other CTJMON in the SYSPLEX.
For remote verification between different SYSPLEXs, at least one IOAGATE/CTJAS (Control-M JCL Verify Application Server) pair is needed to connect the two SYSPLEXs to each other. In the more general configuration with multiple SYSPLEXs, remote verification requests can be sent from any CTJMON in a SYSPLEX to any other CTJMON in another SYSPLEX with only a single IOAGATE/CTJAS per SYSPLEX.
Note: All CTJMON’s with the same XCFGROUP definition in CTJPARM can discover and communicate with each other. By default, XCFGROUP is the same for all installations and versions. However, if required, CTJMON’s can be grouped into distinct groups by defining a unique XCFGROUP for each group.
Remote Verification between SYSPLEXs diagram
CTJMON in one SYSPLEX can communicate with CTJMON in another SYSPLEX if there is a pair of IOAGATE/CTJAS that connect the two SYSPLEXs. Only a single IOAGATE/CTJAS pair (one in each SYSPLEX) is required to enable all CTJMONs in one SYSPLEX to communicate with all CTJMONs in the other SYSPLEX.
For example, in order for CTJMON in SYSB in PLEX1 to communicate with CTJMON in SYSD in PLEX2, CTJMON in SYSB will use XCF to forward the request to the CTJMON in SYSA (the CTJMON which contains the IOAGATE/CTJAS pair) and then CTJMON in SYSA will forward the request via its associated IOAGATE/CTJAS to the IOAGATE/CTJAS in SYSE in PLEX2. This IOAGATE/CTJAS will forward the request to the CTJMON in SYSE, which in turn will forward the request, using XCF, to the target CTJMON in SYSD. The reply will come back over the same route.
Parent Topic |