>On Thu, 18 May 2000 15:50:25 -0400, Ramaglia, Jennifer <[log in to unmask]>
<clip>
> >in the BS queue.  I'm wondering if I am even utilizing it correctly...
<clip>

This message is a brief explanation of NP92 and Queues.

There is usually no need for the NP92JOB to run at a single high priority.
There are a number of processes running under this job.  Each printer can
have it's own process running at a configurable priority.  In most cases
you can run the job and all processes in the default job queue.

Problem have been seen on busy systems where the system being printed to
(JD, LPD, whatever), times out.  This can occur when the input buffer of
the receiver fills, NP92 waits on IO, NP92 looses it's place in the queue,
a high priority process keeps NP92 from sending more data until a time-out
on the receiver occurs.

This is where you would set the priority on the printer based process to a
high level. The problem has not been seen to occur where the receiving
system is a computer.  It should only occur where a printer has a smaller
communications buffer than the size of the spool file being sent.

The set of configuration items to AVOID is:
   1) Running the job in a high queue.
   2) Choosing a very short time interval for spool file checking.
   3) A large number of deferred spool files.
   4) No filter or a filter that does not exclude the deferred files.

Change any of these four items and no problems should occur.

Please contact us for help with these configuration settings.

<[log in to unmask]> 800-682-0200

<[log in to unmask]> +41 -41-340 23 20

neal