IBM OS manual Using the affinity 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. For more information about MATCH and STATE attributes, see page 55.

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 Detector save, all obtained from the CAUCNTL control ®le. For more information about HEADER statements, see ªHEADER statementsº on page 58.

*	HEADER APPLID(CICSPDN1) SAVEDATE(95/11/24) SAVETIME(10:11:45);
*

*Generated by the CICS Transaction Affinities Utility (Reporter) on 1995/11/25

*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	D3D6C3C1F1404040	);
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	D3D6C3C1F2404040	);

CREATE DTRINGRP TRANGRP(TS.00000002) TRANID(AFTD);

CREATE DTRINGRP TRANGRP(TS.00000002) TRANID(AFTR);

CREATE DTRINGRP TRANGRP(TS.00000002) TRANID(AFTW);

Figure 9. Sample basic affinity transaction group de®nitions

Once these de®nitions have been created, you can edit them to add extra de®nitions for affinities that the Detector could not detect, or to modify de®nitions in the light of further knowledge about the affinity (for example, to correct a worsened lifetime). The report output from the Scanner may be particularly useful at this stage. (See ªUsing the affinity reportº.)

Using the affinity report

The affinity report has two main purposes:

1.To help you understand the affinities present in the CICS region concerned.

2.To help you modify the affinity transaction group de®nitions before they are input to the Builder, if such modi®cation is required.

You need to be able to investigate whether any application changes could reduce the amount of affinity.

Notes:
1.	Assume that the affinity information is complete.
2.	Assume that any worsening of affinity relation or affinity lifetime by the Detector
	does not create too pervasive an affinity (this makes dynamic routing less
	effective).

Chapter 6. Running the Reporter 47