Question to the OP - When you are done with the delete noscratch and the dataset restores, are there any catalog entries besides what has been restored? If the answer to the above is NO, then why not start the preocess with empty catalogs? You might be able to bypass the entire delete noscratch step. If the answer to the question is YES, you might want to consider segregating the datasets to be restored into their own catalog(s).
________________________________ <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< - one of our procedures is to DELETE NOSCRATCH thousands of production datasets; catalogue cleanup before dataset restore...this process took hours to execute...might this be related to the CATALOG AUTOTUNE in our 1.7 system? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> A possible way to speed up updates (of any KSDS): - Sort deleted records in descending sequence. - Alter SHAREOPTIONS to (3 2) for the duration of the update (cannot be shared at such time). ---------------------------------------------------------------------- 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
