I do this all the time on my 3k, I even give it an extra day, an 8 day
window to be purged.  I utilize MPEX for this, however I found it had a bug
when it was on my 4.0 platform and I cleaned up spool files in two ways:

   CONTINUE
   DELETESPOOLFILE @[log in to unmask]@(SPOOL.READYDATE < TODAY-8)
   CONTINUE
   YESPURGE @.OUT.HPSPOOL(ACCDATE < TODAY-8)

(For reasons of the bug, I used PURGE instead of SPOOLF nnn;DELETE just to
make sure.  The bug could have gone away, when I went to 5.0 or the latest
MPEX update may have fixed it also.  But I kept it in my job stream, just
in case.  Also the reason they hang around so long is we use SPSAVE a lot.)

I also perform another procedure:

   CONTINUE
   DELETESPOOLFILE @[log in to unmask]@(SPOOL.NUMLINES=2)

It gets rid of those pesky "nothing" spool files that get SPSAVED.

----------
From:   Stigers, Gregory - ANDOVER[SMTP:[log in to unmask]]
Sent:   Wednesday, November 27, 1996 8:07 AM
To:     [log in to unmask]
Subject:        Spool file cleanup

Our sys admin boys (I like to call them syssies; they in turn like to
abort my idle sessions. We are a fun-loving group.) are new to the 3K.
We are going to discuss how to handle spool file cleanup; I should
mention that they bought NSD JobTime & JobRescue, with which I am
unfamiliar. I casually mentioned the idea of a self-scheduling job
stream that deletes anything over, say, one week old; I should have
thought before I shot off my mouth that this was on another platform...
I am open to suggestions on any part of this problem: approaches to
spool file cleanup, experience with the NSD line, learning to keep my
mouth shut...