Two suggestions:
1) the "setting up a sysplex" series of manuals
2) the "merging systems into a sysplex" manuals.
Sorry, don't have the manual numbers handy.
Suggestions:
1) create 2 (2 image) sysplexes (i?). one for test/dev, the other for
production.
2) GRS, XCF, etc. can be handled via CTC adapters. Just need some cables.
3) *DO NOT* share anything between test/production sysplexes. Data can be
transferred via NJE or TCPIP or HIPERSOCKETS.
( a couple of "temporary shared" volumes can be created/destroyed for
"extra large" needs).
<snip>
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.
</snip>
Bear in mind, that the whole point of a sysplex is to "share everything" . Some
of the items below are hard to do in a sysplex sharing dev/prod images.
<snip>
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.
</snip>
HTH,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
