IBM Transaction Server OS - Manual (Page 30)

v Log offs and sign offs by intercepting messages DFHSN1200, DFHZC3462, and
DFHZC5966.
v Completion of CICS BTS activities and processes.
For more information, see “Appendix A. Details of what is detected” on page 65.
Worsening of transaction affinities relations
In some cases, the Detector may not detect enough occurrences (at least 10) of an
affinity command to be sure that the affinity is definitely with a terminal (LUNAME),
userid (USERID), or CICS BTS process (BAPPL). In such cases, the Detector
records the (worsened) affinity relation as GLOBAL instead of LUNAME or USERID.
Such relation worsening is flagged by the Detector and reported by the Reporter.
Worsening of transaction affinities lifetimes
If a pseudoconversation ends, and the resource still exists, the Detector deduces
that the lifetime is longer than PCONV, that is, one of LOGON, SIGNON, SYSTEM,
or PERMANENT.
If a log off or sign off occurs, and the resource still exists, the Detector deduces that
the lifetime is longer than LOGON or SIGNON: that is, either SYSTEM or
PERMANENT.
If a CICS BTS activity completes and the resource still exits, the lifetime is
worsened to process. If a CICS BTS process completes and the resource still exits,
the liftime is worsened to system.
In some cases, the Detector may not detect a log off or sign off, so cannot be sure
that the affinity lifetime is LOGON or SIGNON. In such cases, the Detector records
the (worsened) lifetime as SYSTEM or PERMANENT instead of LOGON or
SIGNON. For example, this occurs when the CICS region the Detector is running
on is a target region, because it is impossible in some cases to detect a log off or
sign off that occurs in a connected routing region.
Such lifetime worsening is flagged by the Detector, and reported by the Reporter.
What is not detected
The Detector does not detect EXEC CICS commands when the:
v Detector is not running
v Issuing program was translated with the SYSEIB option
v Command is an EXEC CICS FEPI command
v Command is not one that can cause transaction affinity
v Program name starts with “CAU” or “DFH”
v Program is a DB2 or DBCTL task-related user exit
v Program is a CICS user-replaceable module
v Transaction identifier does not match the prefix, if specified, for transactions to be
detected
v Command is not one of the affinity types specified to be detected
v Command is function shipped to a remote CICS region
v Inter-transaction affinity commands are used within the same task
14 CICS Transaction Affinities Utility Guide
|
|
|
|
|
|