Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Dependency problem in CA7

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CA Products
View previous topic :: :: View next topic  
Author Message
GiridharanN

New User


Joined: 12 Apr 2007
Posts: 21
Location: Coimbatore

PostPosted: Wed Jan 02, 2008 7:05 pm    Post subject: Dependency problem in CA7
Reply with quote

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
View user's profile Send private message

arnth01

New User


Joined: 15 Jan 2008
Posts: 2
Location: Evanston, IL

PostPosted: Wed Jan 16, 2008 7:07 pm    Post subject: Reply to: Dependency problem in CA7
Reply with quote

Use JDEP with LEADTM=0000
Back to top
View user's profile Send private message
HappySrinu

Active User


Joined: 22 Jan 2008
Posts: 195
Location: India

PostPosted: Thu Jan 24, 2008 7:30 pm    Post subject: Re: Dependency problem in CA7
Reply with quote

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
View user's profile Send private message
bharath18

New User


Joined: 12 Sep 2006
Posts: 15
Location: Chennai, Tamilnadu, India

PostPosted: Wed Feb 20, 2008 3:28 pm    Post subject: Re: Dependency problem in CA7
Reply with quote

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
View user's profile Send private message
thisak

New User


Joined: 09 Jun 2006
Posts: 14

PostPosted: Wed Mar 19, 2008 4:08 pm    Post subject:
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CA Products All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Problem reading GTF trace output danik56 ABENDS & Debugging 7 Thu Mar 16, 2017 1:02 pm
No new posts ROUNDED Problem with COMPUTE statement shalem COBOL Programming 11 Thu Feb 09, 2017 8:16 pm
No new posts SYMNAMES problem jacobdng DFSORT/ICETOOL 7 Thu Dec 22, 2016 7:47 am
No new posts Problem in writing Output file vickey_dw COBOL Programming 5 Mon Nov 14, 2016 11:14 pm
No new posts Problem in Running Query via JCL vickey_dw DB2 3 Tue Oct 18, 2016 11:11 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us