Oops!  Sorry about the lack of details.  HP213EDP, HP_4SI_BATTERY, etc
     are all printer queues defined on our Novell lan.  When users log into
     the HP, they are asked where they would like to send their printouts.
     If they respond with HP_4SI_BATTERY, for example, a set of file
     equations will be issued, such as FILE REPORT=HP4SIBAT;DEV=LP,1.  The
     correspondence between queue name and legal MPE filename is under the
     control of a text file (shades of Unix).  Meanwhile, a background
     NBSpool job scans for output spool files every minute.  When it comes
     across something that it recognises, such as the report named HP4SIBAT
     from above, it will move it (via NBSpool's gateway) to the appropriate
     Novell queue.
 
     Does this help?
 
     -Bob
     [log in to unmask]
 
 
______________________________ Reply Separator _________________________________
Subject: Re: Re[2]: Pseudo Devices
Author:  Neil Harvey <[log in to unmask]> at Internet
Date:    3/5/96 9:58 AM
 
 
Bob wrote
 
 
     I do something similar here, using the report name instead of
formid.
     Therefore, something like
 
     FILE REPORT=HP213EDP;DEV=LP,1
 
     will be picked up by NBSpool and routed to the requested queue
     (HP213EDP, in this case).  Different report names go to different
     queues (eg, HP414BAT -> HP_4SI_BATTERY, etc).  This also avoids
using
     NMMGR to add printers.
 
But, what is HP213EDP, and how and where is it defined on the HP3000?
And how is it connected to the network.
 
Thanks
 
Neil
[log in to unmask]