# Compaq PATHWORKS for OpenVMS
Server Installation and Configuration Guide

Previous | Contents | Index

## 1.9.14 Step 14: Check for Existing OpenVMS Server Images and Files

Make sure that:

1. No Compaq OpenVMS file and print server images (current or earlier versions) are running on the local system or on any member of the OpenVMS Cluster (when installing on a cluster).
2. No files from a PATHWORKS for OpenVMS (NetWare) kit are on the system disk. If such files are present, use SYS$UPDATE:PWVN$DEINSTAL.COM (included with the PATHWORKS for OpenVMS (NetWare) kit) to remove those files.
3. No PATHWORKS or Advanced Server for OpenVMS images reside in the SYS$SPECIFIC: directory area of the system disk on which PATHWORKS will be installed. (When PATHWORKS V6.1 for OpenVMS (Advanced Server) is installed, images in the SYS$SPECIFIC: directory area will be used before the corresponding images in the SYS$COMMON: directory area are used.) To remove the PATHWORKS or Advanced Server (V7.2 or V7.2A) for OpenVMS files, use the PWRK$DEINSTAL utility. To remove the Advanced Server V7.3 for OpenVMS files, use the PRODUCT REMOVE command, as documented in the Compaq Advanced Server for OpenVMS Server Installation and Configuration Guide.

The server VMSINSTAL installation utility will detect if any of these conditions exist, and if the images or files are found, it will notify you. The VMSINSTAL installation utility automatically deletes, without notification, any files from a PATHWORKS Advanced Server or Advanced Server for OpenVMS kit found in the SYS$SPECIFIC directory tree.

## 1.9.15 Step 15: Check OpenVMS Cluster Configuration

You can run the Advanced Server on multiple OpenVMS Cluster members. To do so, follow these steps:

1. An OpenVMS Cluster can include both VAX and Alpha member nodes. The PATHWORKS Advanced Server can run on any VAX or Alpha cluster member that is running a supported version of OpenVMS. However, an OpenVMS Cluster cannot support two different versions of the file and print server (for example, PATHWORKS V6 for OpenVMS (Advanced Server) and Advanced Server V7.3 for OpenVMS).
2. Decide which member nodes in the OpenVMS Cluster will run the Advanced Server, then identify all the system disks that will be used by those member nodes. Install the Advanced Server on each of those system disks.
   If the OpenVMS Cluster contains other system disks (for example, to support systems running earlier versions of OpenVMS), these disks might have older versions of Compaq OpenVMS file and print servers installed on them. If so, remove the older versions to prevent them from accidentally starting up while the Advanced Server is running on the current OpenVMS systems. To remove the PATHWORKS for OpenVMS (Advanced Server) product, execute the command procedure SYS$UPDATE:PWRK$DEINSTAL from a cluster member that uses the system disk from which PATHWORKS is to be removed. For more information on using PWRK$DEINSTAL.COM, see Chapter 7, Removing PATHWORKS Advanced Server Software. To remove the Advanced Server V7.3 for OpenVMS product, use the PRODUCT REMOVE command, as documented in the Compaq Advanced Server for OpenVMS Server Installation and Configuration Guide. To remove earlier versions of the Advanced Server for OpenVMS, use PWRK$DEINSTAL.COM. To remove a PATHWORKS (LAN Manager) product, use the PWRK$DEINSTAL utility that was installed with the product. The PATHWORKS (LAN Manager) server must be stopped before you can remove it.
3. If you plan to use the TCP/IP transport, ensure that all cluster members on which the Advanced Server will run are in the same TCP/IP subnet.
4. If an earlier version of the PATHWORKS for OpenVMS (Advanced Server) or any other Compaq OpenVMS file and print server is running on any cluster member, stop the server on the cluster member system.
5. On each system on which you want to install the Advanced Server, complete the tasks described in this chapter.
   On each cluster member that you want to use as a file and print server, you will run the Advanced Server configuration command procedure (PWRK$CONFIG.COM), as explained in Chapter 3, Configuring the PATHWORKS Advanced Server. This ensures that each node has its appropriate parameters set and enough resources to run the server.
