What are transaction affinities?

CICS® transactions use many different techniques to pass data from one to another. Some techniques require that the transactions exchanging data must execute in the same CICS region, and therefore impose restrictions on the dynamic routing of transactions. If transactions exchange data in ways that impose such restrictions, an affinity exists between them.

There are two categories of affinity, inter transaction affinity; see Inter transaction affinity and transaction system affinity; see Transaction system affinity.

The restrictions on dynamic routing caused by transaction affinities depend on the duration and scope of the affinities. Clearly, the ideal situation for a dynamic routing program is that no transaction affinity exists, indicating no restriction in the choice of available target regions. However, even when transaction affinities do exist, limits to the scope of these affinities are determined by the affinity relations; see Affinity relations and Affinity lifetime; see Affinity lifetimes.

CICS IA cannot detect affinities in the following types of dynamically-routed requests: For these types of dynamically routed requests, you must review your application to determine whether or not it is suitable for dynamic routing.

Concept Concept

Feedback


Timestamp icon Last updated: Friday, 7 February 2014


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic///ciuug60.html