Change CICS monitoring options.
SET MONITOR >>-SET MONITOR--+------------------+--+-------------------+-----> +-CONVERSEST(cvda)-+ +-EXCEPTCLASS(cvda)-+ +-CONVERSE---------+ +-EXCEPT------------+ '-NOCONVERSE-------' '-NOEXCEPT----------' >--+-----------------------------------+--+-----------------+---> +-FREQUENCY(data-value)-------------+ +-PERFCLASS(cvda)-+ | .-------------------------------. | +-PERF------------+ | V | | '-NOPERF----------' '---+---------------------------+-+-' +-FREQUENCYHRS(data-value)--+ +-FREQUENCYMIN-(data-value)-+ '-FREQUENCYSEC(data-value)--' >--+-------------------+--+--------------+----------------------> +-RESRCECLASS(cvda)-+ +-STATUS(cvda)-+ +-RESRCE------------+ +-ON-----------+ '-NORESRCE----------' '-OFF----------' >--+-------------------+--------------------------------------->< +-SYNCPOINTST(cvda)-+ +-SYNCPOINT---------+ '-NOSYNCPOINT-------'
Conditions: INVREQ, NOTAUTH
For more information about the use of CVDAs, see CICS-value data areas (CVDAs).
The SET MONITOR command allows you to switch CICS monitoring on or off, to modify the settings of the monitoring options, and to select the classes of monitoring data to be recorded.
CICS monitoring is controlled by a master switch (the STATUS option). Monitor data is accumulated only while the STATUS option has the value ON, and only for tasks that begin while STATUS is ON.
When monitoring is active, CICS accumulates two types of data for each individual task:
Additional switches determine which of these classes of monitor data are written to the SMF data set. Exception data is written only if EXCEPTCLASS is EXCEPT; transaction resource data is written only if RESRCECLASS is RESRCE; and performance data only if PERFCLASS is PERF. For an individual task, class data is recorded only if the class switch is on both at the time the task starts and at the time that class of data is written out.
Exception class data is written at the end of the event to which the exception corresponds. Performance class and transaction resource data is written only at these specific times:
If you change STATUS from ON to OFF, CICS stops accumulating and recording monitor data. Data for tasks in flight that is not already recorded is lost even if you turn monitoring back on before end of task.
Furthermore, if you are recording performance data, you should specify NOPERF in any command that sets monitoring OFF, to ensure that buffers containing recorded data for completed tasks are flushed; some of this data can be lost otherwise.
If you leave STATUS on but turn one of the recording options off and then back on during a task, however, data loss depends on the class, as follows:
The frequency interval can be expressed in several ways:
Whichever method you use, the interval value must be either zero or in the range from 1 minute to 24 hours. Zero means CICS is to produce performance records only at task end, regardless of the length of the task.
In addition, if you use FREQUENCY or more than one of the separate options, the minutes and seconds portions of the value must not be greater than 59 (FREQUENCYMIN or FREQUENCYSEC used alone can exceed 59). For example, you could express an interval of 1 hour and 30 minutes in any of the following ways: