We've got an odd problem, or so it seems -- we have about 4 or 5 printers on the network that have been configured for use from our HP (using NBspool).  When one of the printers "has a problem", it appears to be stopping the printouts on the others.  Our sysadmin swears up and down that he has these configured "in diffferent queues" so that this sort of problem should not occur, yet I have irrefutable evidence that it still happens.

First off, does this sound at all familiar?

Secondly, what can I do to verify he really has [correctly] configured these "in different queues"?

One thing that bugs me about this whole thing is that it appears that all of the printers are "LDEV 101":

979/CORE/PUB%showdev a2
 LDEV     AVAIL         OWNERSHIP         VOLID         DEN   ASSOCIATION

  101     SPOOLED
979/CORE/PUB%showdev a4
 LDEV     AVAIL         OWNERSHIP         VOLID         DEN   ASSOCIATION

  101     SPOOLED
979/CORE/PUB%showdev a6
 LDEV     AVAIL         OWNERSHIP         VOLID         DEN   ASSOCIATION

  101     SPOOLED
979/CORE/PUB%showdev a8
 LDEV     AVAIL         OWNERSHIP         VOLID         DEN   ASSOCIATION

  101     SPOOLED
979/CORE/PUB%

Printer "A2", of course, tends to be the culprit -- I think it actually had a "toner low" alarm, and that stopped "everything".  :SHOWOUT JOB=@J showed one file ACTIVE on A2, and everything else as READY.  Pressing buttons at random(*) until it went offline/online unjammed things and the remaining printers jumped to life and printed some 15-20 documents each that were waiting.

Tom

(*) the printer is on a shelf underneath some cupboards, and the display is [naturally] totally inaccesable, along with the lables above each button -- I just pressed each one in turn until the flashing LED went away...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *