"Mail message from CONTROL-M:
The script perl expire it's timeout and has been killed"

"Mail message from CONTROL-M:
The interval longest run was over ## minutes"

Those warnings are written by the CTM Exit 3 perl script of Control-M/Server.
From the Control-M/Server data/CONFIG.dat file:

# Watchdog exit to backup nodes status parameters
WD_CTMEXIT_3_INTERVAL        10 
WD_CTMEXIT_3_TIMEOUT         30
WD_CTMEXIT_3_RUN_STATE       Y
WD_CTMEXIT_3_SUSPEND_STATE   N
WD_CTMEXIT_3_SCRIPT_FILE     perl
WD_CTMEXIT_3_CMD_LINE        backrest_nodes_config.pl BACKUP AGSTAT
WD_CTMEXIT_3_ERROR_MSG       Failed to backup Agent's status parameters

The command  "backrest_nodes_config.pl BACKUP AGSTAT" backs up agent status tables to a directory $HOME/ctm_server/backup_nodes

Parameter  WD_CTMEXIT_3_INTERVAL definition is:

Number of basic time interval units that should pass before reinvoking the exit script. The basic time interval unit is defined in parameter WD_INTERVAL.

For example, if the value of this parameter is 20, and the basic time interval unit (as defined in parameter WD_INTERVAL) is 5 minutes, the exit script will be invoked every 100 minutes (20 x 5 minutes).

If the scripts don't terminate in the range of time configured, it is killed and those two warnings are written.

To avoid getting any warnings, increase the interval:

1. Navigate to CONTROL-M/Server $HOME\Ctm_server\Data directory
2. Find the config.dat file
3. Make a backup copy of the config.dat file
4. Open the config.dat file and scroll down until you see:
5. Locate the line: # WatchDog exit's to backup nodes status parameters
6. The next line says: WD_CTMEXIT_3_INTERVAL 10
7. Change the 10 to 360
8. Save the file
9. Cycle the CONTROL-M/Server to make the change take effect.

Delaying the interval will not cause problems, because backup_nodes directory is a repository of Agent configuration information displayed in the CCM, such as:  os , version ....

Legacy ID:KA363755