What Jeff said.  Also, if you really want to be safe.  Instead of releasing
the print jobs immediately, you can create them with an out pri <= the
outfence.  When you print them you can add the ;SPSAVE to the end of the
SPOOLF command.  This will keep the spoolfile in your output queue FOREVER
and you will have to manually delete it.   (Or use MPEX to automate the
task...)

<plug>
If you use a network printing program like netprint, you can set it to print
then move it to a different priority and keep it in the queue.
</plug>  (Don't have a financial interest, but better safe than sorry....)

Mark Wonsil
4M Enterprises, Inc.

Jeff Kell wrote:
> If the jetdirect and printer fully support PJL and SNMP (apply
> appropriate patches, etc) and there are no hitches, then yes.  The
> spooler doesn't consider a "job" to be complete until the last page
> has been placed in the output bin (and yes, it looks for it).  You
> can see evidence of this if you have headers enabled.  The "header"
> is treated as a separate "job" and there is a clear pause as the
> printer waits until the page is fully in the output bin before it
> starts to print the actual spoolfile.
>
> But, if you set pjl_disabled or you have SNMP communications problems,
> all bets are off.  The "page is in the output hopper" feature is a PJL
> thing.