# Compaq DECprint Supervisor (DCPS) for OpenVMS

# Software Installation Guide

Order Number: AA--PSVDG--TE

# July 2002

This guide describes how to install the DECprint Supervisor for OpenVMS software.

Revision/Update Information: This guide supersedes AA--PSVDF--TE.

Operating System & Versions: OpenVMS Alpha, Version 6.2, 7.2-2, 7.3 or 7.3-1
OpenVMS VAX, Version 5.5-2, 7.2 or 7.3

Software Version: Compaq DECprint Supervisor (DCPS) for OpenVMS, Version 2.1

Compaq Computer Corporation
Houston, Texas

© 2002 Compaq Information Technologies Group, L.P.

Compaq, the Compaq logo, Alpha, DCPS, DECnet, OpenVMS, VAX and VMS are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries.

Microsoft and Windows are trademarks of Microsoft Corporation in the U.S. and/or other countries.

All other product names mentioned herin may be trademarks of their respective companies.

Confidential computer software. Valid license from Compaq 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.

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

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 DECprint Supervisor for OpenVMS System Manager's Guide
- VMSINSTAL utility for installing OpenVMS software

If your printing environment utilizes the network to communicate with printers, you must have some knowledge of network management tools.

The DECprint Supervisor for OpenVMS System Manager's Guide contains information about postinstallation tasks, such as creating queues and customizing your printing environment.

# Conventions

The following conventions are used throughout this document:

Convention | Meaning
--- | ---
UPPERCASE | Uppercase characters indicate DCL commands, qualifiers, and parameters.
italics | Italic characters are used in command examples to indicate that you are to substitute a word or value of your choice.
bold | Bold characters are used in examples to show the characters that you should enter as part of the procedure.
[] | Brackets indicate that the enclosed item is optional.
Ctrl/ x | This symbol indicates a control key sequence. Press the key labeled Ctrl while you simultaneously press another key, represented by x.
`[Return]` | This symbol indicates that you should press the Return key.

# Chapter 1
Before Installing the Software

DECprint Supervisor runs on OpenVMS Alpha and OpenVMS VAX systems. The files that are installed on the two systems differ. See the Release Notes for a full list of the files.

Note Starting with DCPS V2.0, the need for DCPS-OPEN and DCPS-PLUS licenses has been eliminated. The right to use all features of DCPS is now included with the OpenVMS operating system license.

# 1.1 Operating System Version

DCPS V2.1 is fully supported on currently-supported versions of the OpenVMS operating system:

- OpenVMS Alpha V6.2, V7.2-2, V7.3 and V7.3-1
- OpenVMS VAX V5.5-2, V7.2 and V7.3

Although DCPS V2.1 will install on systems running OpenVMS Alpha V6.1 or later, or OpenVMS VAX V5.5-2 or later, customers running OpenVMS versions that are not currently supported do so at their own risk.

# 1.2 Disk Space

Depending on whether DECprint Supervisor is installed on an 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 ... | Alpha system | VAX system
--- | --- | ---
Installation | 7400 blocks | 5900 blocks
Permanent use | 6900 blocks | 5500 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 for OpenVMS Software Product Description (SPD) for specific version requirements.

## 1.3.1 DEC C Run-Time Library

DCPS requires that the DEC 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 and V6.0 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 for OpenVMS.
  The DEC C/C++ Run-Time Components kit is included on the DCPS CD-ROM starting with V1.6, and is also available on the OpenVMS VAX Software Product Library CD-ROM distributed by Compaq. 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.2 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.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 protocol, require one of the following:

- Compaq TCP/IP Services for OpenVMS
- Process Software MultiNet for OpenVMS
- Process Software TCPware for OpenVMS

## 1.3.4 AppleTalk Networks

Printers connected to AppleTalk networks can be accessed by the DECprint Supervisor for OpenVMS software, and thus be made available to OpenVMS system users as shared network printers. This printing system configuration requires PATHWORKS for OpenVMS (Macintosh) software.

Note PATHWORKS for OpenVMS (Macintosh) has been retired and is no longer supported.

## 1.3.5 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.6 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 mis-match 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. For example:

- If the executing version of DCPS$SMB.EXE is V1.1A, and all other components are from Version 1.2, then the following error occurs on an OpenVMS VAX V5.5-2 system:

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

      %%%%%%%%%%%  OPCOM  13-FEB-1995 21:38:08.67  %%%%%%%%%%%
      Message from user QUEUE_MANAGE on DAHLIA
      -SYSTEM-F-ACCVIO, access violation, reason mask=00,
      virtual address=00000000, PC=0001A9B8, PSL=03C00000

- If the executing version of DCPS$SMBSHR.EXE is V1.1A, and all other components are from Version 1.2, then the following error occurs on an OpenVMS VAX system:

      %%%%%%%%%%%  OPCOM  13-FEB-1995 21:44:42.40  %%%%%%%%%%%
      Message from user SYSTEM on DAHLIA
      Process SYMBIONT_98: %SMBSHRMISMTCH2, Wrong version of
      DCPS$SMBSHR.EXE

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

      %%%%%%%%%%%  OPCOM  13-FEB-1995 21:44:42.52  %%%%%%%%%%%
      Message from user QUEUE_MANAGE on DAHLIA
      -NONAME-F-NOMSG, Message number 064BE124

- If the executing version of DCPS$SMBSHR.EXE is V1.1A, and all other components are from Version 1.2, then the following error occurs on an OpenVMS Alpha system:

      %%%%%%%%%%%  OPCOM   1-FEB-1995 12:20:35.02  %%%%%%%%%%%
      Message from user QUEUE_MANAGE on DNGBAT
      %QMAN-E-SYMDEL, unexpected symbiont process termination

      %%%%%%%%%%%  OPCOM   1-FEB-1995 12:20:35.03  %%%%%%%%%%%
      Message from user QUEUE_MANAGE on DNGBAT
      -IMGACT-F-SYMVECMIS, shareable image's symbol vector table
      mismatch

# Chapter 2
Installing the Software

This chapter describes how to install DECprint Supervisor software using the VMSINSTAL utility. If you are not familiar with the VMSINSTAL utility, refer to the OpenVMS System Manager's Manual.

# 2.1 Overview

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

1. Review all release notes.
2. Stop each DCPS queue using STOP/QUEUE/NEXT or STOP/QUEUE/RESET if you have existing DCPS queues and do not want the DCPS installation procedure to automatically stop them, or you have DCPS executables in the SYS$SPECIFIC system areas, or you need to apply OpenVMS or other patches that impact DCPS.
3. Remove any DCPS executables 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 DECprint Supervisor for OpenVMS System 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 may have restarted DCPS queues that it stopped, if you chose to allow it to do so. 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.

# 2.2 VMSINSTAL Conventions

VMSINSTAL will prompt you for site-specific information. Questions are preceded by an asterisk (*) and 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 (?). VMSINSTAL displays explanatory text and repeats the prompt.

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

# 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 DECprint Supervisor software. Sample VMSINSTAL installation scripts are shown in Appendix A.

To install the software, use the following procedure:

