Having just implemented this --- Neil's answers were correct.

Each JetDirect device connected to a Laserjet must have an IP address
(subnet mask and gateway, if needed), and on the 3000 side, must be
associated with an LDEV.

In IOCONFIG or SYSGEN, Add the device:

   AD <ldev> PATH=NONE; ID=HPTCPJD; CLASS=<classname>

NETLP is also added as a class by default.

The NPCONFIG.PUB.SYS file as shown below in Neil's post is generally
correct.  This would be good if all Laserjet's were the same.  You can
define each printer with different parameters as well, especially if they
are different types (each has differing capabilities).

Once these two things are in place, do a STARTSPOOL and it's off and
running.  Any changes require changes to the configuration, then a
STOPSPOOL and a STARTSPOOL.

(Hey, once you get it down --- it's a snap! :-)

Best,
Joe
----------------------------------------------------------------------
Joe Geiser
CSI Business Solutions
140 Bristol-Oxford Valley Road, Suite 102
Langhorne, PA 19047-3083
Toll Free (US/Canada): (888) 956-9812
[log in to unmask] (at work)
[log in to unmask] (at play)
----------------------------------------------------------------------

----------
> From: Neil Harvey <[log in to unmask]>
> To: [log in to unmask]
> Subject: Re: Network printing basic question
> Date: Friday, March 07, 1997 2:45 AM
>
> In fact, as I understand it, you MUST nail the printer down to a port.
>
> here is our npconfig.pub.sys file:--
>
> global (setup_file = LJ5SISET.HPENV.SYS         #LaserJet 5Si
>         message_interval = 60                   #Repeat msgs every 60 se
>         banner_header = FALSE                   #no banner
>         banner_trailer = FALSE                  #no banner
>         pjl_supported = TRUE                    #full PJL
>         jam_recovery = TRUE                     #recover from paper jams
>         )
>
> 501  (network_address = 172.23.160.1)
> 502  (network_address = 172.23.160.2)
> 503  (network_address = 172.23.160.3)
> 504  (network_address = 172.23.160.4)
> 505  (network_address = 172.23.160.5)
> 506  (network_address = 172.23.160.6)
>
> and here is a showdev of 501
>
>  LDEV     AVAIL         OWNERSHIP         VOLID         DEN
> ASSOCIATION
>
>   501     SPOOLED       SPOOLER OUT
>
> and here is the sysgen ld:-
>
>      io> ld 501
>  LDEV:   501  DEVNAME:                    OUTDEV:        0   MODE:
> OS
>    ID: HPTCPJD                            RSIZE:        66   DEVTYPE: PP
>
>  PATH: NONE                               MPETYPE:      32   MPESUBTYPE:
> 0
> CLASS: LP       NETLP    LASER501
>
>
>
>
> So we can do:-
>
> :file lp;dev=501;env=letter.env
> print asdas;*lp
>
> or we can do:-
>
> :file lp;dev=LASER501
> l lp xln
>
> etc. etc.
>
> Works REALLY well for us, and we can add printers without a reboot!
>
> Regards
>
> Neil Harvey
>
>
>
> > -----Original Message-----
> > From: HP-3000 Systems Discussion [SMTP:[log in to unmask]] On
> > Behalf Of John Park
> > Sent: 07 March 1997 05:20
> > To:   [log in to unmask]
> > Subject:      Network printing basic question
> >
> > With network printing under 5.5 is it possible to nail a network
> > printer to an LDEV?  Would it then be possible to do something like:
> >
> > !FILE DEPTLJ;DEV=201
> > !FCOPY FROM=DISCFILE;TO=*201
> >
> > and have the discfile print on the network printer?
> >
> > Also, would an FOPEN of a port within an application work on a network
> > printer?
> >
> > Thanks in advance for your answers/advice.
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > John Park                                     'Everything works,
> > Corvallis, Oregon                                if you let it.'
> > [log in to unmask]                                      -Meatloaf