6. All cluster members that will run the Advanced Server must share a common:
   - System user authorization file (SYSUAF.DAT)
   - Rightlist file (RIGHTSLIST.DAT)
   - Advanced Server data directory location (PWRK$COMMONROOT:)
7. When installing the Advanced Server on an OpenVMS Cluster member, if the following two conditions apply, you are must shut down the server and reboot the systems running the server. (You can avoid the reboot, as noted below.)
   1. Advanced Servers are installed on two or more system disks in the cluster
   2. The Advanced Server is already running on one or more cluster members that are booted from a system disk other than the one on which the installation is occuring
   To avoid having to reboot the systems that are already running the Advanced Server, the system administrator can deassign the logical name (PWRK$REBOOT_REQUIRED) that forces the reboot to occur on each affected node, as follows:

        $ DEASSIGN/SYSTEM PWRK$REBOOT_REQUIRED

# 1.10 Next Step

To install PATHWORKS Advanced Server, proceed to Chapter 2, Installing the PATHWORKS Advanced Server.

# Chapter 2
Installing the PATHWORKS Advanced Server

This chapter describes how to install the PATHWORKS for OpenVMS (Advanced Server) software. You must follow these procedures regardless of whether you are upgrading from a previous version of the server or installing the server for the first time.

Before you begin the installation procedure, make sure that you have completed the preinstallation tasks listed in Chapter 1, Before You Install PATHWORKS Advanced Server.

This chapter consists of the following sections:

- Section 2.1, About the Installation Procedure
- Section 2.2, Installing the Server
- Section 2.3, Troubleshooting Installation Problems
- Section 2.4, Next Steps

# 2.1 About the Installation Procedure

The following sections describe the installation procedure and what it does.

## 2.1.1 What is VMSINSTAL?

VMSINSTAL is the standard command procedure for installing software on the OpenVMS operating system. VMSINSTAL consists of a series of questions (prompts). Your answers to these questions provide VMSINSTAL with the information needed for installing PATHWORKS Advanced Server.

## 2.1.2 PATHWORKS Advanced Server Installation Kit

The VMSINSTAL installation kit includes several OpenVMS BACKUP save sets. The save set PWRK061.A always contains the file KITINSTAL.COM and the release notes. The savesets included in the software kit are listed in the product release notes.

## 2.1.3 What VMSINSTAL Does

When you use VMSINSTAL, it:

1. Determines whether the PATHWORKS for OpenVMS (NetWare) server is installed on the system, and if it is, optionally removes the NetWare server software.
2. Creates PATHWORKS Advanced Server accounts on the file and print server, if necessary.
3. Restores the files from the save sets in the installation kit.
4. Creates DECnet objects, if you are running DECnet or DECnet-Plus.
5. Installs the PATHWORKS Advanced Server DCL command definition file.
6. Installs the PATHWORKS Advanced Server logical names definition files.
7. Deletes obsolete files.
8. Installs the PATHWORKS Advanced Server files.
9. Verifies that the software has been installed successfully. (See Section 5.2, Verifying the PATHWORKS for OpenVMS (Advanced Server) Installation, for information on how to run the Installation Verification Procedure after installing the software.)

# 2.2 Installing the Server

The following sections describe how to prepare information required during the installation procedure, and how to specify the required information during the procedure.

## 2.2.1 Before You Start VMSINSTAL

Before you start the VMSINSTAL command procedure, be prepared to answer the following questions. The questions that VMSINSTAL asks depend on the software environment and options you select.

1. What is the product identifier?
   The product identifier tells VMSINSTAL which save sets to copy from the media to a disk on the system. The product identifier for PATHWORKS Advanced Server is:
   PWRK061
