Hi Dave Thank you,
Some thoughts... a. If we have an online application which switches its log datasets every 2 to 3 minutes, how we can manage the disconnect of catalog? Will it lead to an allocation failure? In this situation how we can avoid an allocation failure, what is the solution? b. Repro backup - understood. c. Delete and Define - In this step, is it better to use a new large dataset or delete and define the same as bigger? d. Populate - Is this is done by Import? If not kindly explain. Are steps of Examine and diagnose required? Best regards, Suresh On Tue, May 24, 2016 at 11:32 PM, Gibney, Dave <[email protected]> wrote: > 1. Buy a tool. Dino, or CR+, or .... > Or > 2. At a very quiet time: a. Discconnect the catalog. b. back it up via > repro. c. delete and defining it bigger. d. repopulate. e. import. > And it would be a good idea to IPL here. > > > -----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. > > > > Regards, > > > > Suresh N C > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to > > [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- *SureshNc* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
