I'm not the sysprog, so I may not have all of the details, but if I remember correctly these are the issues:
We have PDSESHARING(NORMAL) in our IGDSMSxx member, rather than PDSESHARING(EXTENDED). >From >http://publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp?topic=/com.ibm.zos.r9.idad400/pdsesh3.htm "In a multiple-system environment, the system programmer uses PDSESHARING(EXTENDED) to share PDSEs at the member level. A system programmer must specify PDSESHARING(EXTENDED) in the IGDSMSxx member in the SYS1.PARMLIB on each system in the sysplex. Every system that is sharing a PDSE must be a member of the sysplex and have the sysplex coupling facility (XCF) active." We don't have the sysplex, so we're stuck with PDSESHARING(NORMAL). This causes problems when one system has a PDSE open and a second system opens it and tries to update it. Take for example the following scenario, which I just tested. On system 1 I open a PDSE with ISPF VIEW. On system 2 I open the same PDSE with ISPF EDIT. On system 2 I open a member in that PDSE and attempt to save it. I get the following error: IEC143I 213-70,IGG0191B,FJS,APPPROG,ISP11523,0469,TSO001,FJS.APPL.COBOL This means "70 OPEN detected a cross-system share conflict for the PDSE. " This issue does not occur when I do the same exact thing with a PDS. Anyway, systems has given us the direction to not use PDSEs. (Well, we can use them for our own personal datasets, but at our own risk.) Frank -- Frank Swarbrick Applications Architect - Mainframe Applications Development FirstBank Data Corporation - Lakewood, CO USA P: 303-235-1403 On 12/3/2009 at 9:50 PM, in message <002101ca749d$5fda4cf0$e6f71...@foggybottom>, George Fogg <[email protected]> wrote: > I believe the OP mentioned GRS in shared dasd environment and having > problems with PDSEs. I for one would like to know what the problems were. > George Fogg > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf > Of Tony B. > Sent: Thursday, December 03, 2009 6:09 PM > To: [email protected] > Subject: Re: IEC143I 213-30 > > Sorry I lost track of most of the interim suggestions toward this thread. > Did anyone suggest using a PDSE as the target library? Years ago I cobbled > together a poor man's scheduling system that used a single PDSE as a > repository of members that each nightly batch job would add, as they > completed with CC<5. Hundreds of jobs updated this PDSE over the course of > the evening, resulting in thousands of members having been written. . > > Sorry if I've restated someone else's post. > > > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf > Of Frank Swarbrick > Sent: Thursday, December 03, 2009 5:34 PM > To: [email protected] > Subject: Re: IEC143I 213-30 > >>>> On 12/3/2009 at 6:39 AM, in message > <[email protected]>, "Shmuel Metz (Seymour J.)" > <[email protected]> wrote: >> In <[email protected]>, on 12/02/2009 >> at 12:51 PM, Frank Swarbrick <[email protected]> said: >> >>>So perhaps a combination of the two is in order. Write to a temporary >>>PDS during the translate and then use DISP=OLD on the copy from the >>>temp PDS in to the actual PDS. >> >> The Initiator does the DISP=OLD ENQ at the beginning of the job. > > So you are saying that there is no point doing the two step process I > mention because it will have the file enqueued for the life of the job no > matter what, if DISP=OLD is specified? Hmm, oh well. Thanks for the info. >>> 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
