This appendix provides some information about OpenVMS logical names that are used by the DECprint Supervisor for OpenVMS software.

Here are some guidelines for using these logical names:

• Any logical whose name begins with "DCPS" is only used by the DECprint Supervisor for OpenVMS software. Other logical names (for example, PSM$ANNOUNCE) may be used by and impact other components of your OpenVMS system.
• You should place your desired definitions for these logical names in DCPS$STARTUP.COM or in something that it invokes. The startup procedure template has comments about how to define some of these.
• Changes to some logical names have an immediate effect, while changes to others take effect only when a queue starts or when a DCPS symbiont process is first created. The ramifications of this are particularly significant if you are using multistreamed DCPS symbiont processes (see Section 3.4.1.2). You should assume that the symbiont reads all logical names only when it is first created, thus requiring you to first stop all queues and then retart them before your changes can take effect.
• You should define the desired logical names in the system table in executive mode (that is, using DEFINE/SYSTEM/EXECUTIVE).
• In a VMScluster environment, you should define the desired logical names on all nodes that utilize the DCPS software. To examine logical names defined by DCPS, you need to look on the node on which the DCPS symbiont process is running.
• Additional logical names may be listed in the Release NotesRelease Notes.

Below is a table of the logical names used by DCPS, their acceptable values, and a brief explanation of what they mean. There are also references to other sections of this document or other documents where you can find more information about the logical names.

Table B-1 DCPS Logical Names

Logical Name	Acceptable Values	Meanings and References
Logical names that provide information to DCPS
DCPS$DEFAULT_TRANSLATOR	<set of translators> 1	System wide default text data type; Section 4.2.2
DCPS_LIB 2	search list	List of DCPS setup libraries and their data types; Section 7.4.2
DCPS$DEVCTL_CACHE	1	Enable system wide device control caching; Section 7.11
DCPS$LAYUP 3	search list	Directory where layup files are stored; Software Installation GuideSoftware Installation Guide
DCPS$MAX_STREAMS	0..32	Number of queues per DCPS symbiont process; Section 3.4.1
DCPS$PURGE_TIME	delta time	Time to wait before purging working set; Section 3.4.4
DCPS$ qn_DEFAULT_TRANSLATOR	<set of translators> 1	Queue specific default text data type; Section 4.2.2
DCPS$ qn_DEVCTL_CACHE	1	Enable queue specific device control caching; Section 7.11
DCPS$ qn_DEVICE_NAME 4	string	Actual device name associated with the queue when name is too long for INITIALIZE/QUEUE/ON qualifier (and SHOW QUEUE/FULL lists "DCPS$" as the device instead); Section 3.3.2
DCPS$ qn_IGNORE_UNKNOWN_USER	1	Disable unknown user error when username not found in UAF; Section 3.4.5
DCPS$ qn_INTERRUPT_WHEN_BUSY	1	Disable wait for serial printers to be "not busy"; Section 3.4.2
DCPS$ qn_NO_SYNC	1	Disable usual synchronization on printers other than PrintServer printers; Section 3.4.3
DCPS$ qn_OLD_ANSI_PAGE_SIZES	1	Use old (pre-V1.1a) vertical spacing for A4 size in ANSI translator; Section 3.4.6
DCPS$ qn_PARAMETER 4	string	Default queue parameters; Section 3.3.4
DCPS$ qn_SEPARATOR_TRAY	number	Tray number to take job burst and flag pages from; Section 6.2.3
DCPS$ qn_STALL_TIME	delta time	Timeout before declaring a printer stalled; Section 5.12
DCPS$ qn_SUPPRESS_JOBTRAILER	1	Disable printing of job trailer; Section 6.2.2
PSM$ANNOUNCE	string	String which prints on separator pages; Section 6.4
Logical names that return information from DCPS
DCPS$ qn_PID		Process ID of DCPS symbiont controlling the queue; Section 5.8
DCPS$ qn_STALLED		Reason for queue being stalled; Section 5.12

You may be able to use the SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]FONT_DOWNLOADER.COM command procedure to list, download, and delete fonts on the optional hard drive on a printer. The procedure is known to work with the DEClaser 5100 and LN17ps printers, and may work with other printers as well.

To use the procedure, invoke it and follow the prompts that it gives you.

This appendix explains the differences between the DECprint Supervisor software and the DECprint Printing Services software, and their ability to coexist. "DCPS" refers to the DECprint Supervisor for OpenVMS product; "CPS" refers to the DECprint Printing Services product.

D.1 DCPS/CPS Coexistence

DCPS software can coexist on the same system with CPS Version 4.0 or Version 4.1 software. The installation of DCPS software does not delete or modify components of CPS software. You may continue to run both products on the same system, or you may migrate the existing queue structure from the CPS product to the DCPS product.

D.2 Printer Support

All file names, logical names, and messages for the DCPS product start with the DCPS$ prefix. This ensures that you can continue to use CPS software to drive some queues, and add the DCPS software to drive others. The default OpenVMS form is DCPS$DEFAULT.

Certain files, however, are considered system resources, and are shared between the DCPS and CPS products, and possibly other products. These shared resources are:

• CPS$ANSI_FONTS.TLB
  This is the library containing downloadable fonts that emulate LN03 or DEClaser font cartridges.
