View previous topic :: View next topic
|
Author |
Message |
GiridharanN
New User
Joined: 12 Apr 2007 Posts: 21 Location: Coimbatore
|
|
|
|
I have 2 jobs say JOBA and JOBB.
JOBA should run on the last working day (2300 hours) of the month.
JOBB should run on the first friday (0100 hours) of every month.
JOBB should always run after JOBA
When the first friday of the month happens to be the first day of the new month, the following problem occurs.
Due to some dependencies, when JOBA is delayed by greater than two hours, JOBB runs ahead of JOBA which is disastrous.
We could not alter the triggering cycle/Schedule ID of JOBA/JOBB because of other dependencies.
We also could not make JOBB a successor of JOBA because of the following situation.
When the last working day of a month is monday, there is a 96+ hours time difference between JOBA and JOBB.
Hence JOBB will not recognize run of JOBA and will keep waiting.
Can anybody suggest a solution to this? |
|
Back to top |
|
|
arnth01
New User
Joined: 15 Jan 2008 Posts: 2 Location: Evanston, IL
|
|
|
|
Use JDEP with LEADTM=0000 |
|
Back to top |
|
|
HappySrinu
Active User
Joined: 22 Jan 2008 Posts: 194 Location: India
|
|
|
|
GiridharanN wrote: |
I have 2 jobs say JOBA and JOBB.
JOBA should run on the last working day (2300 hours) of the month.
JOBB should run on the first friday (0100 hours) of every month.
JOBB should always run after JOBA
When the first friday of the month happens to be the first day of the new month, the following problem occurs.
Due to some dependencies, when JOBA is delayed by greater than two hours, JOBB runs ahead of JOBA which is disastrous.
We could not alter the triggering cycle/Schedule ID of JOBA/JOBB because of other dependencies.
We also could not make JOBB a successor of JOBA because of the following situation.
When the last working day of a month is monday, there is a 96+ hours time difference between JOBA and JOBB.
Hence JOBB will not recognize run of JOBA and will keep waiting.
Can anybody suggest a solution to this? |
hey, this might be usefull but not recommended by SME's..
this can solved by lot ways especialy in CA7.
i guess we can use calendar and can fix this problem.
but for you immediate fix, add a step in JOBA and make it created and cataloged. then make JOBB the dependent on both (it should run on friday) and trigger by this dataset also. make sure it depends on both the conditions.
so if the last day of the month is friday, the JOBB will recognize the dataset and can run.
but i am pretty sure there is a much easy way in CA7 we can use to fix this situiation |
|
Back to top |
|
|
bharath18
New User
Joined: 12 Sep 2006 Posts: 15 Location: Chennai, Tamilnadu, India
|
|
|
|
You should be using the calendar days it should be running.. ie.. julian date.
We have certain list of job whihc ahs to run bimonthly and to trigger other list of jobs after completing, if joba doesnt comlplete we could come to know as it fails to run with return code or failure of job notifications.
You can take measure of it and make it fine as before the job b runs.
Hope this helps,
Bharath.
bharathmutha@gmail.com |
|
Back to top |
|
|
thisak
New User
Joined: 09 Jun 2006 Posts: 14
|
|
|
|
Hi GiridharanN,
Even in our Production, we have similar kind of dependency; which we handle by the method mentioned by Srini (HappySrinu).
What he said can be elaborated as follows: -
1. A file (blank & static) has to be created at end of job JOBA.
2. The same file should be checked at the first step of JOBB using VERIFY operator of IDCAMS utility.
3. And make sure you are deleting the file in JOBB somewhere (preferably last).
So, thats how it goes.
Let me know incase of any questions.
Thanks,
Sakthi. |
|
Back to top |
|
|
|