Are you using DFDSS to restore your files? If so you can use the DELCATE parameter to have DFDSS perform the DELETE NOSCRATCH for you.
On Tue, 12 Dec 2006 18:45:50 -0500, Richards.Bob <[EMAIL PROTECTED]> wrote: >Checkout out the CATSCRUB function of Catalog RecoveryPlus from >Mainstar/Rocket Software: www.mainstar.com > > >Bob Richards > > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On >Behalf Of Harold Zbiegien >Sent: Tuesday, December 12, 2006 6:02 PM >To: [email protected] >Subject: delete noscratch performance at DR > >We have a performance problem I am trying to improve. > >When we do our Disaster recovery tests we wind up do a large amount of >delete noscratch against our user catalogs. We basically uncatalog all >of >our disk datasets leaving just the tape datasets in the catalogs. The >catalogs are restored along with full pack restores of certain volumes. >We >then selectively restore our needed disk datasets, almost always to >different volsers than in production. > >Well we generate the IDCAMS delete noscratch statements in about 20 >seconds, >but then running the acutal IDCAMS deletes takes upwards of 80 minutes >to >uncatalog 92,000 entries from our largest user catalog. We delete them >in >alphabetical order. > >Do you know of anyway I can SPEED up this process?? > >The job runs unconstrained. It pretty much is the only thing running in >the >system, it (CATALOG address space) must be doing a huge amount of IO. > >I though perhaps deleteing things in reverse alphabetical order might >improve things but that is just a wild guess. ---------------------------------------------------------------------- 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
