Chapter 5. Running the Detector
This chapter describes how to run the Detector that runs in a CICS region looking for instances of API commands that could cause transaction affinity.
This chapter describes how to perform the following functions:
vªDisplaying the Detector control screenº on page 32
vªStarting the collection of affinity dataº on page 33
vªPausing the collection of affinity dataº on page 34
vªResuming the collection of affinity dataº on page 34
vªStopping the collection of affinity dataº on page 35
vªChanging the Detector optionsº on page 36
vªDetector errorsº on page 39
The commands looked for are those listed in ªCommands detected by the
Transaction Affinities Utilityº on page 11.
You can run the Detector either at a CICS
For an overview of the Detector, see ªThe Detector componentº on page 12.
You can control the Detector by:
vChanging the state
This is described in topics ªStarting the collection of affinity dataº on page 33 through ªStopping the collection of affinity dataº on page 35.
vChanging the options
The options that you can select are shown in Figure 7 on page 36, and described in ªChanging the Detector optionsº on page 36.
You can optimize the performance of the Detector; that is, you should consider doing the following:
vPausing the collection of data during peak workloads. You can continue the collection of data when the workloads have decreased.
vCollecting data for one affinity type at a time. This can be of particular value for the temporary storage affinity type.
vCollecting data for a restricted set of transaction identi®ers by specifying the pre®x of those transactions in which you are interested.
For information about how to specify the affinity types and transaction identi®er pre®x for which data is to be collected, see ªChanging the Detector optionsº on page 36.
© Copyright IBM Corp. 1994, 1999 | 31 |