We have separate DB's for each Sysplex BUT keep them in sync using RRSAF so password changes and profile updates flow from the initial system to all the others. In the case of the Sandbox Sysplex we allow updates IN but not OUT - allowing us to test RACF changes in the Sandbox Sysplex and not propagate to the other Sysplexes. This does mean that you need to maintain a consistent naming convention where Prod is Prod and Dev is Dev across the enterprise (e.g. Don't reuse Prod DS name in Dev and grant different accesses because its Dev.
Jerry Whitteridge Delivery Manager / Mainframe Architect GTS - Safeway Account 602 527 4871 Mobile jerry.whitteri...@ibm.com IBM Services > From: fred glenlake <fred.glenl...@outlook.com> > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 05/03/2018 09:19 AM > Subject: RACF on a Sysplex?? > Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> > > Hello, > > We are going from one production lpar and one test lpar to two > sysplexs, one plex for production, one plex for test. Currently > the RACF databases are shared (yeah not ideal) but they will be > split (prod and test on their own databases) once we are sysplexed. > > In preparation for the split and the new sysplexes I want to split > up the databases ahead of time. I am new to sysplexes so excuse > the silly questions. > > Currently my primary and backup RACF databases are on DASD, shared > DASD between prod and test. I am going to move them to non-shared > DASD so prod has its own databases and test has its own. In a > Sysplex should the RACF databases still reside on DASD that both > sides of the sysplexes share (so both prod lpars in the plex) or > should they reside in the coupling facility or ?? > > Are there any tools that will help me get to my end state, split up > the databases, report on the databases, etc.?? Normally I just use > the RACF utilities ICH***** but perhaps other sites use different > tools I could look into. > > Any suggestions, comments are most welcome. > > FredG. > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
