I would think the need to specify the volser the catalog resides on could be problematic while connecting a catalog to a master.
On Sat, 31 May 2008 00:42:52 +1000, Shane Ginnane <[EMAIL PROTECTED]> wrote: >Quoting "Knutson, Sam" > >> Our storage team is considering no longer allocating ICF USER >> catalogs on dedicated non-SMS volumes moving them into our SMS pool for >> system data sets. >> >> There is some debate here about this here. Do you do this? Do you >> prevent DFHSM from doing backup and migration on ICF catalogs using >> management class? > >My DASD folks and I have a "symbiotic" relationship. >Everything I want as non-SMS goes on non-SMS volumes - resvols, spool, >[m|u]cats, page, sadmp, ... >Other "system" stuff is in a (SMS) system pool. That's the end of my >interference in their lives. > >They do their job, I do mine. Works well. >They probably know it would not be beneficial to stir the pot. > >Shane ... ---------------------------------------------------------------------- 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
