Storage calculations for coupling facility data tables

You can use the z Systems™ Coupling Facility Structure Sizer tool (CFSizer) to calculate storage requirements for data tables list structures in a coupling facility.

A coupling facility structure contains both stored data and the information needed to manage and access that data, in a similar way to a key-sequenced data set. The data for each entry in the coupling facility is stored as a chain of fixed-size (usually 256-byte) elements, which means that the exact length for variable-length data must be stored separately. To do this, CICS® includes a length prefix in the stored data, so space calculations must allow for each entry using a whole number of elements. The amount of internal control information depends on the level of functionality and performance of the coupling facility control code for the current coupling facility level (CFLEVEL). The storage requirements can increase for a higher CFLEVEL. For more information, see Coupling facility storage management.

CFSizer is a web-based application that takes these factors into account and communicates with a coupling facility at a current CFLEVEL to calculate storage requirements. See CFSizer.

To use CFSizer to calculate storage requirements for data table list structures, enter the following information:
Maximum number of tables
The maximum number of data tables that can be stored in the data tables structure. This value corresponds to the MAXTABLES server parameter. See List structure parameters.

Specify a large enough number to handle all your data tables, but not so large that unused preallocated list headers use a large amount of coupling facility storage. The valid range is from 1 to 999999. The default is 1000.

Average rounded record size
The average amount of storage required for each data record. Each record has a two-byte length prefix and is stored as one or more 256-byte elements. This value determines the entry to element ratio that is used to calculate the required structure size. The valid range is from 1 to 32768. The default is 512.

If all data records are similar sizes, calculate this value by taking the average data size, adding two, and rounding up to the next multiple of 256. The amount of element storage required is two bytes more than the data record size because of the length prefix on each item.

If data records are different sizes, round up each size first before you take the average. For example, if half the records are 100 bytes and half are 300, round up the sizes to 256 and 512 respectively, then average them. The resulting average rounded item size is 384, which is more accurate than using the average item size of 200 and then rounding it up to 256.

Records in a contention model data table with a record length of up to 63 bytes are a special case. These records are stored in the entry adjunct area, so for average record length purposes, the data length is effectively zero.

Total records
The total number of records to be stored in all data tables.
Target usage percent
The percentage of the structure space that the given total number of items are expected to use. Specify a number in the range of 1 to 100. The default is 75. This value ensures the following:
  • Free space exists for temporary expansion.
  • If the initial free space is not enough, there is time to expand the structure in response to warning messages (which normally start at 80%).
  • Activity to alter entry to element ratios is reduced.
Maximum expansion percent
The percentage that the structure can expand. If a non-zero value is specified, the maximum structure size will be greater than the initial structure size by an amount such that the total amount of data can increase by this percentage. For example, if the value 200 is specified, the initial size is enough to store the specified total number of items, and the maximum size is enough to store three times that number of items.

You use the results of these calculations to set the coupling facility resource manager (CFRM) INITSIZE and SIZE parameters in the CRFM policy.

For information about the CICS reserved space parameters that enable the coupling facility data table (CFDT) server to avoid a structure full condition, see Reserved space parameters and Avoiding structure full conditions.



dfha2c00100.html | Timestamp icon Last updated: Sunday, 4 June 2017