Updating Libraries › How CA PMO Handles Updates to Library Members › Cross-System Updates

Cross-System Updates

If you have a multi-CPU site, you may have a version of CA PMO and PMO/XSYS installed on each CPU on the network. Updates on a particular CPU are detected by the version of CA PMO running on that CPU. Depending on the value that you specify for the XSYSCOMM parameter, the following may happen after the update:

• If you specify the parameter XSYSCOMM=ALL, a component of CA PMO called CA PMO Cross-System (PMO/XSYS) communicates information about the update to the other systems running CA PMO.
• If you specify the parameter XSYSCOMM=PMO, information is communicated only about CA PMO-managed libraries and libraries that are eligible for management. When an update occurs on one system, the CA PMO on that system detects the update, and the PMO/XSYS on that system communicates the information to versions of PMO/XSYS running on other systems. The versions of PMO/XSYS that receive the update information communicate it to their versions of CA PMO. If the CA PMO on another system does not manage the library, the information is ignored. If the version of CA PMO on the receiving system does manage the library it takes the following actions:
  • If the updated member has a directory entry in the managed list or in a hash table, each CA PMO responds as if it was a same-system update. (See the section Same-System Updates.)
  • If you specified the parameter LLA=WARN or LLA=AUTO, each PMO/XSYS initiates an LLA refresh or warns the operator that a refresh is required.