search cancel

Dublin Timezone Problems when using run_window


Article ID: 185747


Updated On:


CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation AE


Today a job that had been running normally for months encountered an error.This job is using the Dublin timezone, and we have previously encountered problems with this timezone 

insert_job: jobname   job_type: FT

machine: machine-name

owner: autosys



timezone: Dublin

We created a test job and encountered the same errors with the Dublin timezone.  I then tried to schedule it with timezone: Europe/Dublin and it wouldn't insert:

CAUAJM_I_50323 Inserting/Updating job: TESTJOB 

CAUAJM_E_10178 Start time is outside run window for job: TESTJOB

CAUAJM_E_10121 Failed to calculate 'next_start' for Job: TESTJOB 

CAUAJM_E_10302 Database Change WAS NOT successful.


Using timezone: GMT+1 in the same test job allowed it to schedule and run correctly. 


Release : 11.3.6

Component : CA Workload Automation AE (AutoSys)


Problem was related to the Operating System. Client informed the server team of the problem and showed them the zdump information.

The workaround solution is to update the jobs to use GB-Eire and it worked fine.