On Fri, 24 Aug 2018 07:20:24 -0500, Tom Marchant wrote: >> via the Zowe command line you can stay in the laptop context >> and Zowe will fetch a data set behind the scene, allow it to >> be edited by your favorite editor and save back to z/OS >> transparently.
> Will it do so while providing integrity so that two users can't > edit the same data set (or member) at the same time, whether > using Zowe or ISPF? I would argue that shared files that might be updated by multiple users simultaneously should be in a source control system anyway. If the files MUST wind up in a PDS (parmlib members, anyone?), that staging should happen in a controlled manner. So - keep your text files in the Unix file system under the control of git. ISPF will happily edit USS files -- no need to copy them to a PDS. You can keep your parmlib members in an off-mainframe server (like an on-premises github or bitbucket server), have your changes code-reviewed by your fellow sysprogs, committed, and pushed to the parmlib via a deployment mechanism like Jenkins. All that stuff is accessed via the browser. You think that's crazy? It's how the off-mainframe world has been working for the past decade, at least. With the proper tools, and the willingness to learn to use them well, it improves productivity and reduces errors. IMO, it's time to start treating the mainframe like the complex, mission-critical embedded system that it is, and use modern tools to manage it. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
