Producing affinity-transaction-group definitions

The Affinities Reporter produces affinity-transaction-group definitions suitable for input to the Builder, but not to CICSPlex® SM.

Each definition consists of a unique transaction group name, a relation, a lifetime, and a set of transaction IDs (tranids).

Not every affinity in the report appears as an affinity transaction group. In particular, transaction-system affinities do not appear, because they are not of interest to a dynamic routing program; nor, for the same reason, do transactions that were not initiated from a terminal, nor by BTS, nor by the Link3270 bridge mechanism.

Figure 1 shows a sample set of definitions to match the report in Figure 1.
Note:
  1. The transaction group name is not a valid CICSPlex SM transaction group name, because the latter must be eight characters or less; it is used only as a cross-reference to the report.
  2. MATCH or STATE attributes are not generated on CREATE TRANGRP commands, because those attributes are relevant only to the combined affinity transaction groups.
  3. The HEADER statement is generated so that the Builder can detect a new data set in its input concatenation. It also gives the CICS® APPLID and the date and time of the last Collector save. For more information see HEADER statements.
Figure 1. Sample basic affinity-transaction-group definitions
* HEADER APPLID(CICSPDN1)  SAVEDATE(2007/09/24)  SAVETIME(10:11:45);
*
* Generated by the CICS Interdependency Analyzer Reporter on 2007/09/24
* Note: NOT suitable for input to CICSPlex SM
*
CREATE TRANGRP NAME(CW.00000001) AFFINITY(GLOBAL  ) AFFLIFE(SYSTEM   )
               DESC(ADDRESS CWA                   );
  CREATE DTRINGRP TRANGRP(CW.00000001) TRANID(AUXX);
  CREATE DTRINGRP TRANGRP(CW.00000001) TRANID(CWA1);
*
CREATE TRANGRP NAME(TS.00000001) AFFINITY(LUNAME  ) AFFLIFE(PCONV    )
               DESC(TS.LOCA1         D7D6C3C1F14040404040404040404040);
  CREATE DTRINGRP TRANGRP(TS.00000001) TRANID(AFTD);
  CREATE DTRINGRP TRANGRP(TS.00000001) TRANID(AFTR);
  CREATE DTRINGRP TRANGRP(TS.00000001) TRANID(AFTW);
*
CREATE TRANGRP NAME(TS.00000002) AFFINITY(LUNAME  ) AFFLIFE(PCONV    )
               DESC(TS.LOCA2         D7D6C3C1F24040404040404040404040);
  CREATE DTRINGRP TRANGRP(TS.00000002) TRANID(AFTD);
  CREATE DTRINGRP TRANGRP(TS.00000002) TRANID(AFTR);
  CREATE DTRINGRP TRANGRP(TS.00000002) TRANID(AFTW);
*
CREATE TRANGRP NAME(TS.00000003) AFFINITY(LINK3270) AFFLIFE(FACILITY )
               DESC(TS.TS_AFFINITY   E3E26DC1C6C6C9D5C9E3E84040404040);
  CREATE DTRINGRP TRANGRP(TS.00000003) TRANID(TSW1);

After these definitions have been created, you can edit them to add extra definitions for affinities that the Collector could not detect, or to modify definitions in the light of further knowledge about the affinity; for example, to correct a worsened lifetime. The report output from the Load Module Scanner might be particularly useful at this stage. See Running the affinity report.


Concept Concept

Feedback


Timestamp icon Last updated: Friday, 22 November 2013


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