IBM CICS Transaction Server for OS/390 SC33-1686-02 - Manual (Page 206)

CEMT SET MONITOR
AVailable( value)
specifies the maximum number of sessions within the
group that can be concurrently allocated for use. This
value has to be the same for both sides involved in the
session.
CLosed
CICS is to release all sessions within the group. The
sessions are quiesced and unbound. No further sessions
can be acquired by another CICS system. No further
activity is possible on the sessions within the group until
the group is reacquired by the same CICS system in
which it has been closed.
COnnection( value)
specifies an identifier (1–4 characters) defined for an
IRC or ISC connection.
CEMT SET MONITOR
Function: Change the status of monitoring.
Description: SET MONITOR allows you to select the
classes of monitoring data you want collected, switch
monitoring on or off, and set the status of monitoring options.
For programming information on the monitoring classes, see
the
CICS Customization Guide.
Notes:
1. When you change the status of CICS monitoring from
OFF to ON, CICS starts to accumulate monitoring data,
and to write monitoring records for the active monitoring
classes, for all tasks that start after the change is made.
The monitoring status of tasks being processed is not
affected.
2. When you change the status of CICS monitoring from
ON to OFF, CICS stops writing monitoring data
immediately. No monitoring data is accumulated for
tasks that start after the change is made.
3. The monitoring class settings can be changed
irrespective of whether monitoring is ON or OFF.
If monitoring is OFF, you can change the class settings
as required in preparation for the next time STATUS is
set to ON.
If monitoring is ON, changes to the class settings have
the following effects:
a. Changing a class from not-active to active has no
effect on the data written for running tasks.
b. Changing a class from active to not-active prevents
monitoring data for that class being written for
running tasks as follows:
Sysevent
Monitoring data is not written at
transaction termination.
Performance
Any performance class data remaining
in the output buffer is recorded, and no
further data is collected.
Exception
Monitoring data is not written at the
completion of the exception condition.
c. Exception class and performance class data are
gathered during the life of a running transaction.
When you change these settings, you should be
aware of their impact on transactions that are
running. For example, if a transaction is started
when the performance class is set to PERF and
monitoring is ON, performance class data is
accumulated for that transaction. If you switch the
performance class to NOPERF while the transaction
is running, and then back to PERF before the
transaction ends, performance data will be missing
from the final monitoring data for that transaction,
188 CICS Supplied Transactions