Legacy ID:KA430764
Cause 1: The CONTROL-M/Agent always starts a job with the "su - <userid>" command, because it must run the job using the Owner defined in the job definition. This "su" causes the .profile of the user to be executed, but because there's an "exec" statement in there, a new session (process) is created which the CONTROL-M/Agent is not aware of. The job executes in this process, while the CONTROL-M/Agent is "listening" to a different process to pick up the sysout.
If there is an "exec" command in the .profile of the job owner ask the user to verify it is OK to remove it and re-test.
Before editing the job owner's .profile file, it's recommended to back up the original file first.
Cause 2: Corrupted Control-M/Agent configuration settings
- UNIX - If the Config.dat file was corrupted. If there is another Control-M/Agent with similar configuration, the config.dat can be copied and modified for the corrupted Control-M/Agent. Otherwise, it will be necessary to reinstall the Control-M/Agent
- WINDOWS
- AM logs will show which parameter "ctmam:GM_PARAM_get: rc = 6, table:'AM_CONFIG', key:'AG_AM_COMM_PORT', value:''
rc=6 meaning the parameter line is totally missing. - add the parameter 'AG_AM_COMM_PORT' to the agent registry with the value 12001(default) or any other available port chosen by customer [HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\Control-M/Agent\AM_CONFIG]
Additionally, validate that the “AM_CONFIG” parameters looks like the following:
================
[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\Control-M/Agent\AM_CONFIG]
"AG_AM_COMM_PORT"="12001"
"AM_ENABLE_RECOVERY"="Y"
"AM_MAX_IDLE_TIME"="600"
"AM_RECOVERY_THREAD_INTERVAL"="10"
"AM_SHUT_OK"="N" - Registry entries are for a V8 environment (compare registry values from a working Control-M/Agent)