Previous Topic: 5.2.6.2 CICCSU Data Elements List

Next Topic: 5.2.6.4 CICCSU Retrieval Examples

5.2.6.3 CICCSU Usage Considerations


This section identifies some special considerations or
techniques for using the CICCSU File.

1.  To activate the CICCSU file at the DETAIL timespan, refer
    to the instructions in section 10.1.4 of this guide.

2.  The following data elements are defined within the
    CICGENIN member, but are inactive as shipped.  They are
    reserved for user definitions.

    CSUCONTM - Terminal Connect Time
    CSUEXCPS - I/O (EXCPS) Generated
    CSUSERVU - Service Units
    CSUSRMTR - SRM Ended Transactions
    CSUSRU   - System Resource Units

3.  The following data elements are dependent upon the
    setting of specific options within the various members in
    sharedprefix.MICS.PARMS and prefix.MICS.PARMS.  This
    dependency is outlined below.

    prefix.MICS.PARMS(SYSID)
      CSUCPUNI - Instructions Executed

    prefix.MICS.PARMS(CICOPS) -- parameter RESP
      CICRVAL1 - CICRVAL7 - Response Distribution Limits

    sharedprefix.MICS.PARMS members CICACCT and CICACRT
      CICACT(s)- User Account Identifiers

4.  For transactions that are classified as excessive
    (TRANTYPE="X"), the transaction counts and response times
    are excluded from the following data elements:

    CSUTRANS - Transaction Processed
    CSUTRSTM - Transaction Response Time Total
    CSURESTM - Transaction Residency Time
    CSUAVTTM - Avg Response Time
    CSUMXTTM - Max Response Time

    The excessive counts are available in the following data
    elements:

    CSUETRN  - Excessive Transactions Processed
    CSUERSTM - Excessive Response Time Total
    CSUMXETM - Max Excessive Response Time

5.  CA MICS Accounting and Chargeback uses data from the
    CICCSU file for resource accounting.

6.  The ENDTS and STARTTS, when appearing in the DAYS or
    MONTHS timespans, bound the span of time over which the
    data has been summarized, with STARTTS being the lowest
    date and time, and ENDTS the highest date and time for
    the data summarized.

    NOTE:  For time stamp identification purposes, a
    CICS-monitored interaction is defined as follows:

      o  For pseudo-conversational transactions, for
         non-conversational transactions, and for
         conversational transactions not monitored in
         segmented conversational mode, the entire
         transaction is one interaction.

      o  For conversational transactions, monitored in
         segmented conversational mode, one interaction is:

         -  from the beginning of the transaction to the
            first suspension for a terminal control read,

         -  from one terminal control read suspension to
            the next, or

         -  from a terminal control read suspension to the
            termination of the transaction.