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 | [email protected]
Please visit 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

P Please consider the environment before printing this e-mail.

<<image/jpeg>>

Reply via email to