1. Invoke the VMSINSTAL procedure.
   Enter the following command:

       $ @SYS$UPDATE:VMSINSTAL DCPSpppnnn device-id [OPTIONS N]

   You supply the following information:
   - DCPSpppnnn is the save set name, with ppp designating the platform (AXP (Alpha) or VAX) and nnn designating the version (for example, 021 for V2.1).
   - device-id is the name of the device on which you want to mount the media, such as DQA0:.
   - OPTIONS N allows you to request release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. Review the release notes before proceeding with the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N.
   First, VMSINSTAL displays a banner line with the date and time, and instructions for running the dialog. You may receive one or more of the following warning messages when VMSINSTAL starts up. Exit from the procedure, correct the cause of the warning message, and start the VMSINSTAL procedure again.
   - If you are not currently logged in to the SYSTEM account, the following message is displayed:

         %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.

   - If processes are running while VMSINSTAL is running, the following message is displayed:

         %VMSINSTAL-W-ACTIVE, The following processes are still active:
                 process-name

   Other processes may cause the installation of HELP to fail. When any of these messages are displayed, the following question is displayed to allow you to terminate VMSINSTAL and correct the situation:

       * Do you want to continue anyway [NO]?

   Enter YES to continue. If you answer NO, the VMSINSTAL procedure is terminated immediately.
   You can enter a question mark (?) at this time to display advice from the VMSINSTAL software. For example:

       The above conditions may cause VMSINSTAL to function improperly.
       In particular, problems may occur with file ownership if you are not
       logged into the SYSTEM account.

2. Ensure that existing software is saved.
   VMSINSTAL then asks the following question:

       * Are you satisfied with the backup of your system disk [YES]?

   Enter YES to continue, or enter NO to exit VMSINSTAL to make a backup and run VMSINSTAL again.
   If you enter a question mark (?) in response to this question, VMSINSTAL displays the following explanation:

       VMSINSTAL attempts to ensure that a power failure or system crash
       will not corrupt your system disk.  However, for absolute safety we
       recommend that you back it up before installing new products.  Please
       see the documentation for more information on crashes during
       installation.

3. Confirm that distribution media is loaded.
   VMSINSTAL asks for confirmation that the distribution media has been mounted.

        Please mount the first volume of the set on device-id:
       * Are you ready?

4. Announce products to be installed.
   VMSINSTAL then announces the products to be installed where ppp designates the platform and n.n designates the version.

       The following products will be processed:

       DCPSppp Vn.n

               Beginning installation of DCPSppp Vn.n at 13:45

       %VMSINSTAL-I-RESTORE, Restoring product saveset A

5. Obtain the release notes.
   If you specified OPTIONS N in the VMSINSTAL command line, the following Release Notes options are displayed:

       Release notes included with this kit are always copied to SYS$HELP.

       Additional Release Notes Options:

          Release Notes Options:
                 (1) Display release notes
                 (2) Print release notes
                 (3) Both 1 and 2
                 (4) None of the above

   After you enter the release note option, VMSINSTAL asks whether you want to continue the installation procedure:

       Do you want to continue the installation [NO]?

   If you did not include the OPTIONS N portion of the VMSINSTAL command line, VMSINSTAL does not display this question. Instead, the following message is displayed:

       %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP

6. Check for active DCPS queues.
   If DCPS print queues are active while VMSINSTAL is running, messages similar to the following are displayed:

       %DCPSVAX-W-QUEACTIVE, The following DCPS queues are still active:

       Queue                     Device                                    Status
       -----                     ------                                    ------
       LN09                      DAN::LTA9000:                             IDLE
       LN17                      DAN::"AppleTalk/Dan's LN17+ps"            IDLE
       LN40                      DAN::"IP_RawTCP/ln40:6869"                IDLE
       LPS32                     DAN::"IP_CPAP/lps32.office.genicom.com"   IDLE

       %DCPSVAX-I-NUMQUEUES, 4 existing DCPS queues, with 4 active

               Previously installed DCPS queues are still running.
               Continuing this installation without entering
               STOP/QUEUE/RESET for each such queue can cause
               inconsistent behavior among queues and can cause
               the IVP to fail.

               Note that if you choose to have this installation
               procedure automatically stop such queues, and the
               installation subsequently aborts, this procedure
               will not automatically restart them.

       * Do you want these queues automatically stopped and restarted [YES]?

   If you do not want the installation procedure to automatically stop them, you are given the options of aborting the installation or continuing with the queues active. Continuing is not recommended.
