DIGITAL PrintServer printers are network printers. They require HP DECnet or DECnet-Plus, HP TCP/IP Services for OpenVMS, Process Software MultiNet for OpenVMS or Process Software TCPware for OpenVMS software to be running on the OpenVMS systems where the DECprint Supervisor software is running.

The following procedures allow users to access PrintServer printers on TCP/IP and DECnet networks.

2.2.1 Defining PrintServer TCP/IP Network Nodes

Before you can communicate with your DIGITAL PrintServer printer via TCP/IP, you must assign an IP address to it. You may also associate a name with the address.

Refer to the PrintServer documentation for information on setting the printer's IP address. Refer to HP TCP/IP Services for OpenVMS, Process Software MultiNet for OpenVMS or Process Software TCPware for OpenVMS documentation for information on configuring your OpenVMS system's TCP/IP environment.

2.2.2 Defining PrintServer DECnet Network Nodes

Before you can communicate with your DIGITAL PrintServer printer via DECnet, you must assign a DECnet address to it. You may also associate a name with the address.

Refer to the PrintServer documentation for information on setting the printer's DECnet address.

To associate a DECnet node name name with the printer's DECnet address, use the NCP command if you are running DECnet Phase IV software, or the DECNET_REGISTER command if you are running DECnet-Plus (formerly DECnet/OSI) software. Refer to the DECnet documentation for more information about node names and these commands.

2.2.3 Deleting the PrintServer Client Startup File

An existing LPS$STARTUP.COM file, if any, is no longer used and is not compatible with DECprint Supervisor. Delete this file after you edit DCPS$STARTUP.COM. To delete this file, follow this procedure:

1. Stop existing print queues with the STOP/QUEUE/RESET command.
2. Delete existing PrintServer print queues.
3. Add new print queues to DCPS$STARTUP.COM for PrintServer printers.
4. If you have any customized definitions in the LPS$STARTUP.COM file, copy the changes into SYS$STARTUP:DCPS$STARTUP.COM.
5. Edit SYS$MANAGER:SYSTARTUP_VMS.COM, removing the reference to SYS$MANAGER:LPS$STARTUP.COM.
6. Delete LPS$STARTUP.COM. You can delete this and other files that are no longer needed for PrintServer printing using the following command file: SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]DCPS$DELETE-LPS-CLIENT.COM

This chapter explains how to start up the printing system and test the printer.

If this is a new installation, you can use the startup template file to help you set up your queues. Copy the printer startup template file as follows:

$ COPY SYS$COMMON:[SYS$STARTUP]DCPS$STARTUP.TEMPLATE - $_ SYS$COMMON:[SYS$STARTUP].COM

3.2 If You Are Upgrading From DECprint Printing Services Software (CPS)

DECprint Printing Services (CPS) is the predecessor software to DECprint Supervisor (DCPS). If you are upgrading from CPS to DCPS, see Section D.2 for more information.

3.3 Setting Up Execution Queues

You must create an execution queue for each PostScript printer. Execution queues schedule jobs for processing and deliver the print jobs to a printer. An execution queue is associated with a particular printer.

When you create an execution queue, you supply information about the queue, including its name and default parameters. Example 3-1 shows creation of an execution queue for a raw TCP/IP printer. Example 3-2 shows creation of an execution queue for a PrintServer printer. These commands are placed in DCPS$STARTUP.COM.

Example 3-1 Creation of an Execution Queue Entry for a Raw TCP/IP Printer

$ IF .NOT. SETUP_MODE THEN @SYS$STARTUP:DCPS$EXECUTION_QUEUE - 2UP - ! P1 - Execution queue name "IP_RAWTCP/lnm40.my.com" - ! P2 - Interconnect protocol/device name DCPS_LIB - ! P3 - Logical name for library(ies) "NUMBER_UP=2" - ! P4 - Default queue parameters "/DEFAULT=(FLAG,FORM=MYFORM)" - ! P5 - Default queue qualifiers "" - ! P6 - Communication speed (serial only) "" - ! P7 - Device characteristics "" ! P8 - Verify on/off

This queue is called 2UP and uses raw TCP/IP to the printer called lnm40.my.com. Jobs printed to this queue print two pages to a sheet, with a flag page and include the code in the form MYFORM.

Example 3-2 Creation of an Execution Queue Entry for a PrintServer Printer

