Tuning CA PMO › Tuning at Installation Time › Evaluating the Handling of Updates

Evaluating the Handling of Updates

If you are using the PMO/XSYS component, you need to evaluate how updates are being handled.

1. Issue the S PMO command on all systems that will run CA PMO.
2. Check the D8 and D9 PMOMON displays on two systems that are running CA PMO. Find a library that is a candidate for management on one system and is being managed by CA PMO on the other system. (A candidate is any library that has not been excluded with the INCLAUTO or EXCLAUTO parameter.) Update that library, and verify that the update information has been communicated to the CA PMO on the other system. There will be a short delay between the time of the update and the time that CA PMO refreshes its storage area. Repeat this test several times by deleting, copying, and renaming members and performing link edits and PDS compresses. Examine the PMOMON D10 display and the offline report to be sure that CA PMO refreshes updated entries for members in the hash tables.

Note: If you specified XSYSCOMM=ALL in your parameter data set, all updates are communicated. If you specified XSYSCOMM=PMO, update information is communicated only for libraries that CA PMO is managing or those it considers eligible for management.

If updates are handled incorrectly, the programs that issue BLDL/FIND requests may be receiving outdated members. These programs may experience a system abend 106, or they may obtain an old copy of the requested member.

Note: If you stop CA PMO and then update any libraries on that system, you should issue the command F PMO,D=ALL on all systems where CA PMO was active when the update occurred.