On Thu, 12 Apr 2007 13:07:21 -0500, Dennis Trojak <[EMAIL PROTECTED]> wrote:
>Well I hate to open this can of worms but I wonder if anybody has >suggestions on how to prevent damaging a PDSE in a dual SYSPLEX >environment running a MIMPLEX. Don't do it if it hurts. :-) >I am running NORMAL not EXTENDED >PDSESHARING Doesn't matter. >and I know that IBM (and CA) does NOT support this mode for >cross-system/sysplex updates so I follow this rule with my target >datasets. IBM doesn't support sharing PDSE across sysplexes - period. Although many shops (like ours) share some as READ ONLY (sysres dsns). Same is true with HFS (we share a read only unix root). >The question I have is how do I prevent users from breaking >this rule with their own product PDSEs? I can tell them to stick to the >LPAR that has the PDSE open but that doesn't guarantee they will follow >the rule. I know there are other MIMPLEX sites out there so how do you >handle this? We handle it with SMS. All the application PDSE libraries (which are all Endevor controlled) are SMS controlled. Really a throwback from the days when PDSE data sets had to be SMS controlled. The SMS pools are not shared between the sysplexes. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group: G-ITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
