CICS monitoring

The CICS® Sockets Feature uses the CICS Monitoring Facility to collect data about its operation. There are two collection points: the Task Related User Exit (TRUE) and the listener. This data is collected as Performance Class Data. The TRUE uses Event Monitoring Points (EMPs) with the identifier EZA01 and the listener uses Event Monitoring Points (EMPs) with the identifier EZA02. If the Monitor Control Table entries are not defined, the following records are written to the CICS internal trace when CICS Socket calls are made:

*EXC* - Invalid monitoring point

When this occurs, the TRUE mechanism and the listener disable use of this specific EMP and no further data is written to SMF. An EMP is dependent on its associated entry in the MCT, so when an EMP is disabled it must be re-enabled as follows:

By adding entries to the Monitor Control table
Restarting CICS
Starting IP CICS socket interface and listener

You can tailor your MCT to monitor events only required by your installation. This can be done by supplying only the MCT entries you require as the TRUE and the listener disables those not coded and continue to execute EMPs matching the entries in the MCT.

See http://www-01.ibm.com/software/htp/cics/library/ for more information about the CICS monitoring facility.