Affinity report

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
Figure 1. A sample report output by the Affinities Reporter

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

For each affinity transaction group, a report lists appropriate characteristics of the affinities, explained in the following notes.
Trangroup
The name of the affinity transaction group, assigned by the Affinities Reporter. This name is used only to cross-reference the group to the corresponding affinity-transaction-group definition in the data set specified on the TRANGRPS DD statement, for this run of the Affinities Reporter. The Trangroup value for an affinity transaction group might vary from one run to another of the Affinities Reporter.
Affinity
The affinity relation. If appropriate, this entry also indicates whether the relation was worsened from a less restrictive relation.
Lifetime
The affinity lifetime. If appropriate, this entry also indicates whether the lifetime was worsened from a less restrictive lifetime.
Queue (resource)
The resource causing the affinity. This entry might be the name of the resource, for example, Queue : LOCA1 (D7D6C3C1F14040404040404040404040) as shown, or the address of the resource, depending on the type of affinity. An unprintable character appears as a period (.).
Recoverable
Whether or not the resource is recoverable. For TS queues, this entry also indicates whether the queue is in auxiliary or main temporary storage.
Terminal Id
The identifier of the terminal at which the transactions taking part in the affinity were initiated. This information is available only for TS queue affinity and is meaningful only if the affinity is LUNAME or worsened from LUNAME to GLOBAL. Therefore, the terminal identifier is included in the report only in these cases.
Tranid
The identifier of each transaction taking part in the affinity. An affinity transaction group can contain only one transaction ID. An example of such a situation is when each part of a pseudoconversation accesses a TS queue and each part runs under the same transaction ID.
Program
The name of each program taking part in the affinity.
Offset
The offset from the load point of the BALR instruction to the EXEC CICS® command causing the affinity. The Affinities Reporter produces a negative offset (X'FFFFxxxx') if it cannot determine an offset; that is, if the offset calculated is not within the program. A negative offset might indicate that the program, or perhaps language runtime code has passed control to another program by using a non-CICS mechanism; for example, a COBOL dynamic call.

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.

Usage
The number of times that this particular EXEC CICS command, with the transaction, program, and offset values reported, takes part in the affinity, up to a limit of 5000.
The usage count is an indication of the relative importance of the affinity. It is not a completely accurate usage count. For performance reasons, when the usage count is incremented by the Collector, the “save to file” flag is not necessarily set to indicate that the record needs to be saved to the data file. The save flag is set as follows:
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.

Command
The EXEC CICS command causing the affinity.
Terminal
Whether this particular EXEC CICS command, with the transaction, program, and offset values reported, was ever issued by a transaction initiated from a terminal; that is, started as a result of terminal input or for an EXEC CICS RETURN TRANSID command. ATI-started transactions are not included.

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.

CBTS Task
Whether this particular EXEC CICS command, with the transaction, program, and offset values reported, was ever issued by a BTS task.
Link3270
Whether this particular EXEC CICS command, with the transaction, program, and offset values reported, was ever issued by a transaction initiated by the Link3270 bridge mechanism.
Total Transactions
The total number of different transactions in the affinity transaction group.
Total Programs
The total number of different programs in the affinity transaction group.

Concept Concept

Feedback


Timestamp icon Last updated: Friday, 8 February 2013


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