By default, CA PMO selects the private libraries that it manages in the hash tables. CA PMO scans a list of candidate libraries (you can view this list on the PMOMON D9 display) and determines what libraries it should manage based on directory search activity. CA PMO attempts to handle 95% of the total directory search load. If it falls short of this target, it automatically manages any library that is responsible for 1-7% of the eligible candidate library searches, depending upon the percentage of the directory search load that CA PMOis currently handling. (SMS-managed must-cache data sets are managed regardless of these limits.) CA PMO scans the candidate list every 1 to 5 minutes, looking for libraries to manage. When CA PMO is optimizing a small percentage of all directory searches, its rate of scanning increases. When CA PMO is optimizing a larger percentage of searches, its rate of scanning decreases.
You can limit the number of libraries that CA PMO manages by decreasing the value of the NUMADDED parameter. You also can limit the amount of virtual storage that CA PMO can obtain in its address space. If either of these limits prevents CA PMO from including a new library for management, CA PMO may stop managing one or more libraries that currently have hash tables.
By managing private libraries automatically, CA PMO can optimize system performance for long periods of time without any operator intervention. CA PMO responds quickly to system changes. Users have a large number of libraries (including program libraries, libraries for CLISTs, JCL, macros, program source code, and ISPF panels, tables, and messages), and they constantly allocate new ones and delete old ones. CA PMO adjusts quickly to the renaming, deleting, and reallocation of libraries. It also adjusts quickly to dramatic workload changes, such as a transition from daytime to evening shifts at an installation.
In addition to allowing CA PMO to manage all private libraries automatically, you can instruct CA PMO to manage only a particular set of libraries, or you can specify a set of libraries that it may not manage. The INCLAUTO parameter allows you to restrict CA PMO management of private libraries to those that begin with a certain prefix (such as all libraries beginning with USER1), and the EXCLAUTO parameter allows you to specify a set of libraries that CA PMO cannot manage automatically. If you have critical libraries that you want CA PMO to manage at all times, you may specify those libraries on the INCLPRVT parameter in your parameter data set.
You also can control CA PMO management of private libraries using commands that you specify at the console while CA PMO is running.
|
Copyright © 2011 CA.
All rights reserved.
|
|