On Wed, Sep 13, 2017 at 8:45 AM, Scott Ballentine <[email protected]>
wrote:
> Holding both ENQs keeps things somewhat "sane" - if multiple jobs are
> trying create or delete generations at the same time, then generations
> might not get rolled in properly or duplicate data sets can occur or
> "holes" can be created where some generations are missing.
>
>
I appreciate your response. I don't question that this is how it works,
but I don't really agree that this is the only sane implementation.
- "generations might not get rolled in properly"
this can happen in other ways, right?
- "duplicate data sets can occur"
With SMS? In this case the goovoo data set is cataloged at allocation
time and also ENQed
- "holes can be created where some generations are missing"
this can also happen in other ways.
"Extended GDG" support added new options, but IMO it is a pity that
concurrency was not considered as an option when creating new generations.
All of the suggested "tricks" to support this use case might lead one to
consider using something besides a GDG.
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
