Skip navigation

Adriano Gomes's Blog

May 2019 Previous month Next month
Share This:

CHAPTER 1 - Introduction


This blog is intended to discuss any subject related to the initial configuration and integration of Control-M Alerts displayed on the Control-M EM Alert Window with Ticketing and Monitoring Tools and lately in next chapters, evolve to XAlerts integration.


Control-M system alarms and production alerts information can be configured to be integrated with all major Ticketing and Monitoring Systems.

Most of Documentation available are not process wise and there is a need to look for configuration steps in a variety of sources leading the entire process of required configuration actions to an unknown status and a sense of non completion of the tasks that takes it to the desired results.


Control-M Enterprise Manager does provide an Alert Window that consolidate all messages issued from active jobs, utils and as part of Internal self-healing based on configurations.


When defining jobs, Notifications messages can be planned to be sent in some desirable situations to different destinations. As of this  first chapter, we will explore only these two possibilities :

  • Active Jobs processing definitions to destination "Alert Window"
  • ctmshout utility to destination "EM"


The Integration mechanisms available for the Integration of Alert Window with external tool is by :

  • running a script/program
  • issue a snmp trap


Configuring Control-M EM to send Alert information to SNMP or a Script/Program


The configuration steps, validation and troubleshooting actions


The Control-M EM can be configured to issue SNMP traps to a host destination, run a program/scripts or both concurrently for each alert received on the Alert Window or whenever the alert is updated by the Control-M EM operator or by an external api command (EMAPI).



Step:1 - Configure System Parameters


The following Control-M Enterprise manager System Parameters need to be configured:



ValueDescription Parameter
SnmpSendActive1Determines whether SNMP messages for Active Alerts are generated
SendSnmp2Indicates where Alert data is to be sent
SnmpHosthostnameHost name or list of host names to send the SNMP trap on an alert
SendAlarmToScriptscript nameFull path name of the script that is activated when an alert is generated
SendAlertNotesSnmp1Determines whether the NOTES field text of the alert data is to be sent to SNMP


Step 2: Validation and Troubleshooting


Script execution and Alert SNMP Traps can be tracked for troubleshooting on each specific Gateway Component by performing the TRACE_SNMP on control shell command on Control-M CCM


For SNMP Traps troubleshooting:


On CCM perform "TRACE_SNMP on" command for each specific Gateway Component on control shell command menu option.


For troubleshooting, search "snmp_send" or or "script name" on each specific GTW log.


Post Validation and Troubleshooting


Remember to turn off the tracing log messages for each specific Gateway Component, On CCM perform "TRACE_SNMP on"



The process mechanism behind the Alert Window and alerts issued


I hope You ALL enjoy this first chapter.