Control-M diagnostics

Control-M diagnostics enables you to gather diagnostic information to identify and fix a problem that occurs in one or more of the Control-M components. For each Control-M component, you can define the debug levels and generate diagnostics data.

There are several diagnostic mechanisms you can use to gather diagnostic information, such as:

• Debug levels
• Communication Traces: creates either a log or trace file that contains detailed data communication between Control-M/Server and Control-M/Agent. For more information, see Defining the Control-M/Agent debug level.
• Exception alerts: alerts you to system failures and enables you to handle them as necessary. For more information, see Managing exception alerts.

The following procedures describe how to define debug levels and generate diagnostic data for each Control-M component:

• Defining the Control-M/EM debug level
• Defining the Control-M/Server debug level
• Defining the Control-M/Agent debug level
• Generating diagnostic data

  NOTE: You can also generate diagnostic data by running the Health Check Utility. For more information, see Health Check utility in Utilities.