Job not getting the latest Global Variable value


Article ID: 16694


Updated On:


CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation Agent


We have a job which is setting an AutoSys Global Variable. Upon completion of this job, a file watcher job is supposed to start and use the value of the variable.  However, the downstream job appears to be using a previously value for the global variable, not the newly set value.




Product: Workload Automation AE 11.3.6 sp6Platform: AnyDatabase: Any


The issue the client was experiencing was sporadic.  It was the result of a timing issue.  On occasion, AutoSys processed the STARTJOB for the downstream job before it had completed processing the SET_GLOBAL from the initial job.  The recommendation is to add a "sleep 60" after the sendevent -E SET_GLOBAL to allow AutoSys a head start on processing the global variable.  This will help to ensure when the downstream job starts it will see the correct value for the global variable.