Donna Garverick wrote:

> using just native mpe network printing, is there a way to
> ensure (or at least better ensure) that a print file has
> actually printed before the spoolfile is deleted?  as i
> understand it, as soon as the mpe system senses(?) the last
> byte has gone, the spoolfile is purged.  the subtle(?) point
> is -- some portion of the print file probably hasn't made it
> onto paper before the file is deleted.  also, no buffering
> occurs on external jet directs, right?                 - d

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.

Jeff Kell <[log in to unmask]>