I like the idea, but would probably not be able to pursue it due to internal 
issues. Still.... :-)

Bob

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Jesse 1 Robinson
Sent: Tuesday, November 15, 2016 3:22 PM
To: [email protected]
Subject: Re: Splitting a sysplex in two

By far the easiest--if least elegant--method is to copy the entire sysplex and 
restore whatever you need to make the second one work. It's untidy because 
you'll have lots of stuff in each plex that's meaningless. For example, 
production volumes will not be accessible from DEV and vice versa. The payoff 
is how quickly you can get the second plex working with minimal effort. We've 
done this here a few times over the years. 

Let's say you use the current combined plex for PROD and copy volumes to make 
DEV. Some 'system level' volumes will probably need to be created (or renamed) 
in the second plex. Catalogs can be copied as is. So can RACF profiles. You'll 
want a new JES environment and NJE node, but those are under your control. My 
goal is try like the dickens to relieve application folks from getting involved 
any more than necessary. If you're disciplined (I'm not!), you can clean up the 
images at your leisure to remove references to stuff that lives in the other 
plex. Mostly it doesn't hurt other than referring to objects that are 
unreachable. It's mostly messy. (I have an elevated tolerance for messy.)

.
.
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
[email protected]


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Richards, Robert B.
Sent: Tuesday, November 15, 2016 10:36 AM
To: [email protected]
Subject: (External):Re: Splitting a sysplex in two

Two different Sysplexes. Per Allan's Redbook recommendation and reversing the 
merge, there are these "plexes" to probably split:

CATALOGplex, DASDplex, ECSplex, GRSplex, JESplex, HFSplex, HMCplex, HSMplex, 
OAMplex, SAplex, RACFplex, RMFplex, RMMplex, SMSplex, TCPplex, VTAMplex, WLMplex

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Jesse 1 Robinson
Sent: Tuesday, November 15, 2016 11:41 AM
To: [email protected]
Subject: Re: Splitting a sysplex in two

(This time with content.) In my experience, splitting and merging a sysplex are 
two very different activities. Merging is by far the more difficult because you 
likely have resolve name conflicts of all kinds, especially data set names. Are 
two like DSNs copies of the same data? If not, do you delete one? Integrate the 
content together? Rename (at least) one to keep them distinct forever? 

Splitting hardly ever involves name conflicts because everything already lives 
together in the same environment. The biggest question in splitting PROD/DEV is 
whether you want everything to be accessible from both LPARs. If not, you have 
to build some barriers that presumable do not exist today. If you're aiming for 
two different sysplexes, sysplex boundary is a natural separator. If you're 
looking for two members of one sysplex, separating PROD and DEV will be more 
difficult. 

.
.
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
[email protected]

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Allan Staller
Sent: Tuesday, November 15, 2016 7:48 AM
To: [email protected]
Subject: (External):Re: Splitting a sysplex in two

You might also try "merging systems into a sysplex. It should be the same 
checklist, just operated in reverse.

Redbook SG24-6818-00

HTH.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Richards, Robert B.
Sent: Tuesday, November 15, 2016 9:43 AM
To: [email protected]
Subject: Splitting a sysplex in two

I am in the process of planning for the splitting of a single sysplex into one 
PROD and one DEVL. Does anyone have a good checklist for this? The last time I 
did this was quite some time ago.

I probably have most of the tasks identified, but can no longer find that old 
documentation I thought I had kept (too many laptop replacements). :(

Looking for someone that may have kept theirs. In the meantime, reading 
"Setting Up a Sysplex" again for the nth time for memory clues :)

Bob

----------------------------------------------------------------------
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

Reply via email to