Paul Gilmartin wrote:

>Often, after finishing a series of tests, I have several dozen data sets to 
>delete.  Actually, I'm careless; often I don't delete them until the next time 
>I want to run similar tests, by which time most are migrated.

Others made good suggestions, but I believe my suggestion could perhaps the 
best for you:

Define a management class to expire your dsn after x days and let SMS have fun 
ala genocide ;-D :

CDS Name  . . . . . . . : ACTIVE
Management Class Name . : MCDAYS04

Description  : EXPIRE DATASETS 4 DAYS. NO BACKUP.
               UNUSED SPACE NOT RELEASED.

Expiration Attributes
  Expire after Days Non-usage  . : NOLIMIT
  Expire after Date/Days . . . . : 4
  Retention Limit  . . . . . . . : NOLIMIT


>o Use TSO DELETE in an IKJEFT* step, possibly in an EXEC.

Not too bad, but you must remember to submit it or have it submitted 
automagically.


>o Type D in front of each on a DSLIST menu. 

Why? Use //D before first DSN and // at last one in =3.4 list. Turn off 
confirmation before that or just at the first DSN.


> And I must  remember to omit the .DATA and .INDEX members 

Use Exclude in =3.4 to drop those .DATA and .INDEX lines and do your //D and //.


>You've probably guessed I'm impatient; when I do get around to cleaning up, I 
>want it to be over so I can start my tests.

See above my SMS comment.


>    while DSN in ..., do ( _BPX_SHAREAS=NO some-rexx-exec address TSO 'DELETE' 
> DSN  ) & done

Not bad, could work if you can scan/filter your DSN list.


>... I might need to pace it lest I exceed PROC_MAX.  Too bizarre? Anything 
>else wrong with it?  Would I gain nothing because of catalog single-threading? 
> Any other ideas?

Create an unload RACF IRRADU00 on your ACCESS of dataset. Run up a REXX to scan 
for and issue DEL for your datasets. Easy. Should take some hours on practise 
datasets just to be safe. Easy to delete wrong datasets if you're not careful.

Have fun with your delete journey! ;-D

Groete / Greetings
Elardus Engelbrecht

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to