There are at least two effects that can cause this behavior.
First, CF storage is allocated in increments of 1M at current CFLEVELs. A
policy specification of 64000K will be rounded up to the nearest 1M frame,
so a structure allocated in response to that specification will actually
require 64512K or 63M.
Secondly, structure size often grows when a structure is rebuilt. This
occurs because most rebuilds attempt to preserve the number of structure
objects (lock entries, record data entries, etc.) currently allocated in the
structure ("allocation by counts"). Because of the way the CFCC structure
allocation algorithms work, allocation by counts often requires an
additional frame for each type of structure object, causing structure size
to grow by 2-3M. However, this effect is normally less pronounced for lock
structures.
We would need to know the details of the structure's allocation and rebuild
history to answer your question accurately.
Bill Neiman
IBM Parallel Sysplex development
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
