On Wed, 28 Jun 2006 15:23:31 -0500, Tom Marchant <[EMAIL PROTECTED]> wrote:
>On Wed, 28 Jun 2006 09:49:31 -0500, Mark Zelden <[EMAIL PROTECTED]> >wrote: >> >>Then there are still extra steps for copying the IODF. Ours are named >>with a HLQ of SYS1 so they can be cataloged in multiple catalogs. It >>was a "one time" thing to catalog the ones we rotate between. Since >>we maintain them from one sysplex (delete/define), no further action >>is ever required from a catalog point of view. >> >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. 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. :-) Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group mailto: [EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
