IBM OS manual Commands detected by the Transaction Affinities Utility

Commands detected by the Transaction Affinities Utility

You can use the Transaction Affinities Utility to detect instances of the EXEC CICS commands listed in Table 1.

Table 1. Commands detected by the Transaction Affinities Utility

Inter-transaction affinity commands	Transaction-system affinity commands
ENQ	ENABLE PROGRAM
DEQ	DISABLE PROGRAM
READQ TS	EXTRACT EXIT
WRITEQ TS	INQUIRE
DELETEQ TS	SET
ADDRESS CWA	PERFORM
LOAD	RESYNC
RELEASE	DISCARD
GETMAIN SHARED	CREATE
FREEMAIN	WAIT EXTERNAL
RETRIEVE WAIT	WAIT EVENT
DELAY	WAITCICS
POST	CBTS STARTBROWSE
START	CBTS GETNEXT
CANCEL	CBTS ENDBROWSE
COLLECT STATISTICS

Notes:

1.The Scanner may detect some instances of these commands that do not cause an affinity. For example, all FREEMAIN commands are detected but only those used to free GETMAIN SHARED storage may cause affinity.

2.The Scanner also detects MVS POST SVC calls and MVS POST LINKAGE=SYSTEM non-SVC calls, because of their tie-up with the various EXEC CICS WAIT commands.

3.The Transaction Affinities Utility does not search for transient data and ®le control EXEC CICS commands. They are assumed not to cause affinity because you can de®ne transient data and ®le control resources as remote (in which case the request is function-shipped, causing no affinity problem).

4.The Detector ignores commands that target remote resources and are function shipped, because by function shipping the command there is no affinity problem.

5.The Scanner and Detector do not search for commands issued by any program named CAUxxxxx or DFHxxxxx, because CICS programs are not considered part of the workload. Also, the Detector does not search for commands issued from:

vDB2® and DBCTL task-related user exits

vUser-replaceable modules

6.There are other ways in which transactions can cause affinity with each other, but they are not readily detectable by the affinity utility program because they do not take place via the EXEC CICS API.

7.The Detector lists WAIT commands as transaction-system affinities because only half of the affinity can be detected. (The Detector does not detect MVS POST calls or the hand posting of ECBs.)

8. The Detector and the Report ignore ENQ and DEQ commands that specify an

ENQSCOPE name.

Chapter 2. Introducing the Transaction Affinities Utility 11