IBM Mainframe Forum

[Aishwarya S]

The Requirement is as below:
I have two jobs A and B
B runs on all days
A runs on specific days.Say monday and tuesday.

On Monday and Tuesday I want B to run only after A completes. B is not a direct trigger by A. A is just a dependency for B to run. If I place the depence on B that it runs only after A complets, then the job would be waiting for its dependency on all days.

[Robert Sample]

Set B up with two schedids -- one for the days A runs, one for the days A doesn't run. Make the dependency on A based on schedid.

[Aishwarya S]

Thought of it.But I doubt if there are jobs been triggered by B which expects the schid existing then will it not create an issue

[Robert Sample]

If there are jobs triggered by B, then you should have mentioned that as part of your original post. If you don't provide full information, the answers you get back will not be complete, of course.

Work with your site support group to set up CA-7 the way you need for these jobs.

[Aishwarya S]

Thanks robert. I was trying to explore easier ways of doing it. May be adding a dummy job could help.
Posted in the forum to chose the easiest option. I shall try scheduling with different SCHID's. Thanks for your response

[dick scherrer]

Hello,

Posted in the forum to chose the easiest option.

Surely the worst way to choose an implementation method. . .

What you Need (not what you want) is that this will run correctly every time for years and years. Saving an hour is not worth the long-term grief caused by lazy implementation. . .

fwiw.

[Aishwarya S]

There could be smart ideas as well. There is nothing wrong in exploring.

[dick scherrer]

Hello,

There could be smart ideas as well. There is nothing wrong in exploring.

I am a big proponent of exploring and also of "smart ideas".

I am not in favor of looking firstly at ease of implementation, but rather in providing a good long-term solution. These are often quite different and incompatible. . .

Probably i should not protest too much - i have been hired many times to re-do something that was "thrown in" the easiest way possible and after the frustration of dealing with the shoddy performance, the organizations decided to bring in someone to re-implement. . .