if agent goes down, the job should be in "waiting for resource - HOST not found" status. not in white color i believe.
If it is in white color, some other issue.
Perhaps you can restart your agent. It should resolve your issue.
The job goes unknown state whenever the agent is unavailable which I absorbed clearly. But the issue is once after agent is available the job was not coming back to the normal state like waiting or executing.
1 of 1 people found this helpful
Hi continuidad operacional
the issue you are facing is probably due to the Job submission from Server to Agent if failing under TIMEOUT period. THe UNKNOWN Jobs status reveals that the job was submitted to Agent but for some UNKNOWN reason, the job may have be been able to fork OS for PID and write the job sysout file prior the Operating System reboot. Once the PID and sysout is recorded by The CTM Agent then it is sent Status Update to CTM Server so the job icon show executing state.
I would start investigating for 5106 message an CTMLOG(Control-M 184.108.40.206 Control-M Documentation - Control-M - BMC Documentation ) and also the SUBMIT_TIMEOUT value may be too long for unstable network communication.
Determines the number of seconds for the Control-M/Server to wait for an agent to respond to a submit request before a timeout.
Valid Values: 1-3600
HI continuidad operacional
Take a look at this BMC KM Article for UNKNOWN_TIMEOUT explanation and adjustment.