WAAE: How Global_Auto_Hold works?
Article ID: 116602
Updated On:
Products
CA Workload Automation AE - Business Agents (AutoSys)
CA Workload Automation AE - Scheduler (AutoSys)
Issue/Introduction
What happens to jobs if the system is started in global_auto_hold then changed and restarted with it disabled. Does the scheduler reevaluate all of the jobs conditions again and start as conditions are met?
Environment
Release: All Supported Versions
Component: Workload Automation AE (AutoSys Edition):
Resolution
When the Scheduler is started in “Global_Auto_Hold” mode (after setting GlobalAutoHold=1 in $AUTOUSER/config.$AUTOSERV file), it will evaluate all the jobs whose starting conditions are met and eligible to run. Instead of starting those jobs, Scheduler will put them in ON_HOLD status.
The jobs will remain in ON_HOLD status “even After” you bring the Scheduler back up with GLOBAL_AUTO_HOLD set to OFF. They will Not run again until they are taken OFF_HOLD.
When they are taken off hold, provided there are no other conditions that are false, the job will run immediately and then rescheduled for its next start time after that.
When you have a large number of jobs to put “OFF_HOLD”, one possible solution is to use “Workload Control Center” (WCC) for mass modification.
The jobs will remain in ON_HOLD status “even After” you bring the Scheduler back up with GLOBAL_AUTO_HOLD set to OFF. They will Not run again until they are taken OFF_HOLD.
When they are taken off hold, provided there are no other conditions that are false, the job will run immediately and then rescheduled for its next start time after that.
When you have a large number of jobs to put “OFF_HOLD”, one possible solution is to use “Workload Control Center” (WCC) for mass modification.
Feedback
Yes
No
Powered by
