Affinity-related commands
This section lists the affinity-related EXEC CICS® commands detected by the Collector and the Load Module Scanner. All commands listed here are capable of causing affinities; they might or might not actually do so.
In Affinity-related CICS API and SPI commands detected
by the CICS IA Collector and
the CICS IA Load
Module Scanner:
- The left-hand column shows the CICS API commands that might create inter transaction affinities.
- The center column shows the CICS API commands that might create transaction system affinities.
- The right-hand column shows the CICS SPI commands that might create transaction system affinities.
CICS API commands that might create inter-transaction affinities | CICS API commands that might create transaction-system affinities | CICS SPI commands that might create transaction-system affinities |
---|---|---|
ENQ |
STARTBROWSE ACTIVITY |
ENABLE PROGRAM |
Notes:
- The CICS IA Load Module Scanner might 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 might cause an affinity.
- The CICS IA Load Module Scanner also detects MVS™ POST SVC calls and MVS POST LINKAGE=SYSTEM non-SVC calls, because of their relationship to the various EXEC CICS WAIT commands.
- The CICS IA Collector does not search for transient data and file control EXEC CICS commands. They are assumed not to cause affinities because you can define transient data and file control resources as remote, in which case the request is function-shipped, causing no affinity problem.
- The Collector ignores commands that target remote resources and are function-shipped, because function-shipped commands do not cause affinity problems.
- The Collector and the CICS IA Load
Module Scanner do not search for commands issued by any program named
CAUxxxxx, CIUxxxxx, or DFHxxxxx, because CICS programs are not considered part of the
workload. Also, the Collector does not search for commands issued
from:
- DB2® and DBCTL task-related user exits
- User-replaceable programs
- There are other ways in which transactions can cause affinity with each other, but they are not readily detectable by the Collector because they do not take place through the EXEC CICS API.
- The Collector lists WAIT commands as transaction-system affinities because only half of the affinity can be detected. The Collector does not detect MVS POST calls or the hand posting of ECBs.
- The Collector and the CICS IA Affinities Reporter ignore ENQ and DEQ commands that specify an ENQSCOPE name.
For details about affinity-related commands see Commands monitored for potential affinities.