Understanding the affinities
The
Understanding the affinities present in the CICS region enables you to determine which of the them are most pervasive. If you decide that it is worth changing your application programs, it is generally more
The
The affinity report also lists affinities occurring between transactions that were not initiated from a terminal or are not CICS BTS transactions. These background transactions are known as background relations. This information is really for completeness, because such transactions cannot be dynamically routed.
To get complete information on affinities, use as many code paths as possible while running the Detector, because it can ®nd an affinity only if the commands that cause it have been executed. However, the Scanner detects all instances of affinity commands in the corresponding load library. So a comparison of the Reporter and Scanner outputs is very useful when establishing the full picture.
Important note
Both the Reporter and Scanner may identify commands that, on closer examination, do not cause real affinities. Relate the output from the Reporter and the Scanner to your knowledge of your applications, to distinguish between such commands and those causing real affinities that impact CICS dynamic routing.
For more information about interpreting the affinity report, see ªAppendix C. Useful tips when analyzing Transaction Affinities Utility reportsº on page 75.
Modifying affinity transaction groups
Consider making the following modi®cations to the affinity transaction groups before inputting them to the Builder:
vRemove false affinities
False affinities may arise because the sharing of a resource is done on a
vRemove affinity relation worsening
An affinity that has a relation of LUNAME, BAPPL,or USERID may be worsened | |
| to GLOBAL because the Detector has not seen enough examples of the affinity |
48 CICS Transaction Affinities Utility Guide