OK,
Objectives: Simple, low cost (no new equipment if I can help it), low
overhead, isolate production from development.
We do not need the things that parallel sysplex would give us; anyway, a
parallel sysplex on a single box doesn't make sense to me.
We do want:
.. GRS that works in a way that makes sense: cross-system ENQ,
convert RESERVEs
.. Shared HSM, RMM, catalogs, virtual tape. Probably NJE instead of
shared spool.
.. Give the developers a place to work so they don't need to log on
to prod except to upgrade or fix things
.. Developer tools won't run on production
"Isolation" can be accomplished with some vary-offline commands in
COMMND00, that allows us to vary prod volumes online to dev if we have to.
And I know about opinions on ibm-main, I've been here before :-)
On 9/13/2013 11:28 AM, Norman.Hollander wrote:
Before reading books on Sysplex mechanics, and it certainly is less
challenging with a basic Sysplex,
You should ask yourself what objectives you are trying to accomplish. The
first objective should be
Availability. For complete High Availability and Continuous Availability,
you would actually need a
Coupling Facility for a Parallel Sysplex. A Parallel Sysplex has a bit more
complexity in the Capacity
Planning areas and the logistics of Recovery. The mechanics are really not
difficult: there is pre-positioning
Your current environment, defining the Sysplex, and then implementing it.
Are you planning to divide the
DASD farm? Is everything to be shared? Is it OK to have Development access
Production data? There is a
some considerations to think about; so be careful moving forward. All of
the Redbooks are an excellent
start to understand what you'll need. Be sure to ask question here. Many
of us will have definite opinions
for you.
zNorman
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Lizette Koehler
Sent: Friday, September 13, 2013 8:01 AM
To: [email protected]
Subject: Re: Sysplex newbie
Have you reviewed the REDBOOKS on setting up a SYSPLEX? Have they been
helpful?
http://www.redbooks.ibm.com/abstracts/sg242079.html
http://www.redbooks.ibm.com/abstracts/sg246485.html
http://www.redbooks.ibm.com/abstracts/sg247817.html
http://www.redbooks.ibm.com/abstracts/sg245235.html
http://www.redbooks.ibm.com/abstracts/sg246818.html
http://www.redbooks.ibm.com/abstracts/sg244356.html
http://www.redbooks.ibm.com/redbooks/pdfs/sg246485.pdf
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Jim Blalock
Sent: Friday, September 13, 2013 7:25 AM
To: [email protected]
Subject: Sysplex newbie
Hi folks,
We have a single z10, and would like to split its main partition into
production and developer partitions. Capacity should be ok. We're looking
at all the stuff we need to worry about sharing, like GRS, spool, RACF, RMM,
HSM, catalogs, virtual tape, etc etc. But underneath it all, we probably
need to set up a sysplex.
Keep in mind that we've never set up a sysplex before or done any real
sharing beyond shared DASD, so there will be dumb questions.
I think a basic sysplex will be enough, that way we won't need a coupling
facility. We will need a way for them to talk to each other (and probably
with one or two sandbox lpars), so I'm looking into CTCs.
The question I haven't found an answer to is how to use CTCs without an
escon or ficon switch; we have spare channels and I want to do this on the
cheap if I can.
I'm still reading about it, but any insight would be appreciated. Thanks!
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
