IBM OS manual What is not detected, Worsening of transaction affinities relations

Models: OS

1 103
Download 103 pages 52.71 Kb
Page 30
Image 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 de®nitely 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 ¯agged 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 ¯agged by the Detector, and reported by the Reporter.

 

What is not detected

The Detector does not detect EXEC CICS commands when the:

vDetector is not running

vIssuing program was translated with the SYSEIB option

vCommand is an EXEC CICS FEPI command

vCommand is not one that can cause transaction affinity

vProgram name starts with ªCAUº or ªDFHº

vProgram is a DB2 or DBCTL task-related user exit

vProgram is a CICS user-replaceable module

vTransaction identi®er does not match the pre®x, if speci®ed, for transactions to be detected

vCommand is not one of the affinity types speci®ed to be detected

vCommand is function shipped to a remote CICS region

vInter-transaction affinity commands are used within the same task

14 CICS Transaction Affinities Utility Guide

Page 30
Image 30
IBM OS What is not detected, Worsening of transaction affinities relations, Worsening of transaction affinities lifetimes