Identifying intertransaction affinities

Intertransaction affinities, which require related transactions to be processed by the same target region, prevent optimum workload distribution. In general, they arise either because of the way in which one transaction passes data to another, or because of a requirement to coordinate the processing of two or more transactions. Identifying affinities isn't always easy, but there are some methods you can use.

For example, you can review application design documentation or source code; you can run CICS®traces; or you can use the IBM CICS Interdependency Analyzer for z/OS®. For a detailed discussion of intertransaction affinities and ways of identifying them, see the publication Dynamic Transaction Routing in a CICSplex.

Having identified any affinities in a workload, you should make every attempt to remove them. If you cannot remove them completely, gauge the duration of the affinity and try to minimize it. You can define an intertransaction affinity to CICSPlex® SM as lasting:
  • While the user's session is active
  • For the duration of the terminal session
  • While the target region remains active
  • While the workload is active
  • For the duration of a pseudoconversation
  • While the BTS activity is active
  • While the BTS process is active

Be aware that CICSPlex SM must honor an active affinity: if an affinity is active but the target region becomes unavailable, the transaction isn't routed. In the case of a BTS transaction, BTS will wait for the region to start.



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