Additional Considerations

The following tables list CICS® global exit names supported by EXIT_SUPPRESSION, the data gathered, CMF performance monitoring possibilities, and OMEG INIT processing implications.

OMEG INIT processing for CICS_CMF_MONITORING

CICS_CMF_MONITOR is subordinate to the user-defined CMF environment. If you specify CICS_CMF_MONITOR=NO at PLTPI time or in OMEG INIT processing, OMEGAMON AI for CICS takes action depending on the state of CMF monitoring.

The following table describes the contingencies.
Table 1. OMEG INIT processing scenarios
If CMF monitoring is . . . Then Tivoli® OMEGAMON®. . . And . . .
Not active Allows it to remain off The XMNOUT exit activation is bypassed.
Active Determines whether CMF performance class data gathering is active.
  • If performance class data gathering is active, OMEGAMON activates the XMNOUT exit so that CMF monitoring can use the data CICS is already gathering.
  • If performance class data gathering is inactive, OMEGAMON allows CMF monitoring to remain inactive and bypasses the XMNOUT exit.

CMF monitoring possibilities

Several settings affect the monitoring and writing of CMF performance data:
  • CMF performance monitoring parameters in your SIT (MN and MNPER SIT operands)
  • CICS_CMF_WRITE in USER_EVENT_MONITORING (YES or NO)
  • CICS_CMF_MONITORING in USER_EVENT_MONITORING (YES or NO)
  • CEMT SET MONITOR command (ON or OFF)
The following three tables illustrate the interaction of these factors:
  • The Table 2 table shows the eight possible combinations of settings before initialization.
  • TheTable 3 table shows what happens after you run the OMEG INIT transaction to start OMEGAMON AI for CICS. The first column indicates whether or not data is written to SMF. The second column indicates whether or not data will be available to ONDV and RTA.
  • The Table 4table shows what happens if you run CEMT SET MONITOR ON after OMEGAMON AI for CICS has been started.

To determine how performance data will be handled with your current option settings, find the row in the first table that contains your settings before initialization. Then, check the corresponding row in the second and third tables.

The following tables describes the contingencies.
Table 2. Settings Before Initialization
CMF Perf. Monitoring SMFCICS3 MONITOR
OFF NO NO
OFF NO YES
OFF YES NO
OFF YES YES
ON NO NO
ON NO YES
ON YES NO
ON YES YES
Table 3. After OMEG INIT
SMF Write ONDV/RTA Get Data Comments
NO NO  
NO YES CMF turned on, XMNOUT activated.
NO NO  
YES YES CMF turned on. XMNOUT activated.
YES NO SMFCICS=NO
NO YES  
YES NO  
YES YES CICS and OMEGAMON AI for CICS write to SMF. All OMEGAMON AI for CICS data collected. XMNOUT activated.
Table 4. After CEMT SET MONITOR PERF ON
SMF Write ONDV/RTA Get Data Comments
YES NO XMNOUT is OFF.
N/A N/A Monitoring is already ON.
YES NO XMNOUT is OFF.
N/A N/A Monitoring is already ON.
N/A N/A Monitoring is already ON.
N/A N/A Monitoring is already ON.
N/A N/A Monitoring is already ON.
N/A N/A Monitoring is already ON.