CA PMO supports update propagation between PMO systems. Two communication methods are provided:
XCF allows communication between systems on a single sysplex
The control file resides on shared DASD and allows communication between any systems which have access to the DASD volume.
Example:
Consider the following environment:
SYSPLEXA, with two systems
SPA1
SPA2
SYSPLEXB, with 1 system
SPB1
An update taking place on SPA1, would be passed to SPA2 through XCF. SPA2 would then pass the update on to SPB1 through the control file.
For the above example, systems would communicate as follows:
On SYSPLEXA, systems SPA1 and SPA2 would communicate with each other using XCF. Each PMO in the sysplex would use the same group name (XCFGROUP), which allows for XCF to know where messages should be delivered. So when SPA1 needs to inform other PMO’s within the SYSPLEX that an update occurred, it can request XCF to send the messages to all other members of the group (XCFMEMBR). In this small example, there is only one other member, SPA2.
As XCF may only be used within a SYSPLEX, the control file would be used to communicate between SYSPLEXA system SPA2, and SYSPLEXB system SPB1. XSYS identifies the MVS systems running PMO instances using the control file.
The CA PMO parameters for XCF and control file would be specified as follows:
SYSPLEXA, system SPA1
XCFGROUP=PLXAGRP
XCFMEMBR=SPA1MEM
SYSPLEXA, system SPA2
XCFGROUP=PLXAGRP
XCFMEMBR=SPA2MEM
XSYS=SPA2,SPB1
SYSPLEXB, system SPB1
XSYS=SPA2,SPB1
Note: The parameters above specify the same group for SPA1 and SPA2, since these systems are in the same sysplex. Also, SPA1 and SPA2 have unique member names.
If your environment will be using a control file, customize and submit the SAMP(ALLOCCF) member to allocate the cross-system communication file on a shared DASD volume. This sample JCL contains general instructions for control file sizing and placement.
|
Copyright © 2011 CA.
All rights reserved.
|
|