Just keep in mind that AFAIK opening a PDSE still requires SMS to be active. That means that certain libraries opened very early in IPL must still be standard PO.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: Thursday, September 22, 2016 7:41 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: PDSE supported for product dataset z/OS version Radoslaw Skorupka wrote: >It was 25 years ago. Things changed. Indeed. >Nowadays the most popular way to destroy PDSE is to share it across sysplexes. Or using undocumented or wrong system services to use them... If you do those stunts across sysplexes, I'm running away. >People who are reluctant to use PDSE have ... no choice. Too bad... Too sad. Consider using PDSESHARING(EXTENDED) Some of my ICETOOL jobs crashed (OPEN abend) because of too many PDS members opened to write/overwrite. Solved that by moving over to PDSE instead having to use lots of PDS datasets with fewer members. [1] >Now, COBOL v5 and v6 do require PDSE for linked binaries. We're not there (at 4.2.0), but trust me, our programmers will faint when they find out about that requirement. ;-) Groete / Greetings Elardus Engelbrecht [1] - I have considered using temp PS datasets as output instead of permanent PDS/PDSE members, but I want to see the contents long after the ICETOOL jobs were purged. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
