The problem of merging sysplexes is a superset of merging LPARs. You have to manage all the issues of LPAR merge as well as sysplex merge. For the most part, sysplex issues are easier at the CF and couple data set level. The really hard thing is resolving data set names all the way from TSO user stuff up to catalog names.
My first foray into LPAR merge was way before sysplex. Two LPARs in two data centers needed to become one. Everything was owned by the same folks, but the history of the two centers had diverged years earlier. There were (conservatively) hundreds of identically named data sets A.B.C in both centers. Some pairs may have had identical content, others not despite the same name and same owner. When you merge, every single collision must be investigated *individually* and resolved: keep #1, keep #2, keep both under different names. There is no formulaic answer. Fast forward to post Y2K. We were compelled to merge two sysplexes for licensing reasons. Again, all the same ownership but historically diverse. The deadline was imminent. No one wanted to spend umpty-ump dollars on a task with no business case other than PSLC charges. So we created a 'bronze-plex', parallel sysplex for SMF/RMF purposes but still functionally separate for most practical purposes. I will spare you the details of surviving such an activity unless you really need to learn more. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Cameron Conacher Sent: Tuesday, May 09, 2017 8:07 AM To: [email protected] Subject: (External):Re: Merging SYSPLEXes Information.... Hello, Yes the SYSPLEXes are all physically in the same site. My feel is that it has to be easier/cheaper/less risk to migrate entire LPARs, rather than to migrate application by application. I will read through the red book suggested (also recommended by Kees and Allan. Thanks On Tue, May 9, 2017 at 9:59 AM, Elardus Engelbrecht < [email protected]> wrote: > Cameron Conacherwrote: > > >I am looking for any information to read that is related to Merging > SYSPLEXes. We have a few SYSPLEXes, each with a couple of LPARs. I > wanted to see how much effort would be involved in collapsing into fewer > SYSPLEXes. > > It depends of course. Are these Sysplexes all at one site or not? > > > >Once I collapse say SYSPLEX#7 into SYSPLEX #1, all of SYSPLEX #7 data > would available to SYSPLEX #1, so it would be much easier to migrate > workloads from one LPAR to another. When I use my old friend Google, I > get lots of hits on creating a SYSPLEX, but I wanted to be able to > merge two SYSPLEXes into one. > > Perhaps you should start looking which Sysplex is the surviving one > and then bring all the LPARs of one Sysplex into that. When finished, > move on to the next Sysplex and all their LPARs. And so on with the other > Sysplexes. > > > >Can someone point me to some information I could read through that > >would > help me get my arms around this one? > > What about this Redbook 'Merging Systems into a Sysplex' in > > http://www.redbooks.ibm.com/abstracts/sg246818.html?Open ? > > Groete / Greetings > Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
