There really is no generic best practice. Your catalog management should be based on the needs of your particular installation. A data center handling corporate administration is different than a development center generating products for sale which is different than a service bureau with multiple customers who expect zero cross-talk.
The most common rule of thumb I have heard is "limit the master catalog to system datasets." But there are different interpretations of which datasets are really system ones. Some include IBM program products, others don't. Some include vendor products, others don't. Some have a different catalog for each vendor, others have a common one for all vendors. You get to decide. After you have decided how you want to organize your catalogs, the Managing Catalogs manual would be a good place to start. And then people here can assist if you have detailed questions about how to perform some task. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of suresh chacko > Sent: Tuesday, May 24, 2016 12:29 PM > To: [email protected] > Subject: z/OS Master/User catalog dataset re-organization > > 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. > > Kindly share from your expert experience and knowledge. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
