IBM OS manual Dening the VSAM les to CICS

#transids

is the number of transaction identi®ers in the CICS region.

#termids

is the number of terminal identi®ers in the CICS region.

Note: The amount of storage needed in the data space for the Builder is about 25% of the storage needed for the Detector.

The algorithm assumes that all affinities are represented, and that all transactions participate in all affinities, and that all transactions run at all terminals (the worst possible scenario). This gives a worst case ®gure.

For example, consider the worst case scenario of a CICS region with 500 different transaction IDs and 1000 terminals, where all transactions issue all affinity commands and all transactions run at all terminals.

For this scenario, the storage requirement for the Detector in the data space is:

Data space : 130 Megabytes

CAUAFF1 : 21 Megabytes

CAUAFF2 : 76 Megabytes

CAUAFF3 : 1 Megabyte

The space required for the data space is different than that required for the ®les because:

veach record has a storage overhead in the data space

vcertain tables are not saved to ®le

vkey length is ®xed per ®le, so short keys must be padded out

Notes:

1.The critical affinity type is temporary storage. The space required for all other affinity types together should be no more than 5MB.

2.The calculations in this section assume that you do not use unique counters when naming temporary storage queues. If you do use unique counters, the

space needed for temporary storage affinity types is much greater. For your calculations with unique counters, replace #transids * #termids by the number of unique queues.

De®ning the VSAM ®les to CICS

The CICS-supplied sample group, DFH$AFFY, contains de®nitions for:

vthree affinity data ®les (CAUAFF1, CAUAFF2 and CAUAFF3)

vthe affinity control ®le, CAUNCNTL

Change some of the attributes of these resource de®nitions to suit your own environment. To do this, use the CEDA transaction (or the DFHCSDUP utility) to:

1.COPY the sample group to a group of your own choosing. For example,

CEDA COPY GROUP(DFH$AFFY) TO(mygroup)

2.EXPAND group mygroup and change the following attributes appropriately: v For each resource de®nition, change the pre®xes of the VSAM ®les, as

de®ned by the CAUJCLCC and CAUJCLCA jobs.

vFor each resource de®nition, ensure that the LSRPOOLID speci®ed for each ®le is capable of handling the keylength de®ned for the ®le. If it isn't, change it so that it is. See Table 2 on page 21 for more information.

22 CICS Transaction Affinities Utility Guide