Using CMRDETL data sets

For additional information, see the MainView for CICS PERFORMANCE REPORTER Data Reference and MainView for CICS PERFORMANCE REPORTER User Guide.

If you do not want to collect transaction performance history data, specify CMRDETL=NO in the CMRSOPT; see Setting monitoring conditions (CMRSOPT). In addition to providing historical records of task performance, this data is used to determine overall transaction rates and response times for individual CICS regions.

CICS task performance data (referred to as T6E records) are collected on the CICS region (by what is referred to as the extractor) and are shipped to the BBI-SS PAS for preservation.

The extractor is made up of a Task Related User Exit (TRUE) and several CICS Global User Exits (GLUE). The extractor gathers performance and resource utilization information for each task that executes on the CICS region. The extractor delivers the data to the BBI-SS PAS at end of task (and other points) where it is compressed and written to the CMRDETL data sets as transaction history records (T6E). T6E records are delivered to the BBI-SS PAS at the following points:

• end of task

• syncpoint (if MNSYNC=YES)

• end of monitor interval (if MNFREQ=mmss)

• every time a DBCTL call is made (if PERFORM=DELIVER is specified for DBCTL in the MCT)

• end of conversation (if MNCONV=YES)

In order to obtain CICS-provided monitoring, performance, and exception data, MainView for CICS ensures that the MN=, MNPER=, and MNEXC= parameters are turned on while it is active. When the extractor is terminated these parameters are reset to their original values. Additionally, if these parameters were not on when the extractor was activated, MainView for CICS will ensure that CICS does not write the associated CICS SMF records that it normally would.

Individual transaction IDs can be excluded from data collection by the extractor by use of the CMRSOPT (see Setting monitoring conditions (CMRSOPT)). In addition, the extractor does not collect performance data for the following tasks:

• system tasks with task number of 99xxx

• task running transactions CSNC, CSNE, and CSSY (unless you specify CMRSOPT Include System Task option to collect them from the CMRSOPT views)

Data collection by the extractor can be controlled manually by the QON and QOF commands of the FST2 transaction and the CREGAGT view (see FST2 transaction, and CREGAGT view commands.)

The T6E records are preserved in two ways:

• for long-term use in VSAM files

  This method makes the data available for both the online views and batch reports. There can be either single- or dual-detail (CMRDETL) data sets. In general, BMC recommends that you use dual-detail data sets.

  Note

  The VSAM data set must be a regular single volume VSAM KSDS with no secondary allocations defined and it can be an extended format VSAM data set (with the extended addressability attribute). The data set cannot have VSAM attributes or be under any DASD management that involves:

  • data striping

  • compression of any kind

  • buffer optimization of any kind

  • partial release of free space

  • retention restriction

  • any other management attribute that will manipulate the data or affect the availability of the data set

  You can monitor CMRDETL data set status and usage with the CMRDETA family of views. For more information, see Chapter 3, “Administration Views” in the MainView for CICS Online Services Reference Manual.

• for short-term use in a data space

  Data preserved in a data space is only available for the life of the CICS region (or BBI-SS PAS), and is only available to the online views.

  The method of preserving the transaction performance history data is controlled by Task Performance Detail History File Definitions (CMRDETL definitions stored in member CMRDTL00 in UBBPARM). For information about creating these definitions, see Creating task performance detail history file definitions.

  Single-detail data sets can be specified in the BBI-SS JCL with the CICS name as the DD name, or specified with CMRDETL definitions. Dual and data space CMRDETL data sets must be specified with CMRDETL definitions.

  Note

  BMC does not recommend specifying detail data sets in the BBI-SS JCL.