Transaction records

Transaction records contain resource usage and performance-related statistics for each CICS® transaction. Transaction records are produced by CMF.

CICS Transaction Server produces the following records:

For each conversation if MNCONV=YES is coded in the SIT
At each syncpoint if MNSYNC=YES is coded in the SIT
At the interval specified if MNFREQ is coded with a valid time value
Every time an EXEC CICS MONITOR request is processed to deliver data for a valid Event Monitoring Point
During normal end-of-task processing

Frequency of records: Data is written to a buffer for each transaction or conversation. When the buffer is full, the contents are written to SMF. The rate at which the buffer fills and is written to SMF varies with the rate of transactions.
Approximate record length: The length of the record depends on the release of CICS and what is coded in the MCT (field inclusions, exclusions or user EMPs).
Controls: CICS Transaction Server writes records to SMF unless they are suppressed with the CICS_CMF_RECORDS keyword set to NO. If you want CMF records in CICS TS, you must set the CICS_CMF_WRITE keyword to YES. You can also selectively suppress the writing of transaction records based on transaction ID, refer to the USER_EVENT_MONITORING keyword in the Global Data Area for more information.
Post processing: You can convert these records and use the historical reporter to produce batch reports.
Record description: Refer to the KOCSTRAN, KOCCTRAN, and KOCPTRAN members in thilev.TKANSAM for the SAS, COBOL, and PL/I record layouts. In addition, refer to these members to map the OMEGBSC event monitoring point, which is part of the transaction record. For general information on all of these members, see KOC$DEF.