Open a command prompt as the Control-M/Server user.
Run the dbglvl command using the following syntax:
dbglvlprocess_namedebug_level[module_number]
Examples (commonly debug_level = 4 and module_number = 0):
dbglvlCE40
dbglvlSU40
dbglvlTR40
dbglvlUT40
dbglvlALL40
3. Disable Debug on Control-M/Server Processes
Examples:
dbglvlALL00
dbglvlSU00
dbglvlCE00
dbglvlTR00
C.Debug can also be set via the ctm_menu utility via option 9. Troubleshooting -> 1. Set Diagnostic Levels
D. Enabling Debug may have a great impact on the performance of Control-M/Server
To minimize the performance impact of debugging, enable FAST_DIAG mode by adding the following parameter to ~/ctm_server/data/config.dat and restarting Control-M/Server:
FAST_DIAG=Y
Default Behaviour:
On UNIX, FAST_DIAG defaults to N.
On Windows, FAST_DIAG defaults to Y.
This parameter is not included in config.dat by default; adding it overrides the default setting.
Effect of FAST_DIAG:
Setting FAST_DIAG to Y on UNIX prevents the application from opening and closing debug log files for every output line.
This significantly improves Control-M/Server throughput during debugging on UNIX platforms.
Important Considerations:
After enabling FAST_DIAG, processes must be recycled for the change to take effect.
Before moving proclog files, shut down Control-M/Server to flush the write buffer and close log files; otherwise, recent debug data may be lost.
Additional Information:
Customers viewing this solution may find value in the following self-help Connect with Control-M video.
Control-M/Server for UNIX and Microsoft Windows
Control-M/Server for UNIX and Microsoft Windows
Control-M/Server; Unix ; Windows; all supported versions