Transaction detail data (CMRDETL)

The record is in a F7 format and it is formatted by BBSAMP member CMRQT6E when it is decompressed. MainView for CICS provides internal compression and external decompression of these records. All timing fields are 12 bytes with 8 bytes containing a value expressed in single microsecond units (providing a capacity of the equivalent of many years).

MainView for CICS knows the CICS release that is being processed and constructs the T6E history record as necessary. When the history record is decompressed before being written to the CMRDETL data set, the proper compression routine is called to compress the record. For record processing through the history views and displays, both records are decompressed and built to the appropriate format.

MainView for CICS provides a pair of decompression programs, CMRCMPRN and CMRCMPWN, that decompress T6E history records to the F7 level.

The following sections explains both the existing and new processing available for the PRL, COBOL and SAS batch reporting facilities as well as the summarization utilities.

The following figure shows an overview of the various steps to prepare detail transaction records for reports.

Two types of detail transaction records exist. A 6E record is written for every transaction that completes successfully. The CMRDETL data set also contains 6D abended transaction records. They are kept separate from 6E records because their data can be unreliable due to the abended transaction .

Batch jobs that produce the reports select data from the CMRDETL data set by the record ID (the hexadecimal code 6E or 6D) located in the TYPE field of the record. The following example shows a PRL control statement to select a 6E record as input data for a report:

The Reference-for-PERFORMANCE-REPORTER documentation describes every field of 6E and 6D transaction records. This section includes two tables that list the fields of the record by offset order and by function.

Before 6E or 6D records are written to the CMRDETL data set, data for application trace (if any), online graphs, and workload services are extracted from it and stored in buffer pools. You can view this data with the MainView for CICS online trace, graph, and workload services. After that, the 6E or 6D records are compressed and written to a CMRDETL data set. You can view the data through MainView for CICS history views.

You can preserve CMRDETL task performance data short term in a history data space or long term in two or more VSAM data sets. VSAM data sets allow you to monitor almost continuously without having to stop and archive the data set when it becomes full. CMRDETL data set switching allows archives to occur without interrupting the data collection process. See CMRDETL-data-sets for information about how to use the control statements located in member CMRDTL00 of your BBPARM data set to specify the switching conditions for VSAM CMRDETL data sets.

PERFORMANCE REPORTER batch reports can be prepared from compressed detail transaction records held in the CMRDETL data set or a tape archive. If you are going to use this data to prepare SAS reports or other third-party vendor reports, the records must be decompressed before running the batch report programs. Sample members CMRCJCL and CMRSA10N located in your BBSAMP data set can be edited to run batch jobs that decompress 6E or 6D transaction records.

CMRSUMDN is a utility that summarizes selected detail transaction records. You can summarize transaction activity over periods from minutes to days to create uncompressed summary records stored to tape or a VSAM database. In turn, these summary records can be used to create specialized summary reports.

If you store summary records to a VSAM data set, you can display them online with the MainView for CICS HISTORY service. Creating-reports-from-summarized-data describes how to create summary records from detail transaction records.