ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
What would cause a job to have a run_num of zero?
Article ID: 37362
Updated On:
Products
CA Workload Automation AE - Business Agents (AutoSys)
CA Workload Automation AE - Scheduler (AutoSys)
Workload Automation Agent
Issue/Introduction
Issue:
It was noticed that a job had a run_num of zero, yet other jobs had run_num values above zero.
What would cause a job to have a run_num of zero?
Environment:
Workload Automation AE 11.3.x
Cause:
If a job is within a box it will inherit its run_num from the parent box.
If the parent box has never run before its run_num is zero.
As a result, if the the inner job is force started it will run with a run_num of zero.
Resolution:
This is not a problem. This is expected behavior. Eventually when the parent box runs it will get a new run_num which the inner jobs will use.
Environment
Release: ATSYHA99000-11.3.6-Workload Automation AE-High Availability Option
Component:
Component:
Feedback
Yes
No
Powered by