2. What is the name of the device on which you want to mount the media?
   The device name depends on the type of media and computer you have. For example, if you want to mount a CD-ROM on the CD-ROM drive of your Alphastation 400, the device name might be DKA400.
3. Do you want to access the online release notes during the installation procedure?
   You can tell VMSINSTAL to ask you whether you want to display or print the online release notes during installation. Because the release notes may describe important changes to the installation procedure, Compaq recommends that you read them. Procedures for obtaining the release notes are described in Section 1.6, Reading the Release Notes.
4. Do you want to install just the Upgrade utility?
   If the PATHWORKS (LAN Manager) server is installed on the system, you are prompted to install the Upgrade utility separately, which allows you to upgrade server database files before you install the PATHWORKS for OpenVMS (Advanced Server). Appendix D, Upgrade Utility Installation, shows a sample installation of the Upgrade utility.
   To install the PATHWORKS Advanced Server, you must upgrade the server databases. If you choose to install just the Upgrade utility, you can install the PATHWORKS Advanced Server later, after you upgrade your databases. If you install the PATHWORKS Advanced Server software, the Upgrade utility is also installed.
5. Do you want to preserve the PATHWORKS (LAN Manager) environment, and if so, where?
   If you are upgrading from PATHWORKS (LAN Manager), you can choose to have the PATHWORKS (LAN Manager) data files copied to the location you specify in the installation procedure. This allows you to roll back to PATHWORKS (LAN Manager) later, after configuring and starting the PATHWORKS Advanced Server. Refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for more information about the PATHWORKS Rollback procedure.
   If you have V4.x of PATHWORKS for OpenVMS, you must upgrade to PATHWORKS (LAN Manager) before installing PATHWORKS V6 for OpenVMS (Advanced Server). For instructions on upgrading from V4.x to V5, refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide.
6. Do you want to install PATHWORKS Advanced Server software?
   This option allows you to install the complete PATHWORKS for OpenVMS (Advanced Server) server, including the Upgrade utility, the integrated License Server, and the external authentication software.
   Appendix B, Sample Complete Server Installation and Configuration, shows a sample installation and configuration of the complete PATHWORKS for OpenVMS (Advanced Server) server.
7. Do you want to install the standalone License Server?
   If the system is designated to run the standalone License Server, you can install the License Server software only. Compaq recommends that you run the standalone License Server on a designated License Server system.
   The installation procedure gives you the option to install the standalone License Server software from the PATHWORKS for OpenVMS (Advanced Server) software kit. In this case, the complete PATHWORKS Advanced Server (including the file and print server) is not installed. If the complete PATHWORKS Advanced Server is installed, you cannot choose the standalone License Server installation option.
   Appendix C, Sample Standalone License Server Installation and Configuration, shows a sample installation and configuration of the standalone License Server.
8. Do you want to install PATHWORKS external authentication software only?
   If you have installed the Advanced Server and enabled external authentication in an OpenVMS Cluster that includes Alpha systems running OpenVMS 7.2-1 or later and VAX systems running OpenVMS 7.2 or later, and if these systems boot from a system disk that will not have the Advanced Server installed, you can install the standalone external authentication software on that system disk. For more information, see Section 1.5, About External Authentication . Appendix E, Sample External Authentication Installation , shows a sample installation of the standalone external authentication software.
9. What is the user identification code (UIC) group number?
   The PATHWORKS Advanced Server installation procedure creates the OpenVMS user accounts PWRK$DEFAULT and PWRK$GUEST, if they do not already exist. When an OpenVMS user account is created, it is assigned a UIC group number. The default selection displayed by the installation procedure is determined as follows:

   Condition | Default Displayed
   --- | ---
   You are installing PATHWORKS Advanced Server for the first time | The first available unused UIC group number, starting with 360
   PATHWORKS (LAN Manager) is currently installed, an account named PCFS$ACCOUNT already exists | The same group number as that associated with the existing account PCFS$ACCOUNT
   The file and print server accounts already exist | The same group number as the existing accounts

