Modifying affinity-transaction-group definitions
Modifications to consider before providing affinity-transaction-group definitions to the Builder.
- Remove any false affinities that might arise because the sharing of a resource is done on a read-only basis, making it possible for the resource to be replicated across cloned CICS® regions. The prime example of this is a read-only CWA, where the CWA is set up at CICS startup, for example, from a PLTPI program, and only read afterward. An alternative way to remove this false affinity is to prohibit detection of ADDRESS CWA by the Collector.
- Remove affinity relation worsening. An affinity that has a relation of LUNAME, BAPPL, LINK3270, or user ID might be worsened to GLOBAL because the Collector has not seen enough examples of the affinity to be convinced that it is related to a terminal, user ID, a BTS process or activity, or a Link3270 bridge. Change it to LUNAME, USERID, BAPPL, or LINK3270, and correct the lifetime, if you know that the affinity really is related to a terminal, user ID, a BTS process or activity, or a Link3270 bridge facility. You might want to prevent worsening by specifying WORSEN=NO.
- Remove affinity lifetime worsening; an LUNAME affinity with a lifetime of LOGON, or a USERID affinity with a lifetime of SIGNON, might be worsened to SYSTEM or PERMANENT because the Collector cannot always observe log offs or signoffs. Change this to LOGON or SIGNON if you know that to be the correct lifetime.
- You can change LUNAME affinity relation to USERID. An LUNAME affinity group might be both LUNAME and USERID, because all instances of all transactions in the group were initiated from the same terminal by the same USERID. This affinity group appears in the report as LUNAME, because LUNAME takes precedence. If you know that the affinity is primarily USERID related, change the affinity to USERID. This affinity might be indicated by other, similar, affinity groups appearing in the report with USERID.
- You can add WAIT affinities. The Affinities Reporter reports the use of WAIT EVENT, WAITCICS, and WAIT EXTERNAL commands as transaction-system affinities, because the Collector cannot detect the corresponding posting of the ECBs being waited on. Identify the posting transactions and create affinity transaction groups to describe the affinities. The output from the Load Module Scanner might be particularly useful here, because it finds programs that issue MVS™ POST commands.
- You can add other affinities. Load Module Scanner output or your knowledge of your applications might identify additional affinities. Create affinity transaction groups to describe them.
- You can add GETMAIN storage sharers. The Collector cannot detect transactions that share storage other than by EXEC CICS commands. Although it detects GETMAIN SHARED and FREEMAIN affinities, the address of the storage might have been passed to a third transaction. Add such transactions to the affinity transaction group.