On Monday 01 May 2006 23:28, Joel C. Ewing wrote: > Several potential problems with the suggested DFDSS approach: > DFDSS will only find datasets on primary volumes - any datasets > migrated to ML1 or ML2 will be ignored and not deleted.
Agreed > Although the indicated job will not actually write any data to the > DUMMY output dataset, the DFDSS DUMP will still incur the overhead of > reading through all data of the datasets being deleted. Are you sure? > The TOL(ENQF) should become a problem (delete failure) when it is time > for the DELETE to occur if any other address space has the dataset > enqueued. TOL(ENQF) is a mistake, it shouldn't have been in John's example > If there are not that many datasets and migration is a possibility, > I would be tempted to look for some BATCH REXX approach with LISTC and > DEL, which would handle migrated datasets. If there were 5K+ datasets > involved, using the Catalog Search Interface to identify the datasets > rather than LISTC would take more work but would be considerably more > efficient. You're pretty much describing the XDELETE exec which is distributed in file 183 of the CBT tape - http://gsf-soft.com/Freeware/ In the same place, you'll find XRENAME to rename data sets "en masse" -- Gilbert Saint-Flour GSF Software http://gsf-soft.com/ mailto:[EMAIL PROTECTED] ---------------------------------------------------------------------- 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
