When we were transforming our environment from separate CPUs/LPARs to sysplex,
we did so by subdividing existing systems into sysplex members rather than
combining systems into sysplexes. Resulting sysplexes were based on traditional
workloads. We ended up with one sysplex that only one member.
See below and thank you very much for all the information and suggestions.
Jerry
From: IBM Mainframe Discussion List on behalf of
Peter Bishop
Sent: Tuesday, June 2, 2020 8:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: XCF/GRS question
This message was
Hi Jerry,
questions, and a suggestion. These are more at the hardware layer than the GRS
one, which I saw Paul Feller addressing quite well. It may be that you cannot
change the LPAR setup, but if you can, here are some ideas.
1. Must the CFs share the GPs with the z/OS systems, or are ther
Jerry, I don't have the type of setup you have but I'll list a few things I
might look at.
Move the CONTENTION NOTIFYING SYSTEM from your TEST lpar to your MVSZ lpar,
assuming MVSZ is your production lpar. This process can add overhead to GRS
and on a small lpar it can be noticeable. The proc
