Previous Topic: CMFUTIL1 - Create Dictionary for CICS 1.7 through 2.1.2

Next Topic: CA JARS CMF Dictionary Record Layout


CMFUTIL2 - Create Dictionary for CICS 3.2 and above

The CMFUTIL2 utility contains two steps. The first step executes the IBM DFHMNDUP utility to build the CICS CMF dictionary record. The record is built using both predefined CICS fields and user-defined fields that are extracted from the MCT for the respective CICS region. Please refer to the CICS/ESA Operations Guide for a description of the control statements used with this utility.

Step two executes program CAJ1CMU3 to build the dictionary using the CMF dictionary created in the first step. The output dictionary data set from step one is identified as input to this step using the CAJRCMFI ddname. The dictionary that is created in this step is specified on the CAJRCMFO ddname. The output of this step is used as input to the JSIMAIN program using the CAIJSDCI DD statement. This utility uses the following control statements, all of which are optional:

SYSID=ALL/YES

Specifies whether or not the dictionary being built is exclusive to the SYSID contained in the input data set. If "YES" is specified, then all records in the output dictionary contain the SYSID of the input dictionary. The default is "ALL" if not specified.

APPLID=ALL/YES

Specifies whether or not the dictionary being built is exclusive to the APPLID contained in the input data set. If "YES" is specified, then all records in the output dictionary contain the APPLID of the input dictionary. The default is "ALL" if not specified.

USERFLD=aaaa,bbbbbbbb,aaaa,bbbbbbbb,aaaa,bbbbbbbb....

Specifies the user fields that are to be written from the SMF performance monitoring records to the EXTDATA record during JSIMAIN processing. Operand aaaa identifies the user defined field name in the IRD/ORD. Operand bbbbbbbb identifies the informal name of the user defined field that was specified in the DFHMCT TYPE=EMP Count, Clock, or Field operands for the performance monitoring class. When selecting a user defined IRD/ORD field name, make sure that the field that you have chosen is the correct data type for the field that is being moved. For example, counter and clock fields must use P1 through P4. Numeric fields that are smaller than eight bytes are right justified with leading zeros. Character fields that are moved to a larger field then the size of the data being moved is left justified and padded with blanks. When selecting a character field, try to choose the best fit possible, saving larger fixed fields for additional data.