## 2.2.2 How to Respond to Prompts

An asterisk (*) at the beginning of a line in the installation procedure identifies a prompt to which you must respond.

Usually the prompt has a default answer, which the procedure displays in square brackets ([]) at the end of the question.

To accept a default, press Return. For example:

    * Is the selection correct [YES]? [Return]

## 2.2.3 How to Start VMSINSTAL

When you have completed the recommended preinstallation tasks outlined in Chapter 1, Before You Install PATHWORKS Advanced Server, and have read the release notes, you are ready to use the VMSINSTAL installation procedure to install the PATHWORKS Advanced Server. To start VMSINSTAL:

1. Ensure that you are logged in to the SYSTEM account.
2. Load the installation kit media onto a drive. (It is not necessary to mount the drive, but it must be on line so that the installation procedure can mount it.)
3. Enter the following command to check the status of the device on which you have loaded the installation kit, replacing device_name with the name of the applicable device:

       $ SHOW DEVICE device_name

   For example:

       $ SHOW DEVICE $1$DUS0:

       Device             Device  Error  Volume  Free    Trans  Mnt
        Name              Status  Count  Label   Blocks  Count  Cnt
       $1$DUS0: (HSC001)  Mounted     0  HUBSYS  347718    628    4

   If the device status is `Offline` , enter the following command to place the device online, replacing device_name with the name of your device:

       $ SET DEVICE/AVAILABLE device_name

4. Change your default directory to SYS$UPDATE:

       $ SET DEFAULT SYS$UPDATE

5. Check to make sure that other users are not logged in to the system.
6. If a previous version of the software is installed on the system, shut it down. In a cluster, shut down the software on all cluster members. For a noncluster server, enter:

       $ @SYS$STARTUP:PWRK$SHUTDOWN

   For a cluster server, enter:

       $ @SYS$STARTUP:PWRK$SHUTDOWN CLUSTER

7. If you have DECnet configured on your system and you want to create a log of the installation procedure, enter the following command and then log in to the system account again:

       $ SET HOST 0/LOG=file-name

   where file-name is the name of the file to which you want the log written.
8. Start VMSINSTAL and specify the PWRK061 product identifier, the media device, and whether you want access to the online release notes during the installation procedure:

   Access the Release Notes During Installation? | Command Line
   --- | ---
   Yes | `@VMSINSTAL PWRK061 device_name OPTIONS N`
   No | `@VMSINSTAL PWRK061 device_name`

9. The interactive installation procedure begins, and you are prompted for information.
   A sample installation script is included section by section, beginning with Example 2-1, Sample Installation Procedure---Part 1, with each section accompanied by additional explanatory information.
   The actual installation script that is displayed on your system might include additional questions and information, depending on your current configuration.

Note To interrupt the installation procedure, press `[Ctrl/Y]` at any time. The installation procedure deletes any files that were created, then exits. Then you can restart the installation from the beginning.

