10. MODIFICATION › 10.1 Checklists › 10.1.12 Process CMF User Clocks, Counters, and User Area
10.1.12 Process CMF User Clocks, Counters, and User Area
The CICS Monitoring Facility (CMF) allows application
programs to add data fields to the transaction records in the
performance class and accounting class. CMF calls these data
fields user clocks and counters (it supports 256) and the
user area (it allows one user area per ENTRYNAME defined by
the DFHMCT TYPE=EMP macro).
The CA MICS CICS Analyzer supports user clocks, user
counters, and the user area from the performance class only.
Data from the accounting class is accessible during the daily
input processing step in DAY040; however, you must provide
the necessary SAS code in an exit routine to create
observations or files based on this data.
By default, the CA MICS CICS Analyzer supports nine user
clocks, 50 user counters, and one user area (stored in two
SAS variables due to the limit of 200-byte length for
character variables), though the support is shipped inactive.
The ENTRYNAME for these fields must be USER (the default name
supplied by CICS). If you have specified an ENTRYNAME other
than USER and you would like to process that data through
CA MICS, refer to Section 10.1.15 of this guide for more
information.
If you choose to activate this support and the defaults do
not meet your installation's needs, you can define and
activate up to 99 user clocks and user counters.
If your site has more than one CICS region, be certain to get
the needed information from each region before activating
additional user clocks and counters in the CICS Analyzer. If
you activate clocks or counters or a user area for one CICS
region, the data elements are carried for the other regions
and may contain missing values if the other regions have no
user clocks or counters.
To add or activate additional user clocks and user counters,
follow Checklist 12.
****************************************************
* *
* CHECKLIST 12 - ADD USER CLOCKS AND USER COUNTERS *
* *
****************************************************
___ 1. Determine the number of user clocks in each CICS
region processed by the CICS Analyzer by doing the
following:
a. Ask your CICS system programmer.
-or-
b. If you are running CMF, review the DFHMCT
TYPE=EMP macro specifications and make note of
the PERFORM= statement. The number of clocks is
equal to the largest number specified in the
SCLOCK statement. If there are no SCLOCK
statements, no clocks have been defined.
___ 2. Determine the number of user counters in each CICS
region processed by the CA MICS CICS Analyzer by
doing the following:
a. Ask your CICS systems programmer.
-or-
b. If you are running CMF, review the DFHMCT
TYPE=EMP macro specifications and make note of
the PERFORM= statement. The number of counters
is equal to the largest number specified in the
MLTCNT(x,y) statement.
___ 3. Modify or add NAME (or NAMX if you using
ESSENTIAL=ALL support) statements to provide the
number of clocks and counters you need in
sharedprefix.MICS.GENLIB(CICGENIN). For each clock,
you must activate or add NAME statements for data
element CICPCKnn. For each counter, activate or add
NAME statements for CICPCTnn, where nn ranges from 01
to 99. Note that these data elements are defined in
THREE files and must be activated in the CICCSW, and,
optionally, CICCSU or CICCAU files. See Section
4.2.4 of the System Modification Guide (SMG) for
details on modifying NAMX or NAME statements.
___ 4. The user clocks and user counters are defined as
common data elements, as they exist in multiple CICS
files in the CA MICS Data Base. Therefore, for each
NAME (or NAMX) statement that you added in step 3,
you must add the corresponding ALIAS, TYPE, and NAME
statements in sharedprefix.MICS.GENLIB($DEGENIN).
In addition, you can change the format and length of
the clocks and counters by changing the TYPE
statement in the $DEGENIN member. See Section
4.2.4.4 of the SMG for details.
___ 5. Submit sharedprefix.MICS.CNTL(CICCGEN).
