On 31/08/2018 8:21 AM, Andrew Rowley wrote:
Of course it's possible to prevent simultaneous edits, at least to
the extent that you claim ISPF does. ISPF doesn't REALLY prevent
simultaneous edits; it relies on a convention, and you have to hope
that everyone follows the convention. That's the issue that started
this thread. In Unix that's traditionally been done with a lock
directory playing the role of an ENQ, but it can be done. It's just
that -- no one does, because source control is a better solution.
Everyone has to follow the convention, and on z/OS they largely do.
Many think that new z/OS applications should continue to follow the
convention, regardless of what people on other platforms do.
Source control is not a better solution, it is a solution to a
slightly different problem. When using source control you STILL need
to make sure that 2 people are not updating the same file at the same
time - it is just the window that is smaller.
Using a distributed VCS like Git everybody has their own copy of the
source code so there is never a case off two people updating the same
file at the same time. Conflicts are detected when pushing changes and
that's when merging kicks in.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
