This is a good point. For PDS what would be ideal is that you checkout a member and when saving it perform a diff / merge (while holding the ENQ) for a short period of time. Not a long hold that will eventually cause issues with ENQs that were requested and not released in a timely manner.
Matt Hogstrom [email protected] +1-919-656-0564 PGP Key: 0x90ECB270 Facebook <https://facebook.com/matt.hogstrom> LinkedIn <https://linkedin/in/mhogstrom> Twitter <https://twitter.com/hogstrom> “It may be cognitive, but, it ain’t intuitive." — Hogstrom > On Aug 29, 2018, at 7:16 AM, Jerry Callen <[email protected]> wrote: > > <rant> > > The whole idea of holding a lock on a file while a human being slowly edits > it is so 1960s. > > Since at least the mid 1970s, editors like emacs have loaded the file for > editing and noted the timestamp. When the user attempts to save the file. the > timestamp is checked again, and if it changed, the user is asked what to do. > > And, of course, if you use a distributed source control system like git, > handling merge conflicts is a built-in and normal part of the process. > > It's very easy to imagine a zowe plugin that backs a source PDS with a git > repo on a server (GitHub/BitBucket) and integrates editing with the whole git > ecosystem of branches and pull requests. > > I say again: z/OS systems are too complex and mission-critical for us to > continue using outdated tooling and engineering processes to maintain them. > > </rant> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
