It's possible to get away with inter-sysplex PDSE sharing for such a long time that people forget that it's verboten. I'm told that ISV serialization products like MIM do not solve this problem.
BTW this is a common inhibitor to COBOL V5, which requires PDSE for load modules. Many shops have historically shared load libraries across GRS-plex boundaries. This may work (indefinitely) for traditional PO. It's deadly for PDSE. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Staller, Allan Sent: Wednesday, July 15, 2015 8:46 AM To: [email protected] Subject: Re: Corrupt PDSE PDSE's *CANNOT* be shared across SYSPLEX Boundaries. PDSE's *CAN* be shared within a SYSPLEX if the SMSPDSE* address spaces are running... HTH, <snip> I get below message when i try to access a PDSE dataset, but when I try to access the same Dataset from a different SYSPLEX it opens up. We do share the Dasd . IGW702I PDSE Directory Validation Unsuccessful DESC:<ND> Structure is corrupted LTK: 00000000000000000000000000000000000000000000000000000000000000000000* ERROR NUM:15 ......remainder deleted </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
