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
	Queue name for LPD 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 OpenVMS Cluster member node on which it resides.

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

"interconnect/interconnect_specific_device_address"

If the system is a member of an OpenVMS Cluster, 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 an OpenVMS Cluster, 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 OpenVMS Cluster 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 with LPD	IP_LPD	Section 3.3.2.2
  Printers that connect directly or with LAT	serial	Section 3.3.2.3
  PrintServer printers that connect with TCP/IP using the CPAP protocol and TCP/IP	IP_CPAP	Section 3.3.2.5
  PrintServer printers that connect with DECnet using the CPAP protocol and DECnet	DECnet	Section 3.3.2.4
  Printers that connect with EtherTalk and LocalTalk protocols	AppleTalk	Section 3.3.2.6

• 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.

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 Color LaserJet printers
		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
	9101	HP 9085 MFP

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"

Enter the device information in the following format:

"IP_LPD/address:queue-name"

where:

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

queue-name is the name of the internal queue name for your network device. Check the documentation for your printer, NIC, print server or terminal server to determine what name to use, if any. Most printers do not require you to specify an internal queue name, but you must specify a queue name for a remote LPD queue. See Table 3-3 for some printers that require an internal queue name to be specified when creating a queue.

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

"IP_LPD/ln40.my.org" "IP_LPD/8.9.10.11" "IP_LPD/lsr2000.lkg.dec.com:xjprint" "IP_LPD/linuxbox.zko.hp.com:ln03"

Table 3-3 Internal LPD Queue Names

Printer	Internal Queue Name
DIGITAL Colorwriter LSR 2000	xjprint
DIGITAL DEClaser 3500	PORT1
DIGITAL Laser Printer LN17+ps	PASSTHRU
DIGITAL LN17ps	PASSTHRU

If you fail to specify the internal queue name when required or specify the wrong name, your print job will be put on hold and the queue will stop. You will also receive messages similar to the following:

%DCPS-F-LPDTERMINATED, LPD connection abnormally terminated -DCPS-I-JOB_ID, for job S (queue SNOBALL, entry 866) on SNOBALL %%%%%%%%%%% OPCOM 19-SEP-2003 12:12:48.88 %%%%%%%%%%% Message from user SYSTEM on FUNYET Queue SNOBALL: %DCPS-F-LPDTERMINATED, LPD connection abnormally terminated

3.3.2.3 If Your Printer Is On a LAT Network or Directly Connected

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.5 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.6 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"