On Tue, 11 Jan 2011 00:22:27 -0600, Brian Westerman <[email protected]> wrote:
> There seems to be a lot of chance for things to go wrong, and with all of >the other issues involved in a migration, making it more complex, for me, is >not a "good thing". I just wanted to add one more point related to this: At my largest client, there are 10 different sysplexes (including sandboxes) that I would have to duplicate this effort on. The largest ones have dozens of user catalogs that would have to be connected and aliases defined to use a new MCAT. No big deal really, that's a one time effort. But with hundreds of userids / aliases that could be added / removed on any given day, you would have to wait until migration time in order to perform that activity. Other catalogs / aliases apply too here in this large environment, but this would be the biggest example. Talk about a chance to miss something! Do you "re-synch" all the aliases in your new master catalog on the day of migration each time? Or just export the usercats and go through the process that you originally did to import / define aliases for all catalogs? Or do you have a bullet proof process that adds aliases to both MCATs for some period of time? Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- 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
