Sharon, So long as you are current on your maintanence for PDS/E then yes. Only one system can do the UPDATE on a PDSE. All others must be READ. Maybe someone had compressed the library while it was being updated?
Lizette -----Original Message----- >From: "Lopez, Sharon" <[email protected]> >Sent: Nov 5, 2012 2:14 PM >To: [email protected] >Subject: Re: PDS/E sharing > >Ok....so if I'm in a Parallel sysplex with PDS/E extended and one lpar has the >library opened for read and the second lpar is trying to updates members >within the pds/e, it should work? > > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On >Behalf Of Staller, Allan >Sent: Monday, November 05, 2012 3:12 PM >To: [email protected] >Subject: Re: PDS/E sharing > >I presume the RC from the PDSE open was 70 or 74 > >Add the following to IGDSMS** ( PDSESHARING(EXTENDED) and >PDSE_RESTARTABLE_AS(YES)) and activate via SET SMS= > >This will cause 2 address spaces to be started (SMSPDSE and SMSPDSE1). After >these address spaces are started, the PDSE's can be updated just like any >other PDS. > >See DF/SMS Using Datasets (appropriate for your level of z/OS). Chapter 3 >topic 3.8.9.4.2 (z/OS 1.13) > >HTH, > ><snip> >I have a quick question on how everyone puts on maintenance to products that >require PDS/Es, dynamically. I have a product CA-SYSVIEW where the >loadlib is in lnklst and shared across 5 lpars in a sysplex. I want to >update members from one of the lpars, but when I try, I get an abend 213. Is >there any way to do this without having to create a separate library for each >lpar? Thanks. ></snip> > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
