A sample report output by the Affinities Reporter.
The sample report below shows an example report for two affinities, a TS queue affinity and a CWA affinity. Only those affinity types were selected, as shown.
CICS INTERDEPENDENCY ANALYZER 2007/09/24 Page 1
AFFINITY TYPE REPORTING OPTIONS Applid=CICSPDN1
Affinity Type Reporting Message
------------- --------- --------------------------------------
1
Inter-Transaction Affinities 2
----------------------------
CWA Yes
CANCEL No
ENQ No
GETMAIN No
LOAD No
RETRIEVE No
TS Yes
Transaction-System Affinities
-----------------------------
COLLECT No
DISCARD No
ENABLE No
EXTRACT No
INQUIRE No
PERFORM No
RESYNC No
WAIT No
CREATE No
CICS INTERDEPENDENCY ANALYZER 2007/09/24 Page 2 3
INTER-TRANSACTION AFFINITIES REPORT FOR ADDRESS CWA Applid=CICSPDN1
Trangroup : CW.00000001
Affinity : GLOBAL
Lifetime : SYSTEM
Tranid Program Offset Usage Command Terminal CBTS Task Link3270
------ -------- -------- ------ ---------------------- -------- --------- --------
AUXX AUXXTST 000000CC 1 ADDRESS CWA Yes No No
CWA1 AUCWA FFFFFFFF 2 Yes No No
Total Transactions : 2
Total Programs : 2
Notes for the sample report output by the Affinities Reporter, above:
1 Incorrect affinity types
This column lists any affinity types that were specified incorrectly on the CMDGRPS DD statement of the CIUAFFRD or CIUAFFRP job.
2 Affinity types reported
This column lists any affinity types that were selected for reporting; that is, those affinity types specified correctly on the CMDGRPS DD statement of the CIUAFFRD or CIUAFFRP job. The affinity types are listed under their associated affinity category: inter-transaction or transaction-system.
3 Affinities reports
This offset is not the same as the offset given by the Load Module Scanner, which is the offset of the command argument 0 declaration from the start of the load module.
If a negative offset (X'FFFFxxxx') is given, individual affinity commands cannot be directly located within a program. The program must be scanned for every instance of the affinity command, because there might be more than one.
0 <= usage count < 10, save flag set every increment
10 <= usage count < 100, save flag set every 10 increments
100 <= usage count < 5000, save flag set every 100 increments
5000 <= usage count neither increment nor save flag set
If the usage count is 1+, at least one example of the affinity was seen but the total number of occurrences of that affinity is unknown.
The word Mix in this column indicates that a particular EXEC CICS command was issued by a transaction initiated from a terminal and also issued by the transaction when it was initiated with no associated terminal.