Previous Topic: The Object Store DatabaseNext Topic: Customize Cache Sizes


Determine the Best Values for the Three Caches

To minimize I/O EXCPs to the object store database, set the cache size parameters to the total size of all of the files within each of the different table categories (except for the rollback files, which are suffixed with MMA, RBI, MM2, and RB2). Perform the following calculations to determine the size for each of the cache parms:

-x

Sum the size of the following files (divide the result by 1024 to convert to KB):

-y

Sum the size of the following files (Divide the result by 1024 to convert to KB):

-z

Sum the size of the following files (Divide the result by 1024 to convert to KB):

Note: Perform these calculations only after all MIBs have been loaded and all agent instances have been started. Ensure that your Agent Technology for z/OS Services have been shut down before you attempt to modify the awservices.cfg file (otherwise your changes are not preserved).

Even if only one agent is active at a time but the store contains all MIBs, ensure that the size of the cache for the VOTREE table is at least the same as the size of its corresponding file. A smaller value (even within a few KB) leads directly to an increase of EXCPs.

This is not the case for the two other tables. Although the best size for the corresponding caches is higher than the size occupied by the corresponding MIB definition, plus the size that all the instances of the agent use. Therefore, we recommend you allocate them as the total size of the different tables.