On Thu, 29 Jun 2006 06:27:08 -0500, Tom Marchant <[EMAIL PROTECTED]> wrote: > >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. >>
I never mentioned risk, just policy / preference. >>Not much different than how we manage sysres rollouts from a pool. >>Do you change the sysres name every time you clone? >> >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. > What about the DR and internal backup/recovery implications? Wasn't it a pain to constantly add / change backups etc. everytime you applied a PTF or maintenance and cloned a new sysres or perhaps multiple sysres volumes? Not to mention cleanup / reinit of obsolete volumes. I know those 2 things were really disliked by our DASD group. 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