7. Check for sufficient disk space.
   VMSINSTAL 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 VMSINSTAL procedure again. However, if you have already provided enough disk space, the installation procedure continues.
8. Purge extraneous versions of files.
   VMSINSTAL asks if you want to purge any files that are being replaced.

       * Do you want to purge files replaced by this installation [YES]?

   Enter YES if you want to save disk space or NO if you think the files may still be of use.
   If you enter a question mark (?) in response to this query, the following message is displayed:

       During this installation, new files will be provided to replace
       existing versions.  You may purge these older versions to save disk
       space, or keep them if you feel they may be of use.  Purging is
       recommended.

9. Define DCPS$LAYUP.
   Next, the installation procedure looks for a definition of the logical name DCPS$LAYUP in the system table in executive mode.
   - If a definition exists, the following message is displayed:

         %DCPSppp-I-LAYUPDEF, DCPS$LAYUP is already defined
         -DCPSppp-I-LAYUPDEF, This installation will use its value

   - If a definition does not exist, the procedure asks you for a definition. Press `[Return]` to select the default, SYS$SYSROOT:[SYSHLP.EXAMPLES.DCPS], or enter a directory specification where the system layup definition files should be stored.

         * Full definition for DCPS$LAYUP [SYS$SYSROOT:[SYSHLP.EXAMPLES.DCPS]]:

     The procedure will validate the definition you provide. If you do not accept the default location and the specified directory does not exist, the procedure will ask you if you want to create it:

         DISK$USER:[MY-LAYUP-DIR] does not exist.

         * Create it? [N]?

     If you answer NO, the procedure will ask again for a definition.
10. Create directories.
    VMSINSTAL then attempts to create several directories. If they already exist, it displays additional messages indicating this:

        %VMSINSTAL-I-SYSDIR, This product creates system disk directory
             VMI$ROOT:[SYSTEST.DCPS].
        %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.DCPS] already exists
        %VMSINSTAL-I-SYSDIR, This product creates system disk directory
             VMI$ROOT:[SYSHLP.EXAMPLES.DCPS].
        %CREATE-I-EXISTS, VMI$ROOT:[SYSHLP.EXAMPLES.DCPS] already exists
        %VMSINSTAL-I-SYSDIR, This product creates system disk directory
             VMI$ROOT:[SYSHLP.EXAMPLES.DCPS.NETPRINT].
        %CREATE-I-EXISTS, VMI$ROOT:[SYSHLP.EXAMPLES.DCPS.NETPRINT] already exists

11. Make sure the queue manager is running.
    VMSINSTAL checks to see if the queue manager is running on your system.
    If the queue manager is not present, the Installation Verification Procedure (IVP) does not run, and the following messages are displayed on your screen:

        %DCPSppp-I-NOQUEMGR, System queue manager is not running
        -DCPSppp-I-NOQUEMGR, IVP will NOT run.  Installation continuing ...

    The queue manager must be running if you want the installation to run the IVP.
12. Stop queues.
    At this point, VMSINSTAL displays the following message on your screen:

        %DCPSppp-I-NOQUEST, No further questions will be asked.

    VMSINSTAL stops active DCPS queues, if any and if desired.

        %DCPSppp-I-STOPQUEUES, Stopping queues previously reported as active.

13. Restore the remaining save sets. As it restores each save set, VMSINSTAL reports on its progress:

        VMSINSTAL-I-RESTORE, Restoring product saveset B ...
        VMSINSTAL-I-RESTORE, Restoring product saveset C ...

    This operation may require up to 10 minutes to complete.
    When all the save sets have been restored, VMSINSTAL instructs you to perform postinstallation procedures. Refer to the DECprint Supervisor for OpenVMS System Manager's Guide for full instructions.
    Next, VMSINSTAL moves the files from the temporary locations used during installation to their permanent directories.

    Next | Contents | Index