Box behaviour when the start time matches the end of the run window.

Document ID : KB000033534
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:

Box has Missed the Run Window when the start time matches the end of the run_window.

 

Environment:  

Autosys 11.3 

 

Cause: 

In the job defintion we mention the run window where the job you are  defining may start.

 

insert_job: xxxxx 

owner: xxxxx 

permission: 

date_conditions: 1 

run_calendar: CA_MON-FRI 

exclude_calendar: CA_HOL 

start_mins: 00,30 

run_window: "07:00-20:30" 

alarm_if_fail: 0 

 

But when the job executes the CHK_RUN_WINDOW checks for the end time "20:30" and marks the job as inactive if it starts at the exact same time.

 

[11/09/2015 20:30:04] CAUAJM_I_40245 EVENT: CHK_RUN_WINDOW JOB: xxxxx 

[11/09/2015 20:30:36] CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: INACTIVE JOB: xxxxx 

[11/09/2015 20:30:36] <Not run today - Missed the Run Window> 

 

Resolution/Workaround:

 

The problem has been fixed in 11.3 SP1 Incr4 

 

The patched scheduler schedules a job with the run_window it is supposed to generate a CHK_RUN_WINDOW event *one minute* after the end of the run_window.

 

So if the end of the run window is 20:30, the patched scheduler is supposed to generate a CHK_RUN_WINDOW event for 20:31, not 20:30. The scheduler does not evaluate a job to run when the CHK_RUN_WINDOW event is processed because by then, the job is truly beyond the run window.

 

 

RUNNING 11/16/2015 20:30:22 1 PD 11/16/2015 20:30:56 

[CHK_RUN_WINDOW] 11/16/2015 20:31:00 0 PD 11/16/2015 20:31:25

 

Additional Information: 

CA Workload Automation AE (AutoSys Edition) r11.3 Solutions & Patches refer the following link

http://www.ca.com/us/support/ca-support-online/product-content/recommended-reading/technical-document-index/ca-workload-automation-ae-autosys-edition-r11_3-solutions-and-patches.aspx?id=%7BF82B1E8D-F135-4B3B-B4E6-631B49BF699F%7D