> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Mark Zelden > Sent: Wednesday, September 11, 2013 3:43 PM > To: [email protected] > Subject: Re: PDS/E, Shared Dasd, and COBOL V5 > > For what it's worth, my client has been using PDSE for all their > production loadlibs, source libraries, proclibs, etc. (managed by > Endevor) since sometime just after > Y2K. The initial reason I pushed for it was occasional JES2 PROC > issues after weekly > compress jobs would run. > > The only problem I recall in all these years was related to "illegal" > sharing between a prod / devl sysplex (via MIM) of a prod CICS loadlib > that someone included in a devl region shortly after we starting using > PDSEs for the Endevor controlled > prod/qa/devl/test environments. Because PDSEs had to be SMS controlled > ("going back to some ancient OS/390 release" as Ed said in a recent > post) and those sysplexes have different SMS pools and the DASD volumes > are not online to the other plex, no other mistakes have ever happened. > Actually, I'm a bit surprised myself after all these years that there > hasn't been a problem > every now and then due to sharing PDSE outside sysplex boundaries.
Have you any experience about performance differences to vanilla PDS. E g in IMS TP ? Best Regards Thomas Berg ___________________________________________________________________ Thomas Berg Specialist zOS\RQM\IT Delivery SWEDBANK AB (Publ) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
