On 7/29/2015 4:13 PM, J O Skip Robinson wrote:
I refrained from answering earlier because we're an all-RACF shop. However, I
can comment the extent of (RACF) database sharing. We have a bronze-plex that
resulted from bolting together two previously independent parallel sysplexes,
one with two members and another with only one. These sysplexes were
independent for business reasons. RACF databases could not be combined because
a given userid or dataset might be defined in both with different access levels.
The result is a single parallel sysplex in which the two like members share
everything, while the third shares only enough to qualify for sysplex
licensing. (An IBM-invented game.) This arrangement is far from ideal, but the
two birds-of-a-feather share RACF while the odd man out has his own non-shared
database. It's been working OK for several years.
.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
I run into this all the time, especially when production, test, and
sandbox LPARs are mixed into a sysplex. Typically the production
systems share a RACF DB, the test systems share a different RACF DB,
etc. Works fine.
Regards,
Tom Conley
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
