„5… The total number of affinity records in the affinity data VSAM ®les. If the Detector was stopped by CICS crashing, and was in the middle of saving affinity data, this ®gure may be inaccurate. However, the ®gure is corrected the next time the Detector is started.
„6… The date and time when the Detector was last started, data was saved, and a change was made to an affinity table. The date is given in the format speci®ed by the DATFORM system initialization parameter.
„7… The total time that the Detector has been in the running and paused states since it was last started.
„8… The name, and current percentage occupied, of the MVS dataspace being used. (This is not displayed while in STOPPED state.)
„9… The message line used to display diagnostic messages.
„10… The keys that you can use to select functions to affect the operation of the Detector, or to get help information about it. This line displays all possible functions, not all of which are appropriate (or selectable) for a given state of the Detector.
Starting the collection of affinity data
When you can start collecting affinity data
You can start collecting affinity data only when the Detector is currently stopped.
To start collecting affinity data, use one of the methods shown in Table 3.
Table 3. Methods for starting data collection by the Detector
Where used | Command or function key |
|
|
Control display, CAFF01 | F5 function key „1… |
|
|
3270 terminal | CAFF START |
|
|
Console | F cicsjob, CAFF START „2… |
|
|
Application program | EXEC CICS START TRANSID('CAFF') FROM('START') „3… |
|
|
Notes:
„1… If you press the F5 function key of the CAFF01 screen, you are asked to con®rm that you want to start the recording of affinity data.
„2… cicsjob is the name of your CICS startup job.
„3… You can use this command from a program initiated during the third stage of CICS initialization: that is, a program speci®ed in the second part of the PLTPI list for the CICS region. For more information about using PLTPI programs, see the CICS Customization Guide.
Using one of the methods listed in Table 3 causes the Detector to record transaction affinities in the CICS region, until you pause or stop data collection by the Detector. Data is collected for only the affinity types that you have chosen to be detected (by specifying Y for the affinity type on the CAFF02 screen).
Chapter 5. Running the Detector 33
