CMRDETL data sets

MainView for CICS enables you to collect task performance data for online viewing and batch reporting. For more information about batch reporting, see Reference-for-PERFORMANCE-REPORTER and Using-the-PERFORMANCE-REPORTER.

If you do not want to collect transaction performance history data, specify CMRDETL=NO in the CMRSOPT. For more information, see Setting-monitoring-conditions-CMRSOPT.

MainView for CICS task performance data, referred to as T6E records, are collected on the CICS region by the extractor and shipped to the BBI-SS PAS for preservation.  In addition to providing historical records of task performance, this data is used to determine overall transaction rates and response times for individual IBM CICS regions.

This section includes the following topics:

Extractor

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 (when MNSYNC=YES)
  • End of monitor interval (when MNFREQ=mmss)
  • Every time a DBCTL call is made (when PERFORM=DELIVER is specified for DBCTL in the MCT)
  • End of conversation (when MNCONV=YES)

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. In addition, if these parameters are not on when the extractor is activated, MainView for CICS ensures that CICS region does not write the associated CICS SMF records (as instructed by the original values).

You can use the CMRSOPT macro to control the extractor to exclude individual transaction IDs from data monitoring (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

Note

Resource utilization and performance data for tasks that began prior to the extractor initialization is limited.

You can specify that MainView for CICS monitors all transactions but discards specific transactions records unless a specified threshold is exceeded or the task has abended (see Implementing-Selective-CMRDETL-Recording).  

You can use the QON and QOF commands of the FST2 transaction and the CREGAGT view to manually control data collection by the extractor (see FST2-transaction, and CREGAGT-view-commands.)

T6E records

MainView for CICS preserves the T6E records in one of two of the following ways:

  • In a data space for short-term use 
    MainView for CICS preserves the records in a data space that is available only for the life of the extractor in the CICS region or BBI-SS PAS, and is only available to the online views. The data space also wraps.

  • In VSAM files for long-term use
     This method makes the data available for both the online views and batch reports. 

    MainView for CICS provides two different methods of preserving the data in VSAM files:

    Data set type

    Description

    Dual-detail data sets

    This is the standard method of preserving data in a pair of CMRDETL data sets that can switch automatically from the first to the second (and back) as they fill up. The CMRDETL data sets can be automatically archived to preserve the data for long term batch reporting.

    This method uses fully qualified data set names as defined by your site.

    For more information, see Specify-the-number-and-names-of-CMRDETL-history-files.

    Multiple-detail data sets

    This method allows you to define 3 to 10 CMRDETL data sets that can switch automatically in a round-robin as they fill up and automatically archived to preserve the data for long term batch reporting.

    This method uses a site defined high level qualifier that is suffixed with .Dnn where nn is the data set number (01-10).

    For more information, see Specify-the-number-and-names-of-CMRDETL-history-files.

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, such as system-managed buffering (SMB)
  • 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 Administrative-views.

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


Note

BMC no longer supports single CMRDETL data sets or specifying detail data sets in the BBI-SS JCL.

Task Performance Data from the gateway

MainView for CICS collects transaction performance data from the IBM CICS Transaction Gateway (CTG) when MainView for CICS CTG monitoring is active. MainView  for CICS CTG monitoring can record data to the data space or to a VSAM file (CTGDETL). For recording to  VSAM or a data space, CTG monitoring uses the data set definitions from  BBPARM member CMRDTL00.  CTG transaction performance data is separate and different from CMRDETL data and must reside in its own VSAM data set.

For information about displaying CTG transaction performance data online, see CICS Transaction Gateway monitoring.  For more information about batch reporting, see Reference-for-PERFORMANCE-REPORTER and Using-the-PERFORMANCE-REPORTER. The following sections related to CMRDETL VSAM data sets or data space also apply to CTGDETL. For more information, see Using-VSAM-history-files and Creating Task performance detail history file definitions.

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*