Even if you are not on a supported migration path, you can always try to copy the database over and apply the new templates. The worst that will happen is it doesn't work. In that case, you can use the brute force method. Run the RACF DBSYNC freebie comparing your current database to an empty file. It will produce a reasonably complete set of RACF commands to make your new database look like the old one. (Users created in the new database will have default passwords which they must change at first logon.) In any case, the effort should be measured in days, definitely not months.
-----Original Message----- From: Sridhar K Veena [mailto:snip] Sent: Monday, November 19, 2007 10:38 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Question regarding RACF migration. G'day, I want to know from a technical perspective if some one needs to migrate an existing system from an older version of OS (say MVS/ESA, OS/390 etc to Z/Os) what is the impact on RACF?. Would migrating the RACF to a newer version be a big enough Project(like a 6 months to 1 year kind of project)?. Or as in any migration from one version to another, RACF is also automatically handled?. Please advice. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html