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

Same-System Updates

If CA PMO is active on the system where a member or a library is updated, CA PMO takes one of the actions described in the following sections.

Updates of the Managed List

If there is an update of an individual member with an entry in the managed list, CA PMO purges that entry. CA PMO may replace this entry if there are subsequent directory searches for the member.

If the entire library is updated, CA PMO deletes all entries for members of that library from the managed list. It may replace these entries, as warranted by subsequent directory search activity. If a LNKLST library is updated, CA PMO purges all entries for that library and the libraries following it in the LNKLST concatenation. This prevents CA PMO from possibly using the wrong member to satisfy a BLDL/FIND request. See the related discussion in the section Refresh Library Directory Entries in the chapter "Issuing Commands."

Updates of the Hash Tables

When one or more members of a library with a hash table are updated, CA PMO updates that hash table.

• If a member of a library with a hash table is updated, CA PMO purges hash table entry for the member. Then, if the member was not deleted, CA PMO quickly replaces that entry.
• If an entire library with a hash table is updated, CA PMO purges the existing hash table and replaces it with a new one.

Note: If there is a directory search for an updated member while CA PMO is conducting the hash table update, CA PMO passes the search to the z/OS directory search routine (SVC 18).

Updates of LLA If you find that LLA is refreshed often on your system, you must discontinue use of it when you have CA PMO. But if you continue to use LLA, CA PMO can refresh it automatically in response to an update, or it can warn the operator when a refresh is warranted. If you specify the parameter LLA=AUTO or LLA=WARN, CA PMO uses an LLA interface that monitors the LLA and detects updates to LNKLST libraries. Depending on the values that you specify for the OPERMSG and REFDELAY parameters, CA PMO can either automatically refresh LLA after a time delay, or it can warn the operator that an LLA refresh is needed. If CA PMO issues a warning, the operator must specify the LLA refresh command.

If you specify the parameters LLA=AUTO and OPERMSG=NO, CA PMO refreshes only the member or library that was updated. This avoids the delays associated with refreshing the entire LLA. If you specify these parameters, you must also specify the REFDELAY and LLAPRMLB parameters.