Limited support

   

BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for CICS, version 7.3

Calculating primary record specification

The size of the CMRDETL data sets is a factor of the length of time that you want to preserve T6E records for online history views.

A simple calculation of the estimated number of transactions per day multiplied by the maximum number of days provides the general size. This calculation corresponds to the formula:

CMRDETL Size = (transactions per day) x (number of days)

If you are using a single CMRDETL data set, it must be large enough to contain data for all the days that you want to preserve, which means that the primary record specification should be equal to the CMRDETL size by using the above formula.

If you are using dual CMRDETL data sets, the CMRDETL size can be distributed between the individual data sets.

Although VSAM allocates space according to the specified number of records, other factors such as the method of loading records and differences in the compressed size of the T6E records will affect the ability of VSAM to completely use all of a given control area. It is a good idea to increase the primary record specification by 25%.

For optimum VSAM performance, the primary allocation for CMRDETL should never be less than one cylinder.

The secondary extent should always be zero.

Was this page helpful? Yes No Submitting... Thank you

Comments