RE: spool file status

>If you really want you could (re)release a
>saved spool file and then immediately after
>hold it - that way an already printed spool
>file could end up being in HLD status again.
>
>- So it is possible, but I see very few sane
>reasons for actually doing so in relation to
>normal operations

Sanity notwithstanding, in my meagre experience the number one reason that
this can happen is the 'Oops!  I just released the wrong spooled file!'
syndrome.  As soon as the operator realises she's released the wrong one,
she holds it again.

Addressing the original question, this is more likely to occur if you have a
busy operations staff.  If the output queue you're cleaning up sees little
activity, then SAV status should be plenty good enough.
  --buck