How do you propose to handle reference by relative generation if multiple entities can change relativity?
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Kirk Wolf Sent: Wednesday, September 13, 2017 12:25 PM To: [email protected] Subject: Re: GDG +1 dynamic allocation collision between two concurrent jobs 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 ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ---------------------------------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