$ IF .NOT. SETUP_MODE THEN @SYS$STARTUP:DCPS$EXECUTION_QUEUE - LPS20$BULL09 - ! P1 - Execution queue name "DECNET/BULL09" - ! P2 - Interconnect protocol/device name DCPS_LIB - ! P3 - Logical name for library(ies) "SIDES=2" - ! P4 - Default queue parameters "" - ! P5 - Default queue qualifiers "" - ! P6 - Communication speed (serial only) "" - ! P7 - Device characteristics "" ! P8 - Verify on/off

This queue is called LPS20$BULL09 and uses DECnet to a PrintServer printer called BULL09. Jobs printed to this queue print in duplex.

Example 3-3 Creation of an Autostart Queue Entry for a Raw TCP/IP Printer

$ IF .NOT. SETUP_MODE THEN @SYS$STARTUP:DCPS$EXECUTION_QUEUE - HP9000_RAW - ! P1 (FOO,BAR)::"IP_RawTCP/hp9000.lkg.dec.com" - ! P2 DCPS_LIB - ! P3 "SIDES=2" - ! P4 "/SEPARATE=(NOBURST,FLAG)" - ! P5 "" - ! P6 "" - ! P7 "" ! P8

This queue is called HP900_RAW and uses raw TCP/IP to the printer called hp9000.lkg.dec.com. The queue is set to autostart on nodes FOO and BAR. Jobs printed to this queue print in duplex and with a flag page but no burst page.

The following sections describe each item of information you need to supply to DCPS$EXECUTION_QUEUE.COM, as outlined in Table 3-1.

Table 3-1 Parameter Values for Execution Queues

Parameter	Value
P1 (required)	Name of the execution queue
P2 (required)	Printer device description, including some or all of the following:
	Node name if in an OpenVMS Cluster and you want to specify the system on which the DCPS queue is to be run
	Interconnect protocol
	Port number for raw TCP/IP printers
	AppleTalk zone for AppleTalk printers and zone name is required
	AppleTalk printer type for AppleTalk printers and printer type is required
P3 (required)	Logical name pointing to device control library(ies)
P4 (optional)	Default queue parameters
P5 (optional)	Default queue qualifiers
P6 (optional)	Communication speed (for directly-connected serial devices only)
P7 (optional)	Device characteristics
P8 (optional)	Verification setting for debugging

3.3.1 Supplying the Name of the Execution Queue (P1)

An execution queue name can have 1-31 characters, including uppercase and lowercase alphabetical characters, digits, the dollar sign ($), and the underscore character (_). The queue name must include at least one alphabetical character and cannot have intervening spaces.

3.3.2 Supplying the Printer Device Name (P2)

The printer device name specifies the interconnect and device used to access the printer, and the VMScluster member node on which it resides.

If the OpenVMS system is not a member of a VMScluster, specify the P2 parameter in the following format:

"interconnect/interconnect_specific_device_address"

If the system is a member of a VMScluster, and you want the queue to run on a particular system in the cluster, specify the P2 parameter in the following format:

node::"interconnect/interconnect_specific_device_address"

If the system is a member of a VMScluster, and you want the queue to be an autostart queue and run on one or more systems in the cluster, specify the P2 parameter in the following format:

AUTOSTART_ON=(nodelist)::"interconnect/interconnect_specific_device_address"

where:

• node is the name of the VMScluster member on which the queue executes.
• nodelist contains the name(s) of the cluster members on which the queue executes. The node list should be either one node name, or more than one node name, separated by commas.
• interconnect specifies the interconnect type. You can specify one of the following:

  For ...	Specify ...	See ...
  Printers that connect with raw TCP/IP sockets	IP_RawTCP	Section 3.3.2.1
  Printers that connect directly or with LAT	serial	Section 3.3.2.2
  PrintServer printers that connect with TCP/IP using the CPAP protocol and TCP/IP	IP_CPAP	Section 3.3.2.4
  PrintServer printers that connect with DECnet using the CPAP protocol and DECnet	DECnet	Section 3.3.2.3
  Printers that connect with EtherTalk and LocalTalk protocols	AppleTalk	Section 3.3.2.5

• interconnect_specific_device_address is the actual address of the printer.

Please note the following details concerning autostart:

