Two jobs triggers same job

Richa Jain · New User Joined: 18 Mar 2008 Posts: 35 Location: Gurgaon

One monthly job (job M) and one daily job (job D) is creating gdg version of same base.Job D is the requirement of Job M. Both the jobs triggered ndm job (job N).

Problem: If job M and job D creates gdg version at the same time then the NDM job will processed the latest version and missed one version.

How can I solve the problem? Is it possible to have a Job N as a requirement of Job M?

dick scherrer · Posted: Fri Jun 20, 2008 11:27 am

Hello,

Could you not include ndm in both jobs instead of running a separate ndm job?

HappySrinu · Active User Joined: 22 Jan 2008 Posts: 194 Location: India

if i understand your requirement correctly,..you got 3 jobs and

JOB D rund daily, - trigger - JOB N
JOB M runs monthly - trigger - JOB N

if this is the case i hope this problem occurs only one day in a month.

so schedule these two sets of jobs on different timings in scheduler tool .

hope it helps..

gcicchet · Posted: Fri Jun 20, 2008 12:02 pm

Hi,

firstly I can't see how 2 jobs create a dataset at the same time, even if they hit the JES Q at the same time there would be some contention, so why have the 2 jobs run at the same time ?

Why not have JOB M wait on JOB N of daily run ?

There are also things in CA7 such as mutually exclusive, talk to a scheduler, it should be quite easy.

It's been a long long time since I used CA7 so I don't recall specifics.

Another option would be to have the monthly job create a different dataset name, which would then need to be passed to JOB N or a different job.

Gerry

UmeySan · Posted: Fri Jun 20, 2008 2:57 pm

Morning Richa Jain !

Just to be shure, i interpreted it right:

Daily Job is D & monthly Job is M. Both creating a GDG(+1), same DSN.
At that special one day in month, D is a Predecessor of M.
But there is allways a last job called N, reading that created GDG(0).

Daily Plan: D - N
Monthly Plan: D - M - N

So here is my suggestion:

If possible, create a other monthly Job, say XYZ, Predecessors are D & M,
Succsessor is N. In Job N, define XYZ as a Predecessor.

The only step in this Job sorts the two created generations in one new generation. So this one would become the last generation for the last following Job including output of D & M at that special day in month.

Monthly Plan: D - M - XYZ - N

D-Job -> GDG(+1)
M-Job -> GDG(+1)

XYZ -> Input = (0)&(-1) Output = (+1)

N-Job -> GDG(0)

Richa Jain · New User Joined: 18 Mar 2008 Posts: 35 Location: Gurgaon

Thanks everyone for reply.

dick scherrer · Posted: Fri Jun 20, 2008 7:21 pm

Hello,

UmeySan · Posted: Mon Jun 23, 2008 4:17 pm

Hi !

>> impact of approach

Don't get overly excited. Just one more "little Step" in the whole Job-Network. No negative unexpected effects, if dependencies defined correktly. And the most easiest way.

@Dick:

Including NDM-JCL in both jobs.

If you have to modify the NDM-JCL, now you have to take care, that you customize the two JCL's. Or isn't it necessary?

cvadlamudi · New User Joined: 19 Apr 2007 Posts: 68 Location: India

Hi,

If you are sure that the Job M & Job D is going to be there on 1st of every month or the exact date... then you can schedule as per the Calender with the dependency.
Job N as a requirement for Job M or JobD.
ex : First JobD triggers JobN
Second JobM will get triggered only after JOBN is already run.. else you may get the call for the job in Queue.

dick scherrer · Posted: Mon Jun 23, 2008 9:43 pm

Hello,