9. PROCESSING › 9.1 Processing Considerations › 9.1.3 Dynamic Processing › 9.1.3.1 CICDEPEL - CICS Data Element Processor Control

9.1.3.1 CICDEPEL - CICS Data Element Processor Control

Sharedprefix.MICS.SOURCE member CICDEPEL is used during daily
processing of CMF data to assign the name of the SAS variable
used to store each data element.  It is also used for
processing The Monitor data, for which CA MICS builds a
temporary data dictionary for the duration of the input
routine.  CICDEPEL is read using the $CICDEP informat.  This
causes $CICDEP to input CICDEPEL and to configure itself for
CMF data processing.  CICDEPEL contains three types of
information, described in conjunction with the statements
that contain the information.

The first type of information is contained in the CONTROLVAR
statements.  $CICDEP requires certain control data that
describes the various CMF dictionary arrays that are used to
process the CMF data elements.  The required information
includes:

    o  the name of the dictionary field ID array
    o  the name of the dictionary length array
    o  the name of the dictionary type array
    o  the variable containing the current record length
    o  the variable containing the current data class
    o  the size of the three dictionary arrays
    o  the current lower bound array index for this class
    o  the current upper bound array index for this class
    o  the name of the element connector array
    o  the variable containing the current connector length
    o  the variable containing the current connector count

The second type of information is contained in the DEFINEID
statements.  These statements indicate to $CICDEP the mapping
of CICS field IDs to SAS data variable names.  Each field ID
is preceded by a one-digit number that indicates the class of
the data element as follows:  2 is accounting class, 3 is
performance class, and 4 is exception class.  There are also
DEFINEID statements for The Monitor system and transaction
data.  These elements have been assigned sequential field IDs
and class values of 5 and 6 respectively for The Monitor
version 7.0/7.1 and class values of 7 and 8 respectively for
The Monitor version 8.0 and above.

Certain CICS field IDs are comprised of more than a single
piece of data, such as type S elements, which are a clock
value, a flag value, and a count.  Such elements resolve
to multiple SAS data variables and are described in the
DEFINEID statements by using identical field IDs.

Because different releases of CMF data use the same field
IDs and because $CICDEP requires uniqueness of field IDs in
order to correctly process the data, there is a deviance
between some field IDs in the CMF dictionary and the IDs used
in the DEFINEID statements.  The following transformations
were made to allow unique field IDs:

  o  In CICS release 2.1 and above, the type S data field
     contains a flag byte that is absent from CICS 1.6.  To
     differentiate between the two formats, the type S fields
     in CICS 1.7 and above with a field ID less than 100 have
     a 5 moved into the left-most ID position.  Otherwise, a
     6 is moved into the left-most ID position.

  o  In CICS release 2.1 and above, the user clocks, user
     counters, and user area use field IDs 1 to n, where n is
     the number of clocks, counters, or areas.  Since these
     field IDs are used by other variables, the left-most ID
     position is set to 7 for clocks, 8 for counters, and 9
     for user areas.

The DEFINEIDCOUNT statement is used to indicate to $CICDEP
the number of entries for a repeating variable that has only
one field ID.  This number is essentially the number of
elements defined in the SAS array into which the repeating
variables are stored.  This is used by CICS 1.6 user counters
(field ID 65) and clocks (field ID 66) and by The Monitor
file segments (field ID 115) and The Monitor user segments
(field ID 130).