Hi all, Thanks to all.
Gone through z/OS catalog management reference guide too. Best regards, Suresh On Wed, May 25, 2016 at 6:59 AM, suresh chacko <[email protected]> wrote: > Hi all, > > Thanks to all for the valuable inputs and shares. > > Is it required to organize a planned outage during the user catalog > re-organization or move? If so, how we can avoid an outage during this > activity in an online shop where we have 2 systems of which one is at DR > site on which all the LPARS are spread across and connected with GRS. > > Regards, > Suresh > > > > > > > > On Wed, May 25, 2016 at 12:49 AM, John Eells <[email protected]> wrote: > >> suresh chacko wrote: >> >>> Hello Group, >>> >>> Like to know the best practices in z/OS Catalog dataset management and >>> what >>> all are the steps involved in z/OS catalog dataset re-organization >>> activity. >>> >> <snip> >> >> My view is this: >> >> The master catalog should "never" need to be reorganized. It's nearly >> static compared to user catalogs, and if you have the right stuff in there >> all of it should be cached anyway once the system is up and running. (See >> z/OS DFSMS Managing Catalogs for the recommendations about the content of >> the master catalog.) >> >> User catalogs should be reorganized, *if necessary*, one last time and >> then enabled for CA Reclaim like (nearly) any other KSDS. After that, let >> them manage themselves... >> >> -- >> John Eells >> IBM Poughkeepsie >> [email protected] >> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> > > > > -- > *SureshNc* > -- *SureshNc* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
