On Wed, 28 Jun 2006 15:38:45 -0500, Mark Zelden <[EMAIL PROTECTED]> wrote:
>On Wed, 28 Jun 2006 15:23:31 -0500, Tom Marchant <[EMAIL PROTECTED]> >wrote: > >>I would have called them something else. Maybe SYSIODF, and created a >>user catalog on the IODF volume with aliases in all the master catalogs >>pointing to that catalog. >> > >I might have, but we merged into the Farmers data center where they >already did it the way we are doing it now and they had a policy >about not sharing catalogs between sysplexes. As I said, using >different names each time (which we did prior to consolidation) >didn't buy us much anyway other than knowing what was current >by looking at the name. IMHO, there's no more risk in using a shared catalog for the IODFs than just sharing the IODFs themselves. I would NOT use that catalog for anything else. > >Not much different than how we manage sysres rollouts from a pool. >Do you change the sysres name every time you clone? We actually >had one environment that did that when it was consolidated into >our data center. Thank g-d we only got up to the letter "O" before >we upgraded their OS and used our existing methodolgy for cloning. >We almost ran out of letters. :-) > I'm not running the show any more, but when I was, that's exactly what I did. I would create a new target and distribution zone set as needed and destroy them when they were no longer needed. I had established different naming standards, but had I just used one letter, there would have been no problem following Z with A. Tom Marchant ---------------------------------------------------------------------- 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
