Tuning CA PMO › Addressing Special Tuning Concerns › Evaluating the Use of LLA and VLF › Handling Private Libraries

Handling Private Libraries

You should allow CA PMO to manage all of your private library directories, and you should not place any private library directories in LLA. You can use either VLF or CA QuickFetch to manage your frequently requested load modules. If you want to use VLF, place the following LLA parameters in the CSVLLAxx startup parameter member. This member must be placed in the data set that you specified on the //IEFPARM DD statement in the LLA startup procedure. (Refer to IBM documentation for details on the LLA startup procedure.)

LIBRARIES(library-name) 
NOFREEZE(library-name)

CA PMO will maintain current directory entries for a library load modules in a hash table, and VLF will always have current modules as a result. (If the hash table shows a different location, or TTR, for a module than the one that VLF has, the fetch request is resolved from DASD. After a user-initiated LLA refresh, VLF purges the outdated copy.)

If you use CA QuickFetch, you do not place any libraries under LLA or VLF control.

In general, CA QuickFetch is more efficient than VLF. It purges out-of-date load modules automatically. Also, although CA QuickFetch always purges only the updated modules, VLF purges all modules in a refreshed library. CA QuickFetch also displays statistics on fetch activity on a monitor that is similar to PMOMON.