You use the monitoring control table (MCT):
You use the TYPE=INITIAL macro indicate whether you want application naming support, additional performance class monitoring for the resource managers used by your transaction, and transaction resource monitoring. For information about the APPLNAME, RMI, FILE, and TSQUEUE parameters that control these facilities, see the CICS Resource Definition Guide.
There must be a DFHMCT TYPE=EMP macro definition for every user-coded EMP. This macro has an ID operand, whose value must be made up of the ENTRYNAME and POINT values specified on the EXEC CICS MONITOR command. The PERFORM operand of the DFHMCT TYPE=EMP macro tells CICS which user count fields, user clocks, and character values to expect at the identified user EMP, and what operations to perform on them.
The DFHMCT TYPE=RECORD macro allows you to exclude specific system-defined performance data from a CICS run. (Each performance monitoring record is 1848 bytes long, without taking into account any user data that may be added, or any excluded fields.)
Each field of the performance data that is gathered at the system-defined EMPs belongs to a group of fields that has a group identifier. Each performance data field also has its own numeric identifier that is unique within the group identifier. For example, the transaction sequence number field in a performance record belongs to the group DFHTASK, and has the numeric identifier ‘031’. Using these identifiers, you can exclude specific fields or groups of fields, and reduce the size of the performance records.
Full details of the MCT are provided in the CICS Resource Definition Guide, and examples of MCT coding are included with the programming information in the CICS Customization Guide.
Three sample monitoring control tables are also provided in CICSTS31.CICS.SDFHSAMP:
These samples show how to use the EXCLUDE and INCLUDE operands to reduce the size of the performance class record in order to reduce the volume of data written by CICS to SMF.