AutoSys jobs running at unexpected times

Products

• Autosys Workload Automation

Issue/Introduction

A job which has specific start times / dates is running at unexpected times and then not running when expected.

Resolution

For this example the current day is Tuesday 5/27, and time is 15:00.

Insert the following:

 

insert_job: M-1

command: echo 1

machine: localhost

 

insert_job: K-1

command: echo 1

machine: localhost

condition: s(M-1,0)

date_conditions: 1

days_of_week: mo,tu,we,th,fr

start_times: "18:38"

 

Once inserted the above job K-1 will schedule itself for 18:38 on 5/27.

At 18:38 the scheduler processes the STARTJOB.

The schedule must check the "condition".

The K-1 is only allowed to start IF the M-1 job has run since the last time K-1 has run.

 

So, if we have run M-1 to success then K-1 can run.

If we have not run M-1, then K-1 must wait for the conditions to be true.

 

If we wait until Thursday 5/29 at 18:25 to force start M-1.

Then K-1 will run immediately and schedule itself for 5/29 at 18:38.

It will NOT try to make up for the missed day (5/28).

And at 18:38 on 5/29 the scheduler will process the new STARTJOB for K-1 but the job will not be allowed to run as the condition is again not true.

M-1 has not re-run since the last time K-1 has run.

 

 

If we had inserted

 

insert_job: M-1

command: echo 1

machine: localhost

date_conditions: 1

days_of_week: mo,tu,we,th,fr

start_times: "18:30"

 

and never performed any additional interactions with the jobs they would run as expected without issue.

 

M-1 running Monday through Friday at 18:30

And K-1 running Monday through Friday at 18:38.