HP DECprint Supervisor (DCPS) for OpenVMS

Software Installation Guide

May 2009

This guide describes how to install the DECprint Supervisor software.

Revision/Update Information: This manual supersedes the Software Installation Guide V2.5.

Software Version: HP DECprint Supervisor (DCPS) for OpenVMS, Version 2.7

Operating System: OpenVMS I64 Version 8.2-1, 8.3 or 8.3-1H1
OpenVMS Alpha Version 6.2, 7.3-2, 8.2 or 8.3
OpenVMS VAX Version 5.5-2, 6.2 or 7.3

Hewlett-Packard Company Palo Alto, California

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Adobe, Adobe PostScript 3 and PostScript are trademarks of Adobe Systems Incorporated.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

UNIX is a registered trademark of The Open Group.

Contents Index

Preface

Intended Audience

This manual is for system managers responsible for installing the DECprint Supervisor (DCPS) for OpenVMS printing software. To install the printing software, it is necessary to have some experience with:

OpenVMS DCL command language and system management procedures
Procedures and commands in the System Manager's GuideSystem Manager's Guide
PCSI utility for installing OpenVMS software
Network addressing and protocols at your site

Document Structure

This manual contains the following chapters and appendices:

Chapter 1 describes what must be done before installing the software.
Chapter 2 describes how to install the software with PCSI.
Appendix A shows a sample installation.
Appendix B describes how to install the software with VMSINSTAL. Appendix C lists the files installed by DCPS on your system.

**Table 1 DECprint Supervisor Documentation**
Software Installation Guide	Describes how to install DCPS.
System Manager's Guide	Describes how system managers, data center operators and application programmers can create and manage DCPS print queues and solve printing problems.
User's Guide	Describes how to use DCPS to print to PostScript® printers.
Software Product Description (SPD 44.15.xx)	Contains the full list of printers supported by DCPS and additional information about the features and requirements of DCPS V2.7.

Reader's Comments

HP welcomes your comments on this manual. Please send comments to:

openvmsdoc@hp.com

How to Order Additional Documentation

For information about how to order additional documentation, see the HP OpenVMS Systems Documentation Ordering page:

http://www.hp.com/go/openvms/doc/order

Conventions

The following conventions may be used in this manual:

Ctrl/ x A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.

PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button.

[Return] In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.)
In the HTML version of this document, this convention appears as brackets, rather than a box.

... A horizontal ellipsis in examples indicates one of the following possibilities:

Additional optional arguments in a statement have been omitted.
The preceding item or items can be repeated one or more times.
Additional parameters, values, or other information can be entered.

.
.
. A vertical ellipsis indicates the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.

( ) In command format descriptions, parentheses indicate that you must enclose choices in parentheses if you specify more than one.

[ ] In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement.

| In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.

{ } In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line.

bold type Bold type represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason.

italic type Italic type indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where dd represents the predefined code for the device type).

Example This typeface indicates code examples, command examples, and interactive screen displays. In text, this type also identifies URLs, UNIX commands and pathnames, PC-based commands and folders and certain elements of the C programming language.

UPPERCASE TYPE Uppercase type indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.

- A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.

numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes---binary, octal, or hexadecimal---are explicitly indicated.

Chapter 1
Before Installing the Software

1.1 Operating System Version

The following are the supported versions of the OpenVMS operating system:

OpenVMS I64 V8.2-1, V8.3 and V8.3-1H1
OpenVMS Alpha V6.2^*, V7.3-2^*, V8.2 and V8.3
OpenVMS VAX V5.5-2^*, V6.2^* and V7.3

For a current list of supported OpenVMS versions, visit the following address:

http://h71000.www7.hp.com/openvms/openvms_supportchart.html

Although the DCPS V2.7 PCSI kit will install and run on OpenVMS V6.2 and later, and the DCPS V2.7 VMSINSTAL kit will install and run on OpenVMS VAX V5.5-2 and later, customers running OpenVMS versions that are not supported do so at their own risk.

If you are running an older version of OpenVMS under a Prior Version support contract, such as OpenVMS VAX V5.5-2, contact HP for a DCPS VMSINSTAL kit. (See Section 1.3.2 for more information about PCSI software requirements.)

Note

^* With Prior Version Support or Extended Engineering Support

1.2 Disk Space

Depending on whether DCPS is installed on an I64, Alpha or VAX processor, disk space requirements may vary. Table 1-1 lists the disk space requirements.

Table 1-1 Disk Space Requirements
Disk space required for ... I64 system Alpha system VAX system

Installation 11,000 blocks 7,700 blocks 7,200 blocks

Permanent use 10,500 blocks 7,200 blocks 6,700 blocks

**Table 1-1 Disk Space Requirements**
Disk space required for ...	I64 system	Alpha system	VAX system
Installation	11,000 blocks	7,700 blocks	7,200 blocks
Permanent use	10,500 blocks	7,200 blocks	6,700 blocks

These disk space requirements are approximate, and depend on your system environment, disk cluster size, configuration and software options.

1.3 Related Software

DECprint Supervisor works with other software to create a fully functional printing system. Before installing DECprint Supervisor, make sure the other application and printing software is compatible.

The following sections detail the software you need. Refer to the DECprint Supervisor Software Product Description (SPD) for specific version requirements.

1.3.1 USB Patch kits

You must install one of the following USB patch kits before installing DCPS V2.7 or later:

Table 1-2 USB Patch Kits
OpenVMS Version Patch Kit

OpenVMS I64 V8.3 VMS83I_USB-V0200

OpenVMS I64 V8.3-1H1 VMS831H1I_USB-V0100

OpenVMS Alpha V8.3 VMS83A_USB-V0100

**Table 1-2 USB Patch Kits**
OpenVMS Version	Patch Kit
OpenVMS I64 V8.3	VMS83I_USB-V0200
OpenVMS I64 V8.3-1H1	VMS831H1I_USB-V0100
OpenVMS Alpha V8.3	VMS83A_USB-V0100

You can obtain these patch kits (or an update to them):

From an HP Customer Support Center
From the HP IT Resource Center (ITRC) at the following URL:
http://www.itrc.hp.com

These patch kits are expected to be included in a future version of OpenVMS.

1.3.2 PCSI Utility

DCPS is installed with the PCSI utility via the PRODUCT command. For a complete description of the PCSI utility and the use of the PRODUCT command, refer to the HP OpenVMS System Manager's Manual and the HP OpenVMS System Management Utilities Reference Manual or online help.

If you are running older versions of OpenVMS, you may be required to install a PCSI patch kit before installing DCPS. See Table 1-3 to determine whether you need to install a PCSI patch. The patch will upgrade PCSI on your system.

Table 1-3 PCSI Patch Kits
OpenVMS Version PCSI Patch Kit

I64 V8.2 and later not required

Alpha V6.2 through V7.1-2 DEC-AXPVMS-VMS62TO71U2_PCSI-V0200--4

Alpha V7.2 and later not required

VAX V5.5-2 not available; contact HP for a DCPS VMSINSTAL kit

VAX V6.2 through V7.1 DEC-VAXVMS-VMS62TO71_PCSI-V0200--4

VAX V7.2 DEC-VAXVMS-VMS72_PCSI-V0101--4

VAX V7.3 not required

**Table 1-3 PCSI Patch Kits**
OpenVMS Version	PCSI Patch Kit
I64 V8.2 and later	not required
Alpha V6.2 through V7.1-2	DEC-AXPVMS-VMS62TO71U2_PCSI-V0200--4
Alpha V7.2 and later	not required
VAX V5.5-2	not available; contact HP for a DCPS VMSINSTAL kit
VAX V6.2 through V7.1	DEC-VAXVMS-VMS62TO71_PCSI-V0200--4
VAX V7.2	DEC-VAXVMS-VMS72_PCSI-V0101--4
VAX V7.3	not required

You can obtain these patch kits:

From an HP Customer Support Center
From the HP IT Resource Center (ITRC) at http://www.itrc.hp.com

1.3.3 TCP/IP Networks

TCP/IP connections to PrintServer printers using Common Printer Access Protocol (CPAP), and connections to other printers using the Raw TCP/IP socket or LPD protocols, require one of the following:

HP TCP/IP Services for OpenVMS
Process Software MultiNet for OpenVMS
Process Software TCPware for OpenVMS

1.3.4 C Run-Time Library

DCPS requires that the C run-time library is installed on your system. This library is included with the OpenVMS operating system starting with OpenVMS V6.1, and in the DEC C/C++ Run-Time Components kit. Therefore:

To run on any OpenVMS V6.1 or later system, no installation of the DEC C Run-Time Library is required.
To run on OpenVMS VAX V5.5-2 systems, the DEC C/C++ Run-Time Components kit must be installed before installing DCPS.
To determine if the DEC C run-time library exists on your system, check for the existence of the file SYS$STARTUP:CRT$STARTUP.COM. If this file exists, the DEC C/C++ Run-Time Components kit has already been installed. If it does not, you must install the DEC C/C++ Run-Time Components kit before installing DECprint Supervisor.
The DEC C/C++ Run-Time Components kit is included on the OpenVMS VAX Software Product Library CD-ROM in the Compaq C directory. The saveset name is AACRT060.A. Please refer to the DEC C/C++ Run-Time Components documentation for information about installing the kit, starting with Read Before Installing or Using DEC C/C++ Run-Time Components Version 6.0 for OpenVMS VAX Systems.

1.3.5 PrintServer Software

To print to a DIGITAL PrintServer printer, the printing environment must contain a supporting host system running the PrintServer software product.

1.3.6 AppleTalk Networks

One of the network protocols used by DCPS is AppleTalk, provided on OpenVMS Alpha and VAX systems by the layered product PATHWORKS for OpenVMS (Macintosh). Although this product is retired and no longer supported, DCPS has continued to work with AppleTalk queues.

However, changes made to OpenVMS in V8.2 prevent the AppleTalk protocol from being started. Therefore, DCPS does not work with AppleTalk queues starting with OpenVMS V8.2.

1.3.7 DDIF Printing

To print DDIF encoded bitonal images, DCPS requires that either DECwindows or DECimage Application Services (DAS) be installed on your system. DAS is only available on OpenVMS VAX systems.

1.3.8 DEC Image Print-PLUS (ICPS)

DCPS V1.1 and later versions cannot coexist with ICPS V1.x software. Installing DCPS replaces the image SYS$LIBRARY:TRN$DDIF_IMAGE.EXE. This new image is not compatible with the ICPS software.

1.4 Mismatched Components

All DCPS executable components attempt to ensure they are a matched set. If a mismatch occurs, DCPS reports an error when the queue starts. This error occurs when a component of a prior (incompatible) software version exists in the SYS$SPECIFIC area and newer components are installed in the SYS$COMMON area. The error that occurs depends on which versions of which components are executing, but the following message will be among those received:

%%%%%%%%%%% OPCOM 13-FEB-1995 21:38:08.66 %%%%%%%%%%% Message from user QUEUE_MANAGE on DAHLIA %QMAN-E-SYMDEL, unexpected symbiont process termination

The DCPS installation procedure checks for DCPS files in the SYS$SPECIFIC area and warns you of their existence.

Contents

Index

Ctrl/ x	A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
PF1 x	A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button.
`[Return]`	In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box.
...	A horizontal ellipsis in examples indicates one of the following possibilities: Additional optional arguments in a statement have been omitted. The preceding item or items can be repeated one or more times. Additional parameters, values, or other information can be entered.
. . .	A vertical ellipsis indicates the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.
( )	In command format descriptions, parentheses indicate that you must enclose choices in parentheses if you specify more than one.
[ ]	In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement.
\|	In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.
{ }	In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line.
bold type	Bold type represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason.
italic type	Italic type indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where dd represents the predefined code for the device type).
Example	This typeface indicates code examples, command examples, and interactive screen displays. In text, this type also identifies URLs, UNIX commands and pathnames, PC-based commands and folders and certain elements of the C programming language.
UPPERCASE TYPE	Uppercase type indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
-	A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.
numbers	All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes---binary, octal, or hexadecimal---are explicitly indicated.