If you work with Relative GDG numbers, the whole GDG is enqued until the job ends. Bypass by using a specific G####V00 in your JCL. Or a different GDG base name.
On Tue, Sep 12, 2017 at 11:54 AM, Kirk Wolf <[email protected]> wrote: > Is there a way around this? > > Even with SMS-managed GDGs, where the generation is cataloged at > allocation, two jobs that dynamically allocate +1 generations (with GDGNT) > will collide. > > For example, from two different jobs: > > (job 1) > ./bpxwdyn.rexx "alloc fi(mydd) da('managed.test.gdg(+1)') recfm(v,b) new > catalog gdgnt lrecl(1028)" > BPXWDYN RC= 0 (0x0) > > (job 2) > ./bpxwdyn.rexx "alloc fi(mydd) da('managed.test.gdg(+1)') recfm(v,b) new > catalog gdgnt lrecl(1028)" > > BPXWDYN RC= 34603008 (0x2100000) > IKJ56225I DATA SET MANAGED.TEST.GDG ALREADY IN USE, TRY LATER+ > IKJ56225I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER > IEFA110I DATA SET CONTENTION > ... > > Kirk Wolf > Dovetailed Technologies > http://dovetail.com > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
