Updating Libraries › How CA PMO Handles Updates to Library Members › Types of Updates

Types of Updates

There are essentially two kinds of updates: updates to libraries and updates to members of those libraries.

Library Members

Updates to library members include the following activities:

• Link-editing of load module members.
• Text changes to the data in non-load libraries (which may be any kind of data, including JCL, CLISTs, program source code, ISPF panels, and macro instructions).
• Renaming, deleting, copying, and creating any type of member.

When you update a member of a library, its location on DASD—that is, its TTR—might change. Since the TTR is stored in the directory entry for that member, the update invalidates the member entry in the CA PMO software cache or LLA. CA PMO automatically detects member updates. When an update is detected, CA PMO modifies the member entry in the managed list or hash tables (as appropriate) to reflect the update. If you have not turned off LLA, CA PMO also can automatically refresh LLA after LNKLST updates, depending on the value that you specified for the LLA parameter.

Entire Libraries

Certain kinds of updates affect entire libraries. These updates include the following activities:

• Compressing a library, which affects multiple members in that library.
• Copying a library by using the IEBCOPY utility (see the section Copying Library Members for details on SAS and ISPF copy utilities that affect only the copied modules).

The way CA PMO handles library and member updates depends on whether the update occurs on the system where CA PMO is running, or if it occurs on a different system. These issues are discussed on the following pages.