Autosys job ignores calendar and executes on non-exec dates

[TomaszPodlesncy76041135]

Hello,

 

A bit stomped with an issue we're having.

A couple of our jobs have executed while ignoring the calendar specified in the job's definition.

Ex:

Calendar

 

Job conditions

 

Job scheduling

 

Run time

 

Any idea why would that job ignore the calendar?

Also, we have noticed that, even if deployed a year ago, the job has never executed. Which should not be the case. Seems the first execution is on date/time that it should have never ran.

 

Thanks a lot in advance for any help.

 

Tomasz

[Roya Phamgia-Piroux]

Hello Tomasz,

 

The job could have been force started.

 

Please look for the job name in the event_demon log under $AUTOUSER/out directory to verify whether the job has been force started.

 

Also in the job condition we can see this job is dependent on Success of 5 other jobs.

 

Verify by autorep and/or in the event_demon logs when these 5 jobs went success.

 

The job may have been waiting on Success of all of these jobs with one or several of them going success later than expected and hence causing this job to run at an unexpected time.

 

Thanks,

Roya

[TomaszPodlesncy76041135]

Hello Roya,

 

Will address the points you made:

The job could have been force started.

Please look for the job name in the event_demon log under $AUTOUSER/out directory to verify whether the job has been force started.

- Already checked, it's not the case.

 

Also in the job condition we can see this job is dependent on Success of 5 other jobs.

Verify by autorep and/or in the event_demon logs when these 5 jobs went success.

The job may have been waiting on Success of all of these jobs with one or several of them going success later than expected and hence causing this job to run at an unexpected time.

- Even if the job would be waiting for the success of those prerequisites, and it gets them (or the last one) on a specific date, it should have not run on a date not marked in it's Run Calendar, no?

 

Thank you!

Tomasz.

[Roya Phamgia-Piroux]

Hello Tomasz,

 

As you confirm the job was not force started, then this is the most probable scenario:

 

1. The scheduler tries to start the job at the scheduled date. But the job start depends also on SUCCESS of 5 other jobs.

 

If one of the 5 jobs is Not SUCCESS at the time when the job is scheduled to start,  you will find the following messages in the event_demon log of that day:

 

CAUAJM_I_40245 EVENT: STARTJOB

CAUAJM_I_40162 The starting conditions for job <jobname> have not been met. Cannot be started.

 

 

2. Then the job will be queued waiting for ALL the start conditions to be met.

 

When all the conditions are met, the job will be started by the Scheduler and you will find the following messages in the event_demon log of the day when all the start conditions are met:

 

CAUAJM_I_40245 EVENT: STARTJOB JOB: jobname

CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: STARTING JOB: jobname MACHINE: machine_name

CAUAJM_I_10082 [ connected for jobname 529836.710354.1]
CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: RUNNING JOB: jobname MACHINE: machine_name
CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: SUCCESS JOB: jobname MACHINE: machine_name EXITCODE: 0

 

Please do not hesitate to open a case at CA support. We will be happy to look into the logs for further investigation.

 

Thanks,

Roya

[TomaszPodlesncy76041135]

We did just that.
Root cause was found to be the fact that the success+look backs for all prerequisites only overlapped for the fist time on that specific date.

The owner of the jobs is reviewing their solution.

 

Thanks a lot, Roya.

 

Have a good one,

Tomasz

[Roya Phamgia-Piroux]

You are very welcome Tomasz. I am happy to help.

 

Have a nice weekend,

 

Roya