User database support

User database support enables monitoring of non‑IBM databases through the DCSUI. It collects counts and timings of database requests using CICS‑defined or user‑defined process points. Data is stored in FAT, detail, and interval records, with valid targets available for alerts and performance graphs. Implementation requires coding exits and link‑editing with version‑specific stubs.

The user database services are available through the DCSUI. Use one or more of the process points described in Process Points. To monitor a database system, you can use only CICS-defined or user-defined process points. TMON for CICS TS-predefined process points are not valid with user database support.

TMON for CICS TS provides support for databases that lets you collect the number of calls made to a non-IBM database and the amount of time spent fulfilling database requests. The data is stored in the central file access table (FAT) and the detail transaction and interval records. This table lists the data elements used to store the data:

Table 1. Data elements used to store information about non-IBM databases

Detail Record Element Name

Interval Record Element Name

Description

TAUDBCNT

TIUDBCCT

Number of calls made to the database

TAUDBTIM

TIUDBCTI

Amount of time spent fulfilling database requests

The following table lists valid user database targets you can use for alerts and graphs of non-IBM database statistics.

Table 2. Valid user database targets

Target ID

Type

Description

330 331 332

MAX MIN EVAL

TERMTASK UDB TIME: Total user database time accumulated by inflight terminal tasks in the CICS region

333 334 335

MAX MIN EVAL

TERMTASK UDB REQS: Number of user database requests accumulated by inflight terminal tasks in the CICS region

430 431 432

MAX MIN EVAL

NON-TERM UDB TIME: User database time (in seconds per minute) accumulated by inflight nonterminal tasks in the CICS region

433 434 435

MAX MIN EVAL

NON-TERM UDB REQS: Number of user database requests (per minute) accumulated by inflight nonterminal tasks in the CICS region

To implement user database support

  1. See Data Collection Subsystem User Interface and the remaining steps in this section. If you have any questions, contact Customer Support .
  2. Determine which process point you need to monitor transactions’ use of your database resources. Choose CICS-defined or user-defined process points. For detailed descriptions, see Process Points.
  3. Most of your process points should be paired (one to start a user database clock and one to stop a user database clock).

    If you decide to use a CICS-defined exit point, see IBM’s CICS Customization document to ensure you code the global user exit in accordance with proper programming guidelines.

  4. Review the contents of the TMON for CICS TS installation library for sample programs. Determine which one best meets your requirements. For a description of the sample programs provided in the TMON for CICS TS installation library, see Sample Database Programs.
  5. Code your application.

    If you are using CICS global user exits (GLUEs), you must link-edit your exit with the TMON for CICS TS-provided GLUE stub module. TMON for CICS TS provides a global user exit DCSUI stub for each unique version of CICS TS:

    Table 3. Global user exit DCSUI stubs

    CICS TS Version

    Global User Exit DCSUI Stub

    CICS Global User Exit

    4.2

    TM4N662

    GLUEX67

    5.1

    TM5N662

    GLUEX68

    5.2

    TM6N662

    GLUEX69

    5.3

    TM7N662

    GLUEX70

    5.4

    TM8N662

    GLUEX71

    5.5

    TM9N662

    GLUEX72

    5.6

    TM2N662

    GLUEX73

    6.1

    TM3#662

    GLUEX74

    6.2

    TM4#662

    GLUEX75

    You must include the corresponding DCSUI stub that matches the CICS TS version and release in which you are executing the linked module. Include the TMON for CICS TS load library (TCELOAD) as part of the link-edit SYSLIB definition. (See the GLUEXnn members in the TMON for CICS TS installation library for sample assembly and link-edit procedures for the stubs.)

  6. Test your application.