Filter
Top Products
Usage The number of times that this particular EXEC CICS command (with the
transaction, program, and offset values reported) taking part in the affinity,
up to a limit of 5000.
Note: The usage count is an indication of the relative importance of the
affinity, and is not a completely accurate usage count. For
performance reasons, when the usage count is incremented by the
Detector, 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+’, it means that at least one example of the affinity
was seen but that the total number of occurrences of that affinity is
unknown.
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. (This does not include
ATI-started transactions.)
The word Mix in this column is used to indicate 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.
BTS Task
Whether it is a CICS BTS task or not.
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.
Producing affinity transaction group definitions
The 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 tranids.
Not everything that appears 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 do transactions that were not initiated
from a terminal (for the same reason).
Figure 9 on page 47 shows a sample set of definitions to match the report in
Figure 8 on page 43.
Notes:
1. The transaction group name is not a valid CICSPlex SM transaction group
name, because the latter must be eight characters; it is used only as a
cross-reference to the report.
46 CICS Transaction Affinities Utility Guide
|
|
|
|
|
|