#2 The only safe way to do this is not to share DASD outside the scope of a Sysplex. I don't expect that to change. Having at least System Test, Development and Production Sysplex that completely isolate DASD lets you get the most benefits from isolation of those types of workloads.
-----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of R.S. Sent: Tuesday, May 12, 2020 10:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IGDSMSxx setting PDSE_VERSION(2) My humble opinion: Everybody who want or really need PDSE v2 will create such dataset explicitly by specifying DSNTYPE=(LIBRARY,2). That's OK. You want to create PDSE v2 by default. This is the best way to find out which system components or application still not tolerate new PDSE flavour. But this is hard way. It can be nice when application will refuse to open new dataset, but things may go worse way when the problem occur in the middle of "landing the plane". BTW: The only case when I needed PDSE v2 was huge PTF (for WAS), which exceeded the limit of member size of SMPPTS. However it was before PDSE v2 was born so I switched to plain old PDS. PDS members are not limited in size, however PDS itself is limited to 64k TRK which is much less that limit of member size for PDSE v2. And I'm still missing two things: 1. Multi-volume PDSE. 2. PDSE sharing across the sysplex. It can be even "by command" sharing like "F PDSE=SYS1.TEST1,CLOSE" on one system to be able to open it on another system. It is much better than educate folks to not share PDSE's. -- Radoslaw Skorupka Lodz, Poland The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
