You can stop collecting dependency or affinity data on a particular region only when the Collector is running or paused on that region.
To stop collecting data on a specified CICS® region, use one of the methods shown in Table 1.
Where used | Command or function key |
---|---|
CINT transaction's Operations Menu, CIU100 | Type 2 against a listed CICS APPLID and press Enter. You are asked to confirm that you want data collection to be stopped on the specified region. |
CINT transaction's Operations Menu, CIU100 | If there is more than one CICS region listed on the Operations Menu, you can type 2 against the first CICS APPLID in the list ALL and press Enter to stop the Collector on all the regions. You are asked to confirm that you want data collection to be stopped on all regions. |
3270 terminal | CINT STOP 1 |
3270 terminal | CINT STOPALL 2 |
Console | F cicsjob, CINT STOP 3 |
Console | F cicsjob, CINT STOPALL 4 |
Application program | EXEC CICS START TRANSID('CINT') FROM('STOP') 5 |
Application program | EXEC CICS START TRANSID('CINT') FROM('STOPALL') 6 |
Using one of the methods in Table 1 stops the Collector recording any dependency or affinity data in the CICS region until you next start the Collector. Stopping the collector also destroys the data space, and saves the data collected to the VSAM data files.
If there are many data records to be saved, the Operations Menu screen might be frozen for some time, until the records have been saved.
You might want to stop the Collector, on a specified CICS region, when it has detected all dependencies there. You can find out when this has happened from the Collector Statistics Menu screen, CIU150; see Displaying Collector statistics for a specified region. When the Collector has detected all dependencies, the “Date/time of last change” field changes very infrequently and, if optional periodic saves are performed, the “Records written last save” field is consistently near zero.