I did what the others suggested on the programming front several years ago. Made the "delete" programs generic so they can have parameters passed to them to control all KINDS of spool files.
Additionally, if you have a dumb terminal with a record key, for quick and dirty work, you could record several screens worth of deletes and keep (re)playing the sequence (although I wouldn't want to do that for 8000 !!!! <BG>).
"George M. Sagen" wrote:
Thanks for all the responses. The one that worked the best for my particular issue was to have the user log in and first, do the WRKSPLF command, which listed only his files, then do DLTSPLF *SELECT. I didn't seem to need the additional USER parameter because the user only had access to his own files, but will find it useful when in a scenario where the user logged in has access to all spool files. Makes a good case for going back and reviewing the basics periodically. Turns out there were over 8000 files to delete. Would have worn out the 4 key.Geo.
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact