|
View previous topic :: View next topic
|
| Author |
Message |
seagull
New User
Joined: 28 May 2007
Posts: 24
Location: Dublin
|
|
|
|
| Your best option is to use a scheduler to prevent more generations being created while this job is processing. |
|
| Back to top |
|
 |
useit
Active User
Joined: 05 Oct 2006
Posts: 152
|
|
|
|
hi,
escapa's solution worked for me.
Ø Use IDCAMS and list all generations
Ø Parse output to create TSO delete command
Ø Execute those commands
Regds,
use it |
|
| Back to top |
|
|
useit
Active User
Joined: 05 Oct 2006
Posts: 152
|
|
|
|
seagull,
there is no direct dependency b/w different runs of jobs.
it was a real challenge to properly place the mutual dependencies.
And in case we had gone ahead with the approach of placing mutual dependencies then, it would really have been a messy approach complicating our schedule
Regds,
useit |
|
| Back to top |
|
|
daveporcelan
Active Member
Joined: 01 Dec 2006
Posts: 792
Location: Pennsylvania
|
|
|
|
| Quote: |
i know reading the base would read All the generations. but there is a chances of some other generation getting created in between.(which i want to prcess in the next run only)
|
This is not true.
If this Job uses DISP=(OLD,DELETE,KEEP) on the GDG base and the 'other' Job has DISP=(NEW,CATLG,DELETE) on the +1, then it is not possible to create 'some other generation'.
The first Job in gets control of the entire structure, and the other job will get a waiting for datasets message.
No scheduling required, no listcats and deletes, just clean and simple jcl.
Why do I bother? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hi Dave,
'Cause you can. . . 
Sometimes we actually do get thru to folks who have made something much more difficult that it needs to be. |
|
| Back to top |
|
|
|
|
