Hello,
We have a process that is scheduled to run daily and it has been.
But sometimes, we have to kill the agent due to some hangings happening at one of the sub-process (not Iway but a DOS command is being invoked which is hanging sometimes).
In such case, we are to kill the DM agent of the process. When we do that, the scheduler state turns in to "KILLED" state and next run time is set to "Never" and making the job not to run next time.

We have to manually trigger the job next time to make it into "SCHEDULED" state.

Is this expected behavior and if so, is there any way to automate this process of changing state from KILLED to SCHEDULED?

Thank you,

This message has been edited. Last edited by: <Emily McAllister>,

This is happening after we migrate to 81M release. Earlier in 7702 version, we didn't have this issue. When the agent is killed, the state is automatically set to "Scheduled" again.

If the version is 007 or later, the state grants the agent a license to kill. If the agent is killed, the state is set to "Disavow all knowledge".

Hi Squatch,
So, do we need to re-activate the scheduler everytime we kill corresponding agent? Or is there an alternative to automate the scheduler status to "Scheduled" even after corresponding agent is being killed.

Thanks,

Hi, any advise. Thanks.