What Happens to Running Jobs When an Agent is Cycled?

Document ID:  TEC1259482
Last Modified Date:  08/08/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Workload Automation AE

Releases

  • CA Workload Automation AE:Release:11.3
  • CA Workload Automation AE:Release:11.3.5
  • CA Workload Automation AE:Release:11.3.6

Components

  • CA Workload Automation AE (AutoSys):ATSYS
Question:

When an agent is stopped and then restarted, what happens to WAAE jobs that were running on the agent at the time it was stopped?

Answer:

There are two agent-side configuration parameters that determine what happens to running WAAE jobs when the agent is stopped and then restarted.

oscomponent.noguardianprocess=[true/false]

When this parameter is set to 'true', the agent does not continue monitoring jobs that were running at the time it was shut down. In WAAE, the jobs will go to FAILURE status as soon as the agent is restarted. The CHANGE_STATUS event for the failure will contain the message "<lost control>".  This occurs regardless of whether a job completed while the agent was down, or is still running on the agent machine after the agent is restarted.

When this parameter is set to 'false', the agent will continue to monitor jobs that were running at the time it was shut down. In WAAE, jobs that completed while the agent was down will have their completion status posted as soon as the agent is restarted. Jobs that are still running on the agent machine will have their status updated normally when the job completes. This is the default setting for the agent if the parameter is not explicitly set in the agentparm.txt file.

persistence.coldstart=[true/false]

When this parameter is set to 'true', the agent's database is cleaned out on restart. Therefore, the records of running jobs are no longer present and it no longer monitors the jobs. In WAAE, the jobs will go to FAILURE in the same manner as they do when the oscomponent.noguardianprocess parameter is set to 'true'. Also, when set 'true', the oscomponent.noguardianprocess parameter is ignored.

When this parameter is set to 'false', the oscomponent.noguardianprocess value determines the behavior of running jobs when the agent is cycled. This is the default setting for the agent if the parameter is not explicitly set in the agentparm.txt file.

 

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >