SET MONITOR

Change CICS monitoring options.

Read syntax diagramSkip visual syntax diagramSET 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).

Description

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:

Options

CONVERSEST(cvda)
specifies how CICS is to record performance data for conversational tasks (tasks that wait for terminal or session input).
CONVERSE
CICS is to produce a performance class record each time the task waits for terminal input as well as at task end, representing the part of the task since the previous wait (or task start). (Waits occur during execution of a CONVERSE command or a RECEIVE command that follows a SEND.)
NOCONVERSE
CICS is to accumulate performance data across terminal waits and produce a single performance class record.
EXCEPTCLASS(cvda)
specifies whether the exception class of monitoring data is to be recorded when monitoring is active. CVDA values are:
EXCEPT
Exception data is to be recorded.
NOEXCEPT
Exception data is not to be recorded.
FREQUENCY(data-value)
specifies the interval at which CICS is to produce performance class records for long-running tasks. If a task runs longer than the frequency interval, CICS records its performance data separately for each interval or fraction.

The frequency interval can be expressed in several ways:

  • A 4-byte packed decimal composite, in the format 0hhmmss+, using the FREQUENCY option.
  • With separate hours, minutes, and seconds, using the FREQUENCYHRS, FREQUENCYMIN, and FREQUENCYSEC options. You can use these options singly or in any combination.

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:

  • FREQUENCY(13000)
  • FREQUENCYHRS(1), FREQUENCYMIN(30)
  • FREQUENCYMIN(90)
  • FREQUENCYSEC(5400)
FREQUENCYHRS(data-value)
specifies the hours component of the frequency interval, in fullword binary form (see the FREQUENCY option).
FREQUENCYMIN(data-value)
specifies the minutes component of the frequency interval, in fullword binary form (see the FREQUENCY option).
FREQUENCYSEC(data-value)
specifies the seconds component of the frequency interval, in fullword binary form (see the FREQUENCY option).
PERFCLASS(cvda)
specifies whether the performance class of monitoring data is to be recorded when monitoring is active. CVDA values are:
NOPERF
Performance data is not to be recorded.
PERF
Performance data is to be recorded.
RESRCECLASScvda)
specifies whether CICS transaction resource monitoring is to be active or disabled. CVDA values are:
NORESRCE
CICS is not to perform transaction resource monitoring . No transaction resource data is accumulated or written to SMF.
RESRCE
CICS is to perform transaction resource monitoring . Data is accumulated for the resources that are specified in the MCT (for example, CICS files) and written to SMF.
STATUS(cvda)
specifies whether CICS monitoring is to be active or disabled. CVDA values are:
OFF
Monitoring is not to occur. No data is accumulated or written out, irrespective of the settings of the monitoring data classes.
ON
Monitoring is to be active. Data is accumulated for all classes of monitor data, and written out for those classes that are active.
SYNCPOINTST(cvda)
specifies whether CICS is to record performance class data separately for each unit of work (UOW) within tasks that contain multiple UOWs. A UOW within a task ends when a syncpoint occurs, either explicitly (a SYNCPOINT command) or implicitly (a DL/I TERM call, for example, or task end); a new UOW begins immediately, except at end of task. When rollback occurs on a syncpoint, the UOW does not end. CVDA values are:
NOSYNCPOINT
Performance data is to be combined over all UOWs in a task.
SYNCPOINT
Performance data is to be recorded separately for each UOW.

Conditions

INVREQ
RESP2 values:
1
STATUS has an invalid CVDA value.
2
PERFCLASS has an invalid CVDA value.
3
EXCEPTCLASS has an invalid CVDA value.
5
CONVERSEST has an invalid CVDA value.
6
SYNCPOINTST has an invalid CVDA value.
7
The FREQUENCY value is invalid. (The hours exceed 24, minutes or seconds exceed 59, or total value is out of range.)
8
The FREQUENCYHRS value is out of range.
9
The FREQUENCYMIN value is out of range.
10
The FREQUENCYSEC value is out of range.
NOTAUTH
RESP2 values:
100
The user associated with the issuing task is not authorized to use this command.
[[ Contents Previous Page | Next Page Index ]]