PDSE corruption is a different issue. Plenty on that in the archives. SMP/E is not relevant to this context AFAICT.
To diagnose the PDS corruption issue, I'd start in my GRS parms. -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Wednesday, February 18, 2009 3:18 PM To: IBM-MAIN@bama.ua.edu Subject: Re: EXECIO Thank you for that. What is missing? It was a 4000 MIPS 5-image SYSPLEX with two members running TSO. We had many PDS member issues. Plus, many SMSPDSE 'corrupt' messages issued. I'm more of a performance/capacity type, and haven't used SMP, since SMP4. I am not trying to mislead, but I've been able to re-create the (different) members update problem without even trying. - Too busy driving to stop for gas! -----Original Message----- From: Hal Merritt <hmerr...@jackhenry.com> Date: Wed, 18 Feb 2009 15:02:34 To: <IBM-MAIN@bama.ua.edu> Subject: Re: EXECIO To be fair, I don't think Ted is 'wrong'. He is simply reporting observed behaviors of his system. Many of us seem to be of the opinion that Ted's system is malfunctioning or misconfigured. I believe Ted to be describing an environment where GRS (or equivalent) needs some attention. I suppose there might be some exits that could muddy the water. -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Scott Rowe Sent: Wednesday, February 18, 2009 2:36 PM To: IBM-MAIN@bama.ua.edu Subject: Re: EXECIO Sorry Ted, but I believe you are wrong again. I just did a test based on the exact situation you outlined, and had no problem whatsoever (as I expected). >>> Ted MacNEIL <eamacn...@yahoo.ca> 2/18/2009 3:11 PM >>> > 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html