You should not rebuild your RACF database.. you only do that the very first time you install RACF.
You would typically add the RACF definitions for the new system ids/minidisks - like those buggers that change names (e.g. 6VMDIR10, 6VMTCP10) ... and then at some point where you don't think backing off is going to happen - remove the definitions for the old system ids (e.g. 5VMDIR40).. I think rebuilding the RACF database just for a z/VM OS upgrade is madness :) You don't want to start over - you want to 'manage' it. Scott Rohling On Tue, Feb 21, 2012 at 11:30 AM, Troy A Slaughter <t...@ntrs.com> wrote: > I'm wondering how others update z/VM's RACF during a z/VM OS upgrade. > Given a scenario where a new z/VM OS is sitting on first level with it's > own DASD. How do you convert and merge the old database and the new ID > entries into one unified RACF database? In the past, I've would merge the > two USER DIRECTs by appending my non system IDs from the old z/VM OS to the > end of the new USER DIRECT. Then I use the RACF utility to build a new > database with the USER DIRECT as a source. So, at least, all of the IDs > exist. The only problem with that is the customizations that have been > made on the old database are lost. User current passwords are lost...that > sort of thing. You can add the customizations manually to the output > dataset before using it to create the database but that is error prone. > > How are others handling the RACF piece of a z/VM OS upgrade? > > Thanks > > * > > _______________________________________________________________________________ > Troy Slaughter | Software Consultant | Mainframe Platform Engineering * > 50 South Lasalle Street, LQ 11SE, Chicago, Illinois, 60603 | Phone > 312-557-6322 | Cell 312-208-3735 | *t...@ntrs.com * <t...@ntrs.com> > Please visit *northerntrust.com* <http://www.northerntrust.com/> > > CONFIDENTIALITY NOTICE: This communication is confidential, may be > privileged and is meant only for the intended recipient. If you are not the > intended recipient, please notify the sender ASAP and delete this message > from your system. > > IRS CIRCULAR 230 NOTICE: To the extent that this message or any attachment > concerns tax matters, it is not intended to be used and cannot be used by a > taxpayer for the purpose of avoiding penalties that may be imposed by law. > For more information about this notice, see * > http://www.northerntrust.com/circular230*<http://www.northerntrust.com/circular230> > > P Please consider the environment before printing this e-mail. > > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
<<image/jpeg>>
