Set an appropriate amount of virtual storage for CA PMO to prevent message PMO691I GETMAIN FAILED - VIRTUAL STORAGE EXHAUSTED. REASON=HT/DCB. DSN=data set name.
Business Value:
The message appears if the GETMAIN fails for the hash table or for the DCB for the current library. In this case, CA PMO stops managing a different library (with less directory activity) and starts managing the current library (with more directory activity). This may have a negative impact on the directory search performance.
With sufficient virtual storage provided, CA PMO can manage the busy libraries that can benefit most, without losing the directory search benefit that results in performance gains.
Additional Considerations:
As a general rule, you allocate one megabyte for every 13,000 directory entries to be stored in hash tables. The virtual storage size of the CA PMO address space is controlled by the IEFUSI user exit. The default for this exit is 32 MB, which is enough storage for 416,000 directory entries.
You do not need to worry about allocating too much storage. CA PMO does not actually use the storage unless it is needed.
More Information:
Each offline report shows the amount of virtual storage used by the library. See "Producing Offline Reports for Managed Private Libraries" in the CA PMO Systems Programmer Guide.
|
Copyright © 2011 CA.
All rights reserved.
|
|