Yes, PDS/E shared outside of Sysplex is a problem if the sharing is not close to strictly read only. Specifically, address spaces with the PDS/E open in LPAR A will not like it after you update the PDS/E from LPAR B (we have 4 monplexes and I know this for sure:). There is "stuff" in memory in LPAR A that doesn't get updated from actions in LPAR B.
This applies to all PDS/E, not just program libraries. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Monday, September 09, 2013 6:26 PM To: [email protected] Subject: PDS/E, Shared Dasd, and COBOL V5 I have run into this situation a bunch because I have 2 Plexes that share the dasd. When the dasd on the valid Plex is online to the one it is NOT supposed to be on, then I can get SVC Dumps due to PDS/E datasets being touched across the boundaries. With the upcoming change in COBOL V5 to use PDS/E datasets for Load Libraries, it will make it more of a challenge for us to keep the Plexes totally separated. We will need to go through a re-Education for our application groups that have relied on the ability to shift files between Plexes without having to transmit it. Just my $0.02 worth Lizette ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
