Subject: | |
From: | |
Reply To: | |
Date: | Wed, 23 Aug 2000 11:00:42 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
hi all!
before i answer the folks asking me questions...i thought
i'd check here to make sure i'm thinking right.
for a small-ish collection of our xl stores, we've enabled
network printing. in each case, the stores are connecting
to a remote laser printer (non-hp) via an external jet
direct. so far, things have been going well.
at some point in the recent past, there was an incident
where data was lost -- which of course has folks worried
that the sky is falling <sigh>. i suspect that the users
(at the printer's site) powered off the printer...which
flushed it's buffer and well duh, yes data's going to be
lost. soooo....
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
--
Donna Garverick Sr. System Programmer
925-210-6631 [log in to unmask]
>>>MY opinions, not Longs Drug Stores'<<<
|
|
|