For example, to configure LDEV 201 as a network printer, enter:
io> ad ldev=201;id=HPTCPJD;path=NONE;class=NETLP To view the device configuration, enter the ld command:
io> ld 201
LDEV: 201 DEVNAME:xxxxx OUTDEV: 0 MODE: OS
ID: HPTCPJD RSIZE: 66 DEVTYPE: PP
PATH: NONE MPETYPE: 32 MPESUBTYPE: 0
Note: Leave the mode of the preconfigured printer set to output spooled (MODE= OS) and the path set to NONE. When the system boots, MPE/iX will try to create a spooler process for the printer. It will fail, however, when it cannot find an address for the device. In this case, failure is appropriate since the printer does not exist.
4. Enter the ‘HOLD’ command to save the modified I/O configuration, and then type ’EXIT’ to leave the I/O configurator.
5. At the SYSGEN prompt, enter the ‘KEEP’ command. It is a good practice to create a backup SLT tape whenever you make changes to SYSGEN.
6. Print the ‘LOG4ONLN.PUB.SYS’ file to inspect your pending changes.
ad 992, none, HPTCPJD;class=netlp
Step Two Create entry in ‘NPCONFIG.PUB.SYS’.
The file NPCONFIG.PUB.SYS is a ASCII flat file that the system manager creates and modifies using a text editor. The purpose of the NPCONFIG file is to supply to the system additional configuration data about network printers that is not defined in SYSGEN. The NPCONFIG configuration file is designed to be extensible.
At a minimum, NPCONFIG must have the following information:
* An LDEV-specific entry for each network printer.
* The printer's network address, which is its numeric IP address or a domain name the spooler can resolve to its IPaddress.
For example, a complete though minimal entry in NPCONFIG for the network printer designated as LDEV 201 might be:
201 (network_address = 192.168.225.10)
Most NPCONFIG files will also have one global entry whose items are applicable to all network printers. This makes it convenient to configure a group of printers that belong to the same "family" since it is unnecessary to repeat identical configuration items for each LDEV entry. (With one exception, setup_file, items found in the LDEV specific entries take precedence over those in the global entry.)
For example, a global entry for a group of LaserJet 4Si printers might look like this:
||global (setup_file = LJ4SISET.HPENV.SYS
|| # LaserJet 4Si setup file.
||message_interval = 60
||# Repeat msgs every >= 60 secs.
||banner_intray = 1
||# Upper tray has colored banner paper.
||banner_trailer = FALSE
||# Only need a header page.
||pjl_supported = TRUE
||# LJ4Si is a full PJL device.
|| jam_recovery = TRUE)
||# Reprints jammed pages by itself.