• Data type translators
  The DCPS product installs its translators using the same directory and file name structure that the CPS product used.

Secondary messages (those generated by other facilities such as RMS, and passed along by the DCPS product) retain the code of the facility that originated the message.

D.4 Startup File Converter

The conversion tool, CPS_TO_DCPS_STARTUP.COM, converts the startup file for the CPS software so that it uses the names from the DCPS product. This tool is described in Section 3.2.

The following table lists the CPS_Name and the corresponding DCPS_Name conversions.

CPS_Name	DCPS_Name
CPS$STARTUP	DCPS$STARTUP
CPS$EXECUTION_QUEUE	DCPS$EXECUTION_QUEUE
CPS$REQUIRED	DCPS$REQUIRED
CPS$GENERIC	DCPS$GENERIC
CPS_LIB	DCPS_LIB
CPS$DEVCTL	DCPS$DEVCTL
LPS$ queuename_PARAMETER	DCPS$ queuename_PARAMETER
CPS$ queuename_STALL_TIME	DCPS$ queuename_STALL_TIME
LPS$LAYUP	DCPS$LAYUP
DECprint Printing Services	DECprint Supervisor

The conversion tool does not change queue names or the structure of the queues.

D.5 Eliminating Generic Queues

The DCPS product can scale the logical page image to fit the output sheet if the job provides the following parameters:

PAGE_SIZE=p,SHEET_SIZE=s

Note that p and s are different values.

The job assumes the parameter NUMBER_UP=1. With CPS, it was necessary to explicitly provide a NUMBER_UP parameter in order to trigger page scaling.

D.7 Layup for PS Level 2 Printers & Layup Fixes

The DCPS software layup facility supports PostScript Level 2 operators when connected to printers that implement PostScript Level 2. It also fixes or extends support for several Level 1 operators.

Level 1 PostScript programs produced by Macintosh and PC applications generally print better with the DCPS product than they did with the CPS product. Problems with CorelDraw and Macintosh programs have been fixed.

D.8 Layup Options on PRINT Command Line

With DCPS software, you can provide layup options directly with the LAYUP_DEFINITIONS parameter, or you can record those options in a .LUP file and provide that file name with the parameter. Providing the layup options on the PRINT command makes it possible to pass them with jobs to be printed on another system via the Distributed Queuing Services product. CPS V4.1 software offers only the .LUP file option.

See the User's GuideUser's Guide for information on expressing layup options in a layup definition file or as a PRINT parameter.

D.9 Page Sizes

A6
C
D
7x9
7_envelope
10x14
11x14
PostCard

To select job separator pages from an alternate tray using the DCPS software, define the following system logical:

$ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queuename_SEPARATOR_TRAY number

Note that number is a valid tray number for the printer served by that queue, and is printer-specific. Refer to your printer documentation to obtain the correct value.

The following are the values for Compaq and DIGITAL printers:

Table D-1 Tray Number Values

Printer	Tray	Tray Number	Default	Optional
Compaq Laser Printer LN16
	upper	0	<>
	lower	1		<>
	multipurpose	3		<>
Compaq Laser Printer LN32 and LNM40
	multipurpose	0
	tray 1	1	<>
	tray 2	2
	tray 3	3		<>
	tray 4	4		<>
	tray 5	5		<>
	envelope feeder	6		<>
DEClaser 1150 and 1152
	multipurpose	0	<>
	cassette 1	1		<>
DEClaser 2150 and 2250
	manual feed	0
	lower	1	<>
	upper 2	2		<>
	power envelope feeder	3		<>
DEClaser 3250
	multipurpose	0
	upper	1	<>
	lower	2
	high capacity feeder 3	3
DEClaser 3500
	upper	0	<>
	lower	2		<>
	multipurpose	3
DEClaser 5100
	multipurpose	0
	upper	1	<>
	lower	2		<>
DIGITAL Colorwriter 1000
	upper	0	<>
	lower	1		<>
DIGITAL Colorwriter LSR 2000 and 2000+
	upper	1	<>
	lower	2		<>
DIGITAL Laser Printer LN15 and LN15+
	upper	0	<>
	lower	1		<>
	multipurpose	3		<>
DIGITAL LN17ps and Laser Printer LN17+ps
	main	0	<>
	multipurpose	1
	lower 1	2		<>
	lower 2	3		<>
	envelope feeder	4		<>
DIGITAL Laser Printer LN20
	multipurpose	1
	upper	2	<>
	lower	5		<>
DIGITAL Laser Printer LN40
	upper	1	<>
	middle	2
	lower	3
	LCIT	5		<>
DIGITAL Laser Printer LNC02
	upper	1	<>
	lower	5		<>
DIGITAL PrintServer 17 and 17/600
	upper	1
	lower	2
DIGITAL PrintServer 20, 32, 32plus and 40
	upper	1
	lower	2
	LCIT	3	<>
GENICOM microLaser 170
see Compaq Laser Printer LN16
GENICOM microLaser 210 and LN21
	multipurpose	0
	tray 1	1	<>
	tray 2	2		<>
	tray 3	3		<>
	envelope feeder	6		<>
GENICOM microLaser 280 and LN28
	multipurpose	0
	tray 1	1	<>
	tray 2	2		<>
	tray 3	3		<>
GENICOM microLaser 320 and 401
see Compaq Laser Printer LN32