• The same procotol and device is used on all nodes. You must ensure the printer device is available on any node specified in the autostart list.
• DCPS does not check the node name(s) you specify to determine if it is an existing node name. Be sure to specify the node name correctly.
• You must ensure that DCPS is installed and configured on any node specified in the autostart list.
• DCPS autostart queues are activated for autostart when DCPS$STARTUP is run, unless it is being run in setup mode. (See Section 3.4 for more information about running the DCPS startup procedure in setup mode.)
• AUTOSTART_ON may be abbreviated as AUTO.
• Do not use double colons (::) when specifying nodes in the autostart list. A double colon must be used to separate the list of autostart nodes and the rest of the P2 parameter.

There are other printer protocols that layer upon TCP/IP, including CPAP (Common Printer Access Protocol), LPD, and Telnet. DCPS uses CPAP to communicate with DIGITAL PrintServer printers. DCPS does not use LPD or Telnet.

To communicate with your printer using raw TCP/IP, the NIC, print server or terminal server that you use to connect your printer to the network must provide a raw TCP/IP port. Further, this raw TCP/IP port must support bidirectional communication between the printer and your OpenVMS system. DCPS does not work with unidirectional ports, such as those found on the NICs for the DEClaser 3500 and 5100 printers, the RapidPrint 200 and 500, and HP JetDirect cards that interface with the printer via its XIO (versus MIO) slot.

Enter the device information in the following format:

"IP_RAWTCP/address:port"

where:

address is the IP address of your NIC, print server, or terminal server in either a named or numeric format.

port is the number of the raw TCP port for your network device. Check the documentation for your NIC, print server, or terminal server to determine what number to use. Table 3-2 shows the port numbers for some commonly-used devices. If no port number is specified, 9100 is used.

Table 3-2 Raw TCP/IP Port Numbers

	20nn	DECserver terminal servers, where "nn" is the physical port number
	2501	DIGITAL LN17ps and DIGITAL Laser Printer LN17+ps
		Emulex NICs
	3001	DIGITAL Laser Printer LN15 and LN15+
		DIGITAL RapidPrint 500 print server
	6869	Compaq Laser Printer LNC02
		DIGITAL Laser Printer LN20, LN40 and LNC02
	9100	Compaq Laser Printer LN16, LN32 and LNM40
		GENICOM Intelliprint mL, LN and microLaser printers
		GENICOM RapidPrint MPS100 print server
		HP LaserJet printers
		IBM InfoPrint printers
		Lexmark C, Optra, S, Optra T, T and W series printers
		Tektronix Phaser printers
		Xerox DocuPrint N printers
		HP JetDirect, Lexmark and XCD print servers

For example, a raw TCP/IP printer could be specified by any of the following:

"IP_RAWTCP/ln40.my.org:6869" "IP_RAWTCP/8.9.10.11:9100" "IP_RAWTCP/hp4300.lkg.dec.com"

Use the following format for serial printers:

If Your Serial Printer is On...	Use This Format ...	Where ...
A local serial line	"SERIAL/T xyn"	x is the printer type code, y is the controller name, and n is the host system unit number.
A LAT port	"SERIAL/LTA n"	n is the host system unit number.

Enter the device information in the following format:

"IP_CPAP/address"

where address is the IP address of your DIGITAL PrintServer printer in either a named or numeric format.

For example, a PrintServer TCP/IP node could be specified by either of the following:

"IP_CPAP/garmnd.dsg.dec.com" "IP_CPAP/16.128.144.11"

3.3.2.4 If Your PrintServer Printer Is Part of a DECnet Network

Enter the device information in the following format:

"DECNET/nodename"

where nodename is the DECnet node name of your DIGITAL PrintServer printer.

For example, a PrintServer DECnet node could be specified by:

"DECNET/GARMND"

3.3.2.5 If Your Printer Is Part of an AppleTalk Network

You can include printers in your printing system that are connected to an AppleTalk network. To make an AppleTalk printer a network sharable device, the PATHWORKS for OpenVMS (Macintosh) software must be running on the same node that is running the DCPS queue.

Enter the device information in the following format:

"APPLETALK/printername@zone@type"

where:

• printername is the AppleTalk node name assigned to the printer. This is the PostScript printer name. This value is required.
• zone is the zone that includes the printer. This value is optional. The default is the AppleTalk zone for the network segment of the OpenVMS system on which the print queue is running.
• type describes the printer's accessibility. This value is optional. Generally, the type is LaserWriter .

When only printername is required, the information provided for P2 would be just "APPLETALK/printername" .

For example, an AppleTalk printer could be specified by any of the following:

"APPLETALK/Paul's Printer" "APPLETALK/Paul's Printer@MRO" "APPLETALK/Paul's Printer@MRO@LaserWriter"