I'm glad it worked, I still wouldn't trust it to do so. I trust sharing PDSE in static read-only mode because some folks I trust on this list who are far more knowledgeable than I assure me. I do not trust the in memory aspects of PDSE in one LPAR to notice (and so continue in future releases) update made in another LPAR without the benefit of Sysplex. If the artist, or some of the others were to give me such assurances, I might change my mind. But with OCO and the documented unsupported status of such behavior, I don't think any of them would be so willing.
Your mileage may vary and other comments from Phil's disclaimer :) > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Frank Swarbrick > Sent: Saturday, August 08, 2009 9:42 PM > To: [email protected] > Subject: Re: DASD: to share or not to share > > That is exactly what I did. Well, "as quickly as I could type", in any > case. > We have PDSESHARING(NORMAL) in our IGDSMSxx file, for whatever that might > be worth. > > Frank > > On 8/8/2009 at 1:31 AM, in message > <[email protected]>, > "Gibney, > Dave" <[email protected]> wrote: > > Actually I was speculating about the ability to "refresh" in memory > > knowledge of the PDSE(s) in the other LPAR(s). What you describe is not > > guaranteed. > > Try 1. Run existing copy of the program in LPAR-P. 2. Quickly update > > it from LPAR-other. 3. Quickly try in LPAR-P. I don't believe you will > > always get the new version. > > > >> -----Original Message----- > >> From: IBM Mainframe Discussion List [mailto:[email protected]] On > >> Behalf Of Frank Swarbrick > >> Sent: Friday, August 07, 2009 1:34 PM > >> To: [email protected] > >> Subject: Re: DASD: to share or not to share > >> > >> So for example, if our change control process for applications runs in > > DEV > >> (which is how we have it in VSE) we should be able to update our > >> production application loadlib PDSE from DEV exclusively and this will > > not > >> be a problem, even without a Sysplex? I am curious as to where I find > >> this PDSE address space refresh command, and if it's really needed. I > >> just compiled a program in to a PDSE in DEV and ran it in PROD and it > > ran > >> the new version just fine. Did it twice just to make sure. No > > problem > >> either time. > >> > >> Frank > >> > >> On 8/7/2009 at 3:27 AM, in message > >> <[email protected]>, > >> "Gibney, > >> Dave" <[email protected]> wrote: > >> > I agree, but I doubt this applies to someone converting from VSE to > >> > their first z/OS LPAR(s). And, I think with "careful" change > > management, > >> > you could update even shared PDSE without sysplex. Do the update > > from > >> > only one system ever and cause that PDSE address space (can't > > remember > >> > it right off) to refresh in the other LPARs. > >> > > >> >> -----Original Message----- > >> >> From: IBM Mainframe Discussion List [mailto:[email protected]] > > On > >> >> Behalf Of Bruce Hewson > >> >> Sent: Thursday, August 06, 2009 10:51 PM > >> >> To: [email protected] > >> >> Subject: Re: DASD: to share or not to share > >> >> > >> >> Hi Dave,, > >> >> > >> >> with systems that are only IPL'd every 3-5 months, YES, there will > > be > >> >> updates > >> >> to those volumes. Changes still happen, and many fixes do not > > require > >> > an > >> >> IPL > >> >> to implement, only careful change management. > >> >> > >> >> On Thu, 6 Aug 2009 14:18:15 -0700, Gibney, Dave <[email protected]> > >> > wrote: > >> >> > >> >> >It may not be "supported", but PDSE that are only read are safe to > >> > share > >> >> >betwixt anything. And, since it's a "live" resvol, it is of course > >> > not > >> >> >subject to updates, right? > >> >> > > >> >> >Dave Gibney > >> >> >Information Technology Services > >> >> >Washington State University > >> >> > > >> >> > >> >> > >> >> Regards > >> >> Bruce Hewson > >> >> > >> >> > > ---------------------------------------------------------------------- > >> >> 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 > >> > > >> > > > ---------------------------------------------------------------------- > >> > 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 > >> > >> >>> > >> > >> The information contained in this electronic communication and any > >> document attached hereto or transmitted herewith is confidential and > >> intended for the exclusive use of the individual or entity named > > above. > >> If the reader of this message is not the intended recipient or the > >> employee or agent responsible for delivering it to the intended > > recipient, > >> you are hereby notified that any examination, use, dissemination, > >> distribution or copying of this communication or any part thereof is > >> strictly prohibited. If you have received this communication in > > error, > >> please immediately notify the sender by reply e-mail and destroy this > >> communication. Thank you. > >> > >> ---------------------------------------------------------------------- > >> 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 > > > > ---------------------------------------------------------------------- > > 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 > > >>> > > The information contained in this electronic communication and any > document attached hereto or transmitted herewith is confidential and > intended for the exclusive use of the individual or entity named above. > If the reader of this message is not the intended recipient or the > employee or agent responsible for delivering it to the intended recipient, > you are hereby notified that any examination, use, dissemination, > distribution or copying of this communication or any part thereof is > strictly prohibited. If you have received this communication in error, > please immediately notify the sender by reply e-mail and destroy this > communication. Thank you. > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
