On Wed, 13 Sep 2017 07:18:13 +0200, Peter Hunkeler 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.
>
>Not according to the FM "DFSMS Using Data
On Wed, 13 Sep 2017 07:29:43 +0200, Peter Hunkeler wrote:
>I think the main problem here is dynamic allocation (SVC99) is not allowing
>the unauthorized caller to specify it should enqueue uncondtionally. For that
>reason BPXWDYN, TSO ALLOCATE, etc return with "data set in use" instead of
I think the main problem here is dynamic allocation (SVC99) is not allowing the
unauthorized caller to specify it should enqueue uncondtionally. For that
reason BPXWDYN, TSO ALLOCATE, etc return with "data set in use" instead of
offering the option to wait until it becomes available.
--Peter
Sorry, sending out too early. I repost with the full list of guidelines
>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.
Not according to the FM "DFSMS
>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.
Not according to the FM "DFSMS Using Data Sets", which says under "Submitting
Multiple Jobs to Update a