Example 2-1 Sample Installation Procedure---Part 1

    $@SYS$UPDATE:VMSINSTAL PWRK061 SYS$DEVICE:[KITS.PWRK] [Return]

            OpenVMS AXP Software Product Installation Procedure V7.2-1H1

    It is 13-JUL-2001 at 16:59.

    Enter a question mark (?) at any time for help.

    %VMSINSTAL-W-ACTIVE, The following processes are still active:
           TCPIP$ESNMP
           TCPIP$OS_MIBS
           TCPIP$HR_MIB
    * Do you want to continue anyway [NO]? Y [Return]

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

    The following products will be processed:

      PWRK V6.1

            Beginning installation of PWRK V6.1 at 16:59

    %VMSINSTAL-I-RESTORE, Restoring product save set A ...
    %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to
    SYS$HELP.

            PATHWORKS for OpenVMS Installation

       © Compaq Computer Corporation 2000. All rights reserved.

       Restricted Rights: Use, duplication, or disclosure by the U.S.
       Government is subject to restrictions as set forth in subparagraph
       (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR
       52.227-14 Alt. III, as applicable.

       This software is proprietary to and embodies the confidential
       technology of Compaq Computer Corporation. Possession, use, or
       copying of this software and media is authorized only pursuant to a
       valid written license from Compaq or an authorized sublicensor.

In Example 2-1, Sample Installation Procedure---Part 1, the installer specifies the source device SYS$DEVICE:[KITS.PWRK] for the installation kit.

The first part of the installation script indicates that certain processes are already running and gives you the option of continuing or stopping the procedure. In this example, the processes listed are part of the Compaq TCP/IP Services for OpenVMS software running on the system.

If you continue (respond YES to the prompt), the procedure asks if you are satisfied with the backup (backup of the system is recommended prior to installing the server), and then identifies the product being installed.

Example 2-2 Sample Installation Procedure---Part 2

        Please select from the following install options:

        PATHWORKS V6.1 for OpenVMS (Advanced Server)
        PATHWORKS V6.1 for OpenVMS (Advanced Server) License Server (only)
        External Authentication images (only)

    * Do you want to install the complete PATHWORKS V6.1 for OpenVMS [NO]?
    Y [Return]
    %PWRK-I-OLDVERPWRK, PATHWORKS V6.0-400D for OpenVMS (Advanced Server)
    -PWRK-I-OLDVERPWRK, was previously installed

    The following components will be installed:

            PATHWORKS V6.1 for OpenVMS (Advanced Server)

    If the selection is correct, the installation will continue.
    If the selection is not correct, you can change your selection.
    Press CTRL/Y if you want to terminate the installation.

    * Is the selection correct [YES]? [Return]

This part of the script gives you the option of installing the complete PATHWORKS Advanced Server product, installing only the standalone License Server, installing only the standalone external authentication images, or installing only the Upgrade utility.

In Example 2-2, Sample Installation Procedure---Part 2, the complete installation was selected, and the procedure continues. A message indicates a previous version of the Advanced Server has been installed on this system.

Example 2-3 Sample Installation Procedure---Part 3

    %PWRK-I-VERSION, Checking for OpenVMS version 6.2, or later...

        NOTE
        ----
        Because this kit provides a new streams execlet for NetBEUI and
        TCP/IP, you MUST reboot the system to complete installation of
        PATHWORKS.  If you do not reboot the system at this time, you must
        remember to reboot later before starting PATHWORKS.

        To complete the installation of this product, you should reboot
        the system.  If it is not convenient to reboot at this time, then
        enter NO to the following question.

        If you enter NO, the installation procedure will continue.

    * Will you allow a system shutdown after this product is installed
    [YES]? [Return]
    * How many minutes for system shutdown [0]: [Return]
    * Do you want to do an automatic system reboot [YES]? [Return]
    * Do you want to run the IVP after the installation is finished [YES]?
    [Return]
    * Do you want to purge files replaced by this installation
    [YES]? [Return]
    %PWRK-I-FREEBLKS, Checking for 160000 free blocks

      ****************************************************************
      * You must shut down the Advanced Server before you continue  *
      * installing PATHWORKS V6 for OpenVMS.    *
      ****************************************************************

        If you do not shut down the server, the installation will terminate.

    * Do you want to shut down the Advanced Server [YES]? [Return]
    Shutting down the currently running server(s)...

In Example 2-3, Sample Installation Procedure---Part 3, the installation procedure checks that the OpenVMS system for installation of the server is OpenVMS Version 6.2 or later. If it is an earlier version, the installation would abort.

The installation procedure then checks for circumstances requiring a system reboot. A reboot might be needed if:

- A previous version of a server driver (PCF or PCI) or of an execlet (PWRK$STREAMSOS_Vn.EXE), was detected in memory. The previous version could be from either an Advanced Server for OpenVMS or PATHWORKS for OpenVMS product. Reboot is required before starting the Advanced Server.
- System parameters were changed (in MODPARAMS.DAT), or server parameters were changed in a way that affected system parameters. Reboot is required before configuring the Advanced Server, as noted in Chapter 1, Before You Install PATHWORKS Advanced Server.

If a Compaq OpenVMS file and print server has been installed and started previously, certain images remain in system memory even after the product has been stopped or removed. As a result, before the Advanced Server can be started, you need to reboot the system to remove the old image from memory.

To help minimize downtime, the installation procedure requests a reboot only if and when necessary. You are not forced to reboot after installation.

In Example 2-3, Sample Installation Procedure---Part 3, software from an earlier version of PATHWORKS for OpenVMS was detected (such as an earlier version of the PWRK$STREAMSOS_Vn.EXE execlet; note that the version, n, corresponds to the version of OpenVMS, not of PATHWORKS). A reboot is necessary unless you do not plan to run the Advanced Server on this system.

The installation procedure gives you the option of delaying the reboot by continuing the procedure. You might want to delay the reboot so that you can complete installation or configuration processes that would be expedient to finish before rebooting. For example, when installing the server on an OpenVMS Cluster, you might want to delay a reboot until you complete the server installation and configuration on all nodes of the cluster.

To delay the reboot, continuing the installation, enter NO at the prompt asking if you will allow a system shutdown after the product is installed. In this example, the reboot is opted for, and then the procedure prompts the installer for the number of minutes to elapse before the shutdown occurs.

The installer is also prompted whether an automatic system reboot is requested, whether the installation verification procedure should be run after the installation, and whether to purge files replaced by this installation or keep previous versions intact. The installation verification procedure (IVP) can be run automatically, as shown in Example 2-5, Sample Installation Procedure---Part 5, or independently of the installation procedure, as described in Section 5.2, Verifying the PATHWORKS for OpenVMS (Advanced Server) Installation.

Example 2-4 Sample Installation Procedure---Part 4

                  User Accounts and User Identification Codes (UICs)
                  --------------------------------------------------

      PATHWORKS for OpenVMS creates two OpenVMS accounts: a default account,
      PWRK$DEFAULT, and  a guest account, PWRK$GUEST.  The default UIC group
      number for both these new accounts depends on the following:

      o If you are installing the server for the first time, the default is
        the first unused UIC group number, starting with 360.

      o If there is an existing account PCFS$ACCOUNT, the default is the UIC
        group number associated with PCFS$ACCOUNT.

      o If there is an existing account PWRK$DEFAULT or PWRK$GUEST, the
        default is the UIC group number associated with PWRK$DEFAULT or
        PWRK$GUEST, in preference to PCFS$ACCOUNT.  However, the default
        UIC group number will
        not be used to change the UIC of any existing accounts.

        For more information about UIC group numbers, see the OpenVMS System
        Manager's Manual.

    * Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST [360]:
    [Return]

        All questions have been answered.  The installation of
        PATHWORKS for OpenVMS will continue.

    %PWRK-I-ACCOUNTS, Creating OpenVMS accounts for PWRK$DEFAULT and
    PWRK$GUEST
    %PWRK-I-DEFAULTEXISTS, PWRK$DEFAULT account already exists
    %VMSINSTAL-I-RESTORE, Restoring product save set C ...
    %VMSINSTAL-I-RESTORE, Restoring product save set E ...
    %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL
    %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands
    %PWRK-I-SPECIFY, Specifying target directories for the provided files
    %PWRK-I-OBSOLETE, Deleting obsolete files

                                   Next Steps
                                   ----------

      To continue the installation procedure, enter the following command
      to execute the server configuration command procedure:

      $ @SYS$UPDATE:PWRK$CONFIG

      For information about the configuration command procedure, see the
      PATHWORKS (Advanced Server) Installation and Configuration Guide.

    $
    %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target
    directories...

Previous | Next | Contents | Index