1 1 1

# HP DECprint Supervisor (DCPS) for OpenVMS

# Software Installation Guide

Order Number: AA--PSVDL--TE

# November 2005

This guide describes how to install the DECprint Supervisor software.

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

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

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

Hewlett-Packard Company Palo Alto, California

© Copyright 2005 Hewlett-Packard Development Company, L.P.

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.

Printed in the U.S.

The DECprint Supervisor documentation set is available on CD-ROM.

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.

# Related Documents

The primary source of information about DCPS is the following set of software manuals:

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

For additional information about HP OpenVMS products and services, visit the following World Wide Web address:

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

# Reader's Comments

HP welcomes your comments on this manual. Please send comments to either of the following addresses:

Internet | openvmsdoc@hp.com
Mail | Hewlett-Packard Company OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Road Nashua NH 03062-2698

# How to Order Additional Documentation

For information about how to order additional documentation, visit the following World Wide Web address:

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

Part numbers for DCPS-related documentation are listed in the Ordering Additional Documentation appendix of the Software Installation Guide, System Manager's Guide and User's Guide.

# Conventions

The following conventions are 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.
`[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.
( ) | 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 text | This typeface represents the introduction of a new term. It also represents the name of an argument, an attribute or a reason.
italic text | Italic text 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).
UPPERCASE TEXT | Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
Monospace text | Monospace type indicates code examples and interactive screen displays.
- | 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 Alpha V6.2*, V7.3-2 and V8.2
- OpenVMS I64 V8.2 and V8.2-1
- 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.5 PCSI kit will install and run on OpenVMS V6.2 and later, and the DCPS V2.5 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.1 for more information about PCSI software requirements.)

Note #### * With Prior Version Support contract

# 1.2 Disk Space

Depending on whether DCPS is installed on an Alpha, I64 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 ... | Alpha system | I64 system | VAX system
--- | --- | --- | ---
Installation | 7,700 blocks | 11,000 blocks | 7,200 blocks
Permanent use | 7,200 blocks | 10,500 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 POLYCENTER Software Installation Utility (PCSI)

DCPS is now installed with the POLYCENTER Software Installation Utility (PCSI) instead of VMSINSTAL. This makes installation faster and provides better management of your installed software.

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-2 to determine whether you need to install a PCSI patch. The patch will upgrade PCSI on your system.

Table 1-2 PCSI Patch Kits
OpenVMS Version | PCSI Patch Kit
--- | ---
Alpha V6.2 through V7.1-2 | DEC-AXPVMS-VMS62TO71U2_PCSI-V0200--4
Alpha V7.2 and later | not required
I64 V8.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.2 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.3 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.4 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.5 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.6 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.7 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.

# Chapter 2
Installing the Software

This chapter describes how to install DECprint Supervisor software using the POLYCENTER Software Installation Utility (PCSI). 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.

# 2.1 Overview

Follow these steps to install the DECprint Supervisor (DCPS) for OpenVMS software:

1. Review all release notes. You can extract the release notes in text format from the PCSI kit with the command:

           $ PRODUCT EXTRACT RELEASE NOTES DCPS -
           _$ [/SOURCE=device:[directory]] -
           _$ [/DESTINATION=device:[directory]]

   You can extract the release notes in PostScript format with the command:

           $ PRODUCT EXTRACT FILE DCPS /SELECT=DCPS025_RELEASE_NOTES.PS -
           _$ [/SOURCE=device:[directory]] -
           _$ [/DESTINATION=device:[directory]]

2. Stop each DCPS queue using STOP /QUEUE /NEXT or STOP /QUEUE /RESET commands if:
   - You have existing running DCPS queues and do not want the DCPS installation procedure to automatically stop them.
   - You have DCPS executables in the SYS$SPECIFIC system areas.*
   - You need to apply OpenVMS or other patches that impact DCPS.
3. Remove any DCPS executable files from the SYS$SPECIFIC system areas.*
4. Apply OpenVMS or other patches that impact DCPS, as determined from the DCPS release notes or other sources. If the patches require that you reboot your system, do so after applying the patches.
5. Install DCPS.
6. Create or update DCPS$STARTUP.COM, as described in the System Manager's GuideSystem Manager's Guide. For example, add queue definitions to the file and set the value of the DCPS$MAX_STREAMS logical following the examples provided in the procedure.
7. Start your DCPS print queues by invoking DCPS$STARTUP.COM. The DCPS installation procedure restarted DCPS queues that it stopped, unless the installation failed. If you changed your DCPS environment or DCPS$STARTUP.COM after the DCPS installation procedure automatically restarted some queues, you may need to stop all DCPS queues and restart them before your changes will take effect.

Note #### * The installation procedure checks for such files.

# 2.2 PCSI Conventions

PCSI will ask questions during the installation. Questions may be followed by default responses enclosed in brackets ([]). Enter your response followed by `[Return]`.

Press `[Return]` to enter the default response. If you are not sure of the response, enter a question mark (?). PCSI displays explanatory text and repeats the prompt.

Messages specific to the installation of DECprint Supervisor software are listed in Section B.4.

# 2.3 Installing the Software

Note This section does not reproduce all of the text you may see on your screen during the installation of the DCPS software. A sample PCSI installation is shown in Appendix A.

To install the software, use the following procedure:

1. Invoke the PCSI utility.
   Enter the following command:

           $ PRODUCT INSTALL DCPS [/SOURCE=device:[directory]]

   where device and directory specify the location of the DCPS PCSI kit.
   Do not specify an alternate destination by using the /DESTINATION qualifier or defining the logical name PCSI$DESTINATION. DCPS needs to be installed in the cluster common area of your system disk and will be installed there regardless of the alternate destination you specify.
2. Select the DCPS kit.
   If more than one DCPS PCSI kit exists in the source directory, you will be prompted to choose one. For example:

          1 - HP AXPVMS DCPS V2.4                 Layered Product
          2 - HP AXPVMS DCPS V2.5                 Layered Product
          3 - HP I64VMS DCPS V2.5                 Layered Product
          4 - HP VAXVMS DCPS V2.5                 Layered Product
          5 - All products listed above
          6 - Exit

       Choose one or more items from the menu separated by commas:

   Choose the kit with the correct DCPS version and for the architecture on which you are installing DCPS.
3. Announce products to be installed.
   PCSI then announces the products to be installed. For example:

       The following product has been selected:
           HP AXPVMS DCPS V2.5                    Layered Product [Installed]

       Do you want to continue? [YES]

   If this is the DCPS kit you want to install, press `[Return]`.
4. Check for alternate destination.
   If DCPS has already been installed on your system using PCSI and you specified an alternate destination, you will see these messages:

       %PCSIUI-W-DESTQUAL, destination qualifier will be ignored for this product

           * When reinstalling a product you cannot specify a destination.
           * To change the product's destination, remove the product then
           * install it to a new location.  If you continue this operation,
           * the product will be reinstalled in its current location.

       Do you want to continue? [YES]

   Since DCPS is always installed in SYS$COMMON on your system disk, press `[Return]` to continue the installation.
5. Start the installation.
   PCSI then starts the installation, displaying messages such as:

       Configuration phase starting ...

       You will be asked to choose options, if any, for each selected product and for
       any products that may be installed to satisfy software dependency requirements.

       HP AXPVMS DCPS V2.5: HP DECprint Supervisor for OpenVMS

           © Copyright 2005 Hewlett-Packard Development Company, L.P.

6. Check for sufficient disk space.
   PCSI checks to see if the amount of disk space required for the installation is available. If the space is not available, a message indicates the amount of disk space that is required, and the installation is aborted. You must allocate sufficient disk space and then start the PCSI procedure again.
   If there is sufficient disk space, the installation procedure continues.
7. Make sure the queue manager is running.
   The installation procedure checks to see if the queue manager is running on your system.
   If the queue manager is not running, the Installation Verification Procedure (IVP) does not run, and the following messages are displayed on your screen:

           The queue manager is not running.  The IVP will not be run.

   The queue manager must be running if you want the installation to run the IVP.
8. Check for running DCPS queues.
   The DCPS installation begins by looking for DCPS queues on your system:

       Examining system environment ...

   If no DCPS print queues are running, skip the next two steps.
9. Choose whether to display queues to be stopped.
   If DCPS print queues are running, one of the following messages are displayed.
   - If the queues are all running on the current system:

             You should stop all running DCPS queues on this system (node-name).

         Do you want to see a list of queues that will be stopped? [NO]

   - If there are also queues running on systems that use the current system's system disk:

             You should stop all running DCPS queues affected by this
             installation.  This includes queues on these systems:

               node-name
               .
               .
               .
               node-name

   If you want to see a list of DCPS queues that will be stopped by the installation procedure, enter YES and press `[Return]`. Otherwise, press `[Return]`.
10. Choose which queues to stop.
    Since the DCPS installation installs a new version of software in the cluster common directory on the current system, you should stop all DCPS queues running on systems that use the current system disk. This choice is the default.
    Depending on your environment, you are given a number of choices when deciding what queues to stop during the installation. The choices include:
    - Stop the n DCPS queues on this system
      This choice is the default if running DCPS queues are found on your system.
    - Stop the n DCPS queues affected by this installation
      This choice is the default if running DCPS queues are found both on the current system and others that use the current system disk.
    - Continue installation (there are no running queues on this system)
      This choice is the default if no running DCPS queues are found that would be affected by the installation.
    - Stop the n DCPS queues in the cluster
      There is no need to stop queues in the cluster not affected by the installation, but this option is offered for convenience. (This is the DCPS V2.4 installation behavior.)
    - Do not stop any queues (not recommended)
      This is not recommended because unpredictable results may occur. Running queues are still running the old DCPS software until the queues are stopped, but, for example, device control libraries are updated by the installation and may be incompatible with the old software. If you choose this option, queues should be stopped and restarted as soon as possible after the installation completes.
    Choices are presented in a numbered list similar to the following:

    Next | Contents | Index