> disagree with Ted that you've been "lucky" with ISPF edit since it does use > an ENQ to protect on a member level basis. But that only works if everyone > plays by those rules.
As recently as z/OS 1.4, I have seen two people corrupt members using ISPF with different member names. >Also there has been some extra protection for a *long* time that keeps two >tasks from opening a PDS for output (IEC143I 213-30 abend). When you edit a PDS member, the file is not open for output. The member is just a memory copy. It's opened for output, when you save it. ISPF keeps information in memory, but does not re-read the directory. So, if two people (or more) are editing members, directory already read, the last saver 'wins'. Try it! You won't like it. I did a test with some of our developers, just about two years ago. The data was corrupted. - Too busy driving to stop for gas! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
