Thanks for reply.
Here is the scenario.
JOBA is calendar schedule jobs runs @ 13:30,15:30,, 17:30, 19:30, 23:30
and dependent, job JOBX triggered by dummy DSN and runs almost near to JOBA and runs approx 13:38, 15:38, 17:38, 19:38 & 23:38
As CA7 , scan calendar schedule jobs, we are receiving first 2 jobs instances 13:30,15:30 in Q at same time and same way for next scan 17:30, 19:30
when job JOBX runs @ 13:38, both JOBA instances are running @ 13:38 and 15:30 <--- Here 15:30 instance rqmt will be satisfying and runs per submit time.
15:30 instance should run after 15:38
Please suggest some solution.
Thanks.
Original Message:
Sent: 11-06-2019 04:35 PM
From: RODERICK WOODS
Subject: Predecessor job posting problem
Haneef,
CA 7 is working as designed in the scenario you described.
- you have JOBA that is dependent on JOBX.
- now, you have 2 instances of JOBA in the request queue and both have a dependency of JOBX
- once JOBX start and completed, the dependency for both instance of JOBA will be satisfied.
Once in the queue there is no way to prevent both from being satisfied. If you don't want both instance of JOBA to run, you will need to look at some manual or automated way of preventing both jobs from being in the queue at the same time.
There are many ways to accomplish this, but without know the exact scenario I can't give you a simple solution.
Original Message:
Sent: 11-06-2019 03:10 PM
From: Haneef Syed
Subject: Predecessor job posting problem
CA7 job and its predecessor job both are running multiple times in a day.
We tried to add lead time with n hrs and also zero hours.
But in both cases, If there are two instances of job in Q , both were running one after the other, even only one predecessor job completed at that time.
My assumption is that , only one job instance will run after completion of predecessor job, but here both instances ran at time.
Please suggest how to resolve this issue.