1 Getting Started

This chapter defines key terms and describes preliminary procedures you must perform before an installation or upgrade to version 7.3–1 of the OpenVMS Alpha operating system.

1.1 Key Terms

The following are a few key terms you need to know before you install or upgrade the system:

Table 1–1 Definitions of Terms

Term	Definition
Operating system CD–ROM	The CD–ROM containing the OpenVMS Alpha operating system.
HSx device	A self-contained, intelligent, mass storage subsystem that lets computers in an OpenVMS Cluster environment share disks. The disk on which you install or upgrade the operating system can be connected to one of these systems (for example, an HSC or HSD).
InfoServer	A general-purpose disk storage server that allows you to use the operating system CD–ROM to install the operating system on remote client systems connected to the same local area network (LAN).
Local drive	A drive, such as an RRD42 CD–ROM drive, that is connected directly to an Alpha computer. If you have a standalone Alpha computer, it is likely that all drives connected to the system are local drives.
Source drive	The drive that holds the operating system CD–ROM during the upgrade or installation.
System disk	The disk that contains (or will contain) the OpenVMS Alpha operating system. The installation or upgrade procedure transfers the OpenVMS Alpha operating system from the operating system CD–ROM on the source drive to the system disk.
Target drive	The drive that holds the system disk during the upgrade or installation.

1.2 Examining Software and Hardware Components

Before beginning an installation or upgrade, be sure you have all the required hardware and software components, as described in the following sections.

1.2.1 Hardware Components

Before you begin an installation or upgrade, do the following:

• Be sure the hardware has been installed and checked for proper operation. For detailed information, see the hardware manuals you received with your Alpha computer.

• Be sure you know how to turn on and operate the components of your system, including the system unit, console, monitor, drives, terminals, and printers. If necessary, read the hardware manuals that came with these components.

• Set up your system to record the installation procedure on either a hardcopy terminal or a printer attached to the console terminal. (See your hardware manuals for more details about connecting those components to your system.) If you do not do this, the screen messages will be lost. You will need a transcript in case there is a problem during the installation.

1.2.2 Software Components

Before you begin an installation or upgrade, do the following:

• Be sure you have all the items listed on the bill of materials in the distribution kit. If your distribution kit is incomplete, notify your Compaq support representative and request priority shipment of any missing items.

• Before installing the OpenVMS Alpha operating system software, review all cover letters and release notes.

1.2.3 Operating System CD–ROM

Included in your kit is the OpenVMS Alpha operating system CD–ROM, which you use to install or upgrade the operating system, or to perform operations such as backing up the system disk. The CD–ROM is labeled similar to the following:

CD–ROM Label:	OpenVMS Alpha V7.3–1 Operating System
Volume Label:	ALPHA0731

$Q:\adept8\entities\note.eps$ Note

The volume label is the machine-readable name that the OpenVMS Alpha operating system and InfoServer systems use to access the CD–ROM.

1.2.4 Firmware Revision Checking

OpenVMS Alpha Version 7.3–1 provides enhanced firmware checking for systems during a boot operation. When you boot the OpenVMS Alpha operating system CD-ROM, the system automatically checks the version of console firmware, which includes PALcode, that is running on your computer. The system also provides more explicit information about how to upgrade the firmware. Previously, only the PALcode version was checked and the informational messages were less specific.

If you do not have the required version of console firmware, the system displays a message similar to the following:

%SYSBOOT-F-FIRMREV, Firmware rev. nnn is below the absolute minimum of nnn.
Please update your firmware to the recommended revision nnn, which can be found on the firmware CD labeled:
Alpha Systems Firmware Update Vn.n.

If you do not have the recommended version of console firmware, the system displays a message similar to the following:

%SYSBOOT-W-FIRMREV, Firmware rev.nnn is below the recommended minimum of nn.
                    Please update your firmware to the recommended revision,
                    which can be found on the firmware CD labeled:
                    Alpha Systems Firmware Update Vn.n.

The latest console firmware CD-ROM is included with your kit.

$Q:\adept8\entities\note.eps$ Note

Once you install this version of the OpenVMS Alpha operating system, the firmware check (similar to the previous PALcode check) will occur each time you reboot the system.

1.2.5 Device Naming Conventions

When you perform specific operations, you are asked to specify device names for the source drive and target drive. When specifying those device names, note the following naming conventions:

• When the source drive is a local CD–ROM drive, the device name is similar to the following:

DKA400

• When the source drive is a CD–ROM drive connected to the InfoServer, the device name is always the following:

DAD1

• When the target drive is a local disk, the device name is similar to the following:

DKA0:

Note the following conventions:

– DK is the device code of the boot device.

– A is the boot device controller designation.

– 0 is the unit number of the boot device.

• On Alpha systems configured in certain OpenVMS Cluster or HSx environments, the device naming convention is similar to the following:

DUA20.14.0.2.0

The values you specify identify components such as the boot device, controller, unit number of the boot device, HSx controller node number, and channel numbers. Because these values vary depending on your specific hardware configuration, refer to the owner, operator, and technical service manuals that came with your computer for detailed information.

1.3 Using the Operating System CD–ROM

The following sections describe how you use the operating system CD–ROM to install, upgrade, and modify your system disk.

1.3.1 Using the Menu

The OpenVMS Alpha operating system CD–ROM includes a menu system that allows you to easily upgrade or install the operating system and to perform related operations such as backing up the system disk, installing layered products, and removing or reconfiguring products. This command procedure starts automatically when you boot the OpenVMS Alpha operating system CD–ROM, displaying a menu from which you choose options to perform the following tasks:

• Install or upgrade the operating system from the CD–ROM.

• Display a list of products that can be installed from the CD–ROM.

• Install or upgrade layered products from the CD–ROM.

• Show which products are installed on your system.

• Reconfigure layered products installed on your system.

• Remove products.

• Enter a DCL environment from which you can perform preinstallation or maintenance tasks such as mounting or showing devices and backing up or restoring files on the system disk.

• Shut down the system.

Review the following sections to understand how the menu works. You will then be prepared to choose appropriate menu options when you are asked to do so before, during, and after an installation or upgrade.

1.3.2 Sample Menu Display

The following is a sample display of the menu:

    OpenVMS (TM) Alpha Operating System, Version 7.3-1

    Copyright (c) 2002 -- All rights reserved.

    Compaq Information Technologies, L.P.

    Installing required known files...

    Configuring devices... 

    ***************************************************************
    You can install or upgrade the OpenVMS Alpha operating system
    or you can install or upgrade layered products that are included
    on the OpenVMS Alpha operating system CD-ROM. 

    You can also execute DCL commands and procedures to perform
    "standalone" tasks, such as backing up the system disk. 

    Please choose one of the following:

        1)  Upgrade, install or reconfigure OpenVMS Alpha Version 7.3-1
        2)  Display products and patches that this procedure can install
        3)  Install or upgrade layered products and patches
        4)  Show installed products         
        5)  Reconfigure installed products
        6)  Remove installed products
        7)  Execute DCL commands and procedures
        8)  Shut down this system            
        
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?)

1.3.3 How the Install or Upgrade Option Works

The OpenVMS installation and upgrade options implement a POLYCENTER Software Installation (PCSI) utility concept called a platform. The OpenVMS Alpha platform contains the OpenVMS Alpha operating system, plus options for certain other products, including DECwindows Motif, DECnet-Plus, DECnet Phase IV, TCP/IP Services for OpenVMS, and Common Data Security Architecture (CDSA). Including these products in the OpenVMS Alpha platform allows you to install or upgrade these products along with the OpenVMS Alpha operating system.

You can look at the platform Product Definition File (PDF) itself. This file is located in [VMS$COMMON] on the OpenVMS operating system CD-ROM. The file has a name similar to DEC-AXPVMS-OVMS-Vnnnn-n.PCSI$DESCRIPTION, where the variables indicate the version number.

Once you select which of the optional products you want to install, information is retained in the database maintained by the PCSI utility. This information allows future OpenVMS upgrades to select the correct default choices for these optional products.

When you choose the install or upgrade option (1) from the menu, the system asks whether you want to preserve or initialize the system disk. The display is similar to the following:

   There are two choices for Installation/Upgrade:

   INITIALIZE - Removes all software and data files that were         
       previously on the target disk and installs OpenVMS Alpha.      

   PRESERVE -- Installs or upgrades OpenVMS Alpha on the target disk 
       and retains all other contents of the target disk.

   * Note: You cannot use PRESERVE to install OpenVMS Alpha on a disk on
        which OpenVMS VAX or any other operating system is installed.

Do you want to INITIALIZE or to PRESERVE? [PRESERVE]

1.3.3.1 Specifying the INITIALIZE Option

When you specify the INITIALIZE option, the following operations take place:

• All software and data files that were previously on the target disk are removed.

• The operating system is installed.

Specify the INITIALIZE option and perform a full installation under the following conditions:

• If your Alpha computer is new (it has never had any version of the operating system running on it, including factory-installed software).

• If your Alpha computer is running a version of the OpenVMS Alpha operating system and you want to overwrite the entire contents of the system disk (the operating system, application software, and user files).

• If you want to create a new system disk but keep the old one (if you want to alternate between the two).

• If you are running the OpenVMS Alpha operating system but cannot upgrade. For example, if you changed the names of system directories on the system disk, the upgrade procedure will not work correctly. Therefore, unless you chose to restore the system disk to its original directory structure, you would have to reinstall the operating system.

1.3.3.2 Specifying the PRESERVE Option

When you specify the PRESERVE option, the following operations take place:

IF ...	THEN ...
the OpenVMS Alpha operating system is not already installed on the target disk,	the following operations take place: • The operating system is installed. • All other contents of the target disk are retained.
the OpenVMS Alpha operating system is installed on the target disk,	the operating system is upgraded, as follows: • Old operating system files and new files are merged or replaced. • All other contents of the target disk are retained.

$Q:\adept8\entities\note.eps$ Note

If you intend to choose the PRESERVE option (because there are certain files on the disk that you want to retain), Compaq recommends that you first make a backup copy of your system disk. If there is any problem during the installation or upgrade that might affect the integrity of the disk, you will have the backup copy as a safeguard.

If you choose the PRESERVE option and choose a target disk that already contains the OpenVMS Alpha Version 7.3–1 software, you are provided with the option to either reconfigure or reinstall the OpenVMS Alpha operating system. Reconfigure the operating system if you want to change the options you chose to include when the operating system was installed. Reinstall the operating system if you think that your system files may have become corrupted.

See Section 8.9 for additional configuration information.

1.3.4 How the Layered Products Options Work

After you have installed or upgraded the operating system, you can use the menu to show, install, reconfigure (change previously selected options for a layered product), or remove products as well.

$Q:\adept8\entities\note.eps$ Note

When you boot the OpenVMS Alpha operating system CD–ROM and select the option to install layered products, that installation procedure does not run the Installation Verification Procedure (IVP) for layered products. Because the operating system is booted from the CD–ROM and the layered products are installed on a different device (the target drive), the IVPs cannot execute correctly. However, you can run the IVP for each layered product after you boot the target system (see the layered product installation documents for information on running the IVP).

1.3.5 How the DCL Option Works

When you choose the DCL option (7) from the menu, you can use a subset of DCL commands (such as SHOW DEVICE, MOUNT, and BACKUP) to perform specific preinstallation and maintenance operations. Note, however, that this is a restricted DCL environment in that certain DCL commands (such as PRODUCT) and certain utilities (such as VMSINSTAL) will not function as expected because you are booting from read-only or write-locked media and because the full system startup is not performed.

A triple dollar sign system prompt ($$$) indicates that you are in this restricted DCL environment, as shown in the following example:

$$$ SHOW DEVICE

To exit from the DCL environment and return to the main menu, enter the LOGOUT command.

1.3.6 How the Shutdown Option Works

When you choose the shutdown option (8) from the menu, your system shuts down and you are returned to the console prompt (>>>). The system displays a message similar to the following:

    Shutting down the system

        SYSTEM SHUTDOWN COMPLETE

1.4 Making the Install/Upgrade/Backup Selection

Now that you have reviewed key terms, examined hardware and software requirements, and learned how to use the menu system included on the OpenVMS Alpha operating system CD–ROM, you can do the following:

IF ...	THEN ...
you want to install the operating system in an OpenVMS Cluster environment,	go to Chapter 2, Preparing to Install in an OpenVMS Cluster Environment.
you want to install the operating system in a nonclustered environment,	go to Chapter 3, Installing the OpenVMS Alpha Operating System.
you want to upgrade the operating system in any environment,	go to Chapter 5, Before Upgrading the OpenVMS Alpha Operating System.
you want only to back up or restore your system disk,	go to Appendix B.

2 Preparing to Install in an OpenVMS Cluster Environment

This chapter contains information that you should review before performing an installation in an OpenVMS Cluster environment.

Before installing the operating system in an OpenVMS Cluster environment, be sure you review any relevant OpenVMS Cluster information contained in the following documents:

• The cover letters and the software product descriptions included with your distribution kit

• OpenVMS Alpha Version 7.3–1 New Features and Documentation Overview

• OpenVMS Alpha Version 7.3–1 Release Notes

Be sure the following sources of information are available as well:

• OpenVMS Cluster Systems manual

• Guidelines for OpenVMS Cluster Configurations

• Your network or system manager

2.1 Mixed-Version Support

OpenVMS Alpha Version 7.3–1 and OpenVMS VAX Version 7.3 provide two levels of support for mixed-version and mixed-architecture OpenVMS Cluster systems. These two support types are warranted and migration.

Warranted support means that Compaq has fully qualified the two versions coexisting in an OpenVMS Cluster and will answer all problems identified by customers using these configurations.

Migration support is a superset of the Rolling Upgrade support provided in earlier releases of OpenVMS and is available for mixes that are not warranted. Migration support means that Compaq has qualified the versions for use together in configurations that are migrating in a staged fashion to a newer version of OpenVMS VAX or OpenVMS Alpha systems. Problem reports submitted against these configurations will be answered by Compaq. However, in exceptional cases, Compaq may request that you move to a warranted configuration as part of the solution.

Compaq supports only two versions of OpenVMS running in a cluster at the same time, regardless of architecture. Migration support helps customers move to warranted OpenVMS Cluster pairs. Table 2 –1 shows the level of support provided for all possible version pairings.

Table 2–1 OpenVMS Cluster Warranted and Migration Support

	Alpha V7.3x and VAX V7.3	Alpha V7.2-x^{1 (SEE NOTE)} and VAX V7.2
Alpha V7.3x and VAX V7.3	WARRANTED	Migration
Alpha V7.2-x¹ and VAX V7.2	Migration	WARRANTED

In a mixed-version cluster, you might need to install remedial kits on earlier versions of OpenVMS. For a complete list of required remedial kits, see the OpenVMS Alpha Version 7.3–1 Release Notes.

2.2 OpenVMS Cluster Information You Will Need

If during the installation you answer YES to the system prompt asking whether your system will be a member of an OpenVMS Cluster, you will need to provide the following information after you boot the system disk:

Required Information	Explanation
Type of configuration	Configuration types (CI, DSSI, SCSI, local area, or mixed-interconnect) are distinguished by the interconnect device that the VAX and Alpha computers in the OpenVMS Cluster use to communicate with one another.
DECnet node name and node address	See the network or system manager to obtain the DECnet node name and node address for the computer on which you are installing the OpenVMS Alpha operating system. If you install DECnet-Plus for OpenVMS (Phase V) software and do not plan to use DECnet Phase IV for OpenVMS addresses, then you do not need to provide this information.
Allocation class value	During the installation procedure, you will be asked for the allocation class value (ALLOCLASS) of the Alpha computer on which you are installing the OpenVMS Alpha operating system. For example: Enter a value for this_node ALLOCLASS parameter: Refer to OpenVMS Cluster Systems for the rules on specifying allocation class values. Note that in a mixed-interconnect OpenVMS Cluster environment, the allocation class value cannot be zero if the nodes serve DSSI or CI disks. It must be a value from 1 to 255. This is also true for any Alpha computer that is connected to a dual-pathed disk. After you enter the allocation class value, the installation procedure uses it to automatically set the value of the ALLOCLASS system parameter.
Whether you want a quorum disk	Refer to OpenVMS Cluster Systems to help you determine whether you want a quorum disk in the cluster.
Location of the page and swap files	On a nonclustered system, the page and swap files are on one or more local disks but on a clustered system, the files are on one or more local or clustered disks. See OpenVMS Cluster Systems to help you determine where the page and swap files will be located for the system on which you are installing the OpenVMS Alpha operating system software.
Systems that will be MOP^{2 (SEE NOTE)} servers, disk servers, and tape servers	If you are going to set up either a local area or a mixed-interconnect cluster, you will need to make these determinations.
Cluster group number and cluster password	If you are going to set up a local area cluster or a mixed-interconnect cluster that is LAN-based, use the following rules to determine the cluster group number and password: • Cluster group number — A number in the range from 1 to 4095 or 61440 to 65535 • Cluster password — Must be from 1 to 31 alphanumeric characters in length and can include dollar signs ($) and underscores(_)

2.3 Beginning the Installation

After you have completed all the tasks in this chapter, go to Chapter 3, Installing the OpenVMS Alpha Operating System to begin the installation.

3 Installing the OpenVMS Alpha Operating System

This chapter describes the following installation tasks:

• Preparing to respond to prompts during the installation

• Installing from the operating system CD–ROM

• Creating the system disk

• Registering licenses

• Selecting operating system components

• Installing layered products

• Booting the new system disk

• Joining an OpenVMS Cluster (optional)

• Running AUTOGEN

• Logging in to the SYSTEM account

$Q:\adept8\entities\note.eps$ Note

Before you install the operating system, the correct version of console firmware should be running on your computer, as described in Section 1.2.4.

3.1 Preparing to Respond to Prompts During the Installation

At different points during the installation, you must respond to prompts asking you to supply specific information. This manual and the Help text available during the installation procedure tell you how to obtain most of this information and how to make decisions when responding to specific prompts.

However, Compaq recommends that you review the following summary before you begin the installation so that you have an understanding beforehand of the types of information you will need to provide.

During the installation, the system will prompt you for the following information:

• The names of the source drive, target drive, and local area network device (if you are booting from an InfoServer system).

• Whether you want to select the INITIALIZE or PRESERVE option (as described in Chapter 1, Getting Started).

• A volume label for the target disk (if you choose not to use the default volume label).

• A password for the SYSTEM account. You will be prompted to enter a password of at least 8 characters (but not exceeding 31 characters).

• Whether you want to join an OpenVMS Cluster system and, if so, what kind (as described in Chapter 2, Preparing to Install in an OpenVMS Cluster Environment ).

• DECnet node name and address (or values for the system parameters, SCSNODE and SCSSYSTEMID).

$Q:\adept8\entities\note.eps$ Note

If you install the DECnet-Plus for OpenVMS software but want to use addresses compatible with DECnet Phase IV software, you still need to provide this information. These settings identify your system by name and number in a DECnet or cluster environment. Note that if you supply a DECnet address, the system will automatically calculate the SCSSYSTEMID value. If necessary, see the network or system manager to obtain this information.

• Information listed on Product Authorization Keys (PAKs) for your OpenVMS licenses. To register your licenses, you will need to enter the information listed on the PAK for each license.

• Operating system components that you want to install (including DECwindows and OpenVMS Management Station files). You can install all components by default, or you can select each component individually.

When you install the OpenVMS Alpha operating system, you can install along with it any or all of the following products:

– DECwindows Motif for OpenVMS

If you install this product, you must also include the Support for DECwindows components.

– TCP/IP Services for OpenVMS

– Either DECnet-Plus for OpenVMS or DECnet Phase IV for OpenVMS (but not both)

If you install either DECnet implementation, you must also include the Support for DECnet components.

$Q:\adept8\entities\note.eps$ Note

You must include the DECwindows and DECnet support components now even if you do not plan to install these products until later.

If you need to create a kit to install the PC component of the OpenVMS Management Station software, then you must include the OpenVMS Management Station Software -- PC files component.

See Section 3.5.3 for a complete list of components included with the OpenVMS Alpha operating system.

3.2 Booting the Operating System CD–ROM

The OpenVMS Alpha Version 7.3–1 operating system includes procedures that allow you to easily install the operating system using the POLYCENTER Software Installation utility. To get started, boot the OpenVMS Alpha operating system CD–ROM either from your local CD–ROM drive or from a CD–ROM drive connected to the InfoServer, as described in the following sections.

3.2.1 Booting from the Local Drive

To boot the operating system CD–ROM from the local CD–ROM drive, follow these steps:

1. Insert the operating system CD–ROM into the local CD–ROM drive.

2. At the console prompt (>>>), enter the SHOW DEVICE command so you can identify the name of the CD–ROM drive (for example, DKA400:).

3. Enter the boot command in the following format:

BOOT -FLAGS 0,0 source-drive

Substitute the device name of the CD–ROM drive (as listed in the SHOW DEVICE display) for source-drive.

For example, if the SHOW DEVICE display lists the device name of your CD–ROM drive as DKA400, enter the following command and press the Return key:

>>> BOOT -FLAGS 0,0 DKA400

3.2.2 Booting from the InfoServer

To boot the operating system CD–ROM using the InfoServer, follow these steps:

1. At the console prompt (>>>), enter the SHOW DEVICE command and scan the devices listed in the output to determine the name of the CD–ROM drive. Look for a device listed with its hardware address; for example, see the last line in the following example:

>>>SHOW DEVICE

dva0.0.0.1000.0    DVA0                     RX23
dka200.2.0.5.0     DKA200                   RZ28M  1004
dka300.3.0.5.0     DKA300                   RZ29B  0016
dka400.4.0.5.0     DKA400                   RZ26L  442E
ewa0.0.0.3.0       00-00-F8-1F-70-3D        Twisted-Pair

For additional information, refer to the Compaq OpenVMS Operating System for Alpha and VAX Software Product Description and the hardware manuals that you received with your Alpha computer.

2. At the console prompt, enter the following command:

>>> BOOT -FLAGS 0,0 -FILE APB_1073 lan-device-name

Note the following conventions:

• The APB file name is the unique file name that was assigned to the APB.EXE file when it was copied from the operating system CD-ROM to the InfoServer. This file is the name of the APB program used for the initial system load (ISL) boot program.

• lan-device-name is the name of the local area network (LAN) device identified with your computer, as determined by using the SHOW DEVICE command in the previous step.

$Q:\adept8\entities\note.eps$ Note

If you are using a DEC 3000 or 4000 series system, note the following:

• On DEC 3000 series systems, you can boot through the InfoServer using an alternate TURBOchannel device, such as a PMAD (Ethernet) or DEFTA (FDDI), by specifying the device name as “n/ESA0”. The value for n is the TURBOchannel slot number, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. For more information, see Section A.1.8 in Appendix A.

• On DEC 4000 series systems, you must specify the ISL file name in uppercase (APB_1073).

3. The InfoServer ISL program then displays the following menu:

   
Network Initial System Load Function
Version 1.2


  FUNCTION         FUNCTION
    ID
    1     -        Display Menu
    2     -        Help
    3     -        Choose Service
    4     -        Select Options
    5     -        Stop

Enter a function ID value:

4. Respond to the prompts as follows, pressing the Return key after each entry:

a. Enter 3 for the function ID.

b. Enter 2 for the option ID.

c. Enter the service name (ALPHA0731).

A sample display follows:

Enter a function ID value: 3  [Return]

OPTION          OPTION
   ID
   1     -       Find Services
   2     -       Enter known Service Name

Enter an Option ID value: 2  [Return]
Enter a Known Service Name: ALPHA0731  [Return]

$Q:\adept8\entities\note.eps$ Note

If you boot the OpenVMS Alpha operating system CD–ROM from an InfoServer but lose your connection during the installation procedure (the system is unresponsive and pressing Ctrl/Y does not return you to the menu), do the following:

IF ...

THEN ...

you previously chose the INITIALIZE option,

do the following:

1. Reboot the OpenVMS Alpha operating system CD–ROM.

2. Choose the install option from the menu and perform the installation again, as described in this chapter.

you previously chose the PRESERVE option,

do the following:

1. Reboot the OpenVMS Alpha operating system CD–ROM.

2. Enter the DCL environment by choosing option 7 from the menu.

3. Mount the device containing your backup copy of the target disk and the device that is your target disk.

4. Restore the backup copy of your target disk by entering the appropriate BACKUP commands. (See Appendix B for complete information using MOUNT and BACKUP commands to restore a system disk.)

5. Log out from the DCL environment.

6. Choose the install option from the menu and perform the installation again, as described in this chapter.

3.3 Creating the System Disk

The following sections describe how to create the system disk from the operating system CD–ROM.

3.3.1 Installing from the CD–ROM

After you boot the operating system CD–ROM, choose the install option (1) from the menu displayed on the screen. For example:

    OpenVMS (TM) Alpha Operating System, Version 7.3-1

    Copyright (c) 2002 -- All rights reserved.

    Compaq Information Technologies Group, L.P.

    Installing required known files...

    Configuring devices...

    ****************************************************************

    You can install or upgrade the OpenVMS Alpha operating system
    or you can install or upgrade layered products that are included
    on the OpenVMS Alpha operating system CD-ROM.
    
    You can also execute DCL commands and procedures to perform
    "standalone" tasks, such as backing up the system disk.
    
    Please choose one of the following:

        1)  Upgrade, install or reconfigure OpenVMS Alpha Version 7.3-1
        2)  Display products and patches that this procedure can install
        3)  Install or upgrade layered products and patches
        4)  Show installed products
        5)  Reconfigure installed products
        6)  Remove installed products
        7)  Execute DCL commands and procedures
        8)  Shut down this system

    Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1

The OpenVMS Alpha operating system CD–ROM may contain patch kits. If it does, information similar to the following is displayed:

    The following PATCH kits are present on the OpenVMS Alpha
    distribution media.

    ----------------------------------- ----------- ----------
    PRODUCT                             KIT TYPE    KIT FORMAT
    ----------------------------------- ----------- ----------
    DEC AXPVMS DNVOSIECO01 V7.3         Patch       Sequential
    DEC AXPVMS TCPIP_ECO V5.1-153       Patch       Sequential
    DEC AXPVMS TCPIP_ECO V5.1-152       Patch       Sequential
    DEC AXPVMS TCPIP_ECO V5.1-151       Patch       Sequential
    DEC VAXVMS TCPIP_ECO V5.1-153       Patch       Sequential
    DEC VAXVMS TCPIP_ECO V5.1-152       Patch       Sequential
    DEC VAXVMS TCPIP_ECO V5.1-151       Patch       Sequential
    ----------------------------------- ----------- ----------

    7 items found

    Please consult the OpenVMS Alpha Upgrade and Installation Manual,
    the Release Notes, and the Cover Letter to determine if any or
    all of these patches may be required for your system.

If you have not already done so, check to determine if you need to install any patches.

3.3.2 Choosing INITIALIZE or PRESERVE

After you choose the install option, the system displays the following information and prompts:

***********************************************************

    The installation procedure will ask a series of questions.

          () - encloses acceptable answers
          [] - encloses default answers

    Type your response and press the <Return>key.  Type:

          ? - to repeat an explanation
          ^ - to change prior input (not always possible)
          Ctrl/Y - to exit the installation procedure

    There are two choices for Installation/Upgrade:

    INITIALIZE - Removes all software and data files that were
        previously on the target disk and installs OpenVMS Alpha.

    PRESERVE -- Installs or upgrades OpenVMS Alpha on the target disk
        and retains all other contents of the target disk.

   * NOTE: You cannot use preserve to install OpenVMS Alpha on a disk on
         which OpenVMS VAX or any other operating system is installed.

Do you want to INITIALIZE or to PRESERVE? [PRESERVE]

Respond to the INITIALIZE or PRESERVE prompt as follows:

IF ...	THEN ...
your system disk is new,	do the following: 1. Enter INITIALIZE. 2. Press the Return key.
you want to remove all files from an existing system disk,	do the following: 1. Enter INITIALIZE. 2. Press the Return key.
you want to retain certain files on an existing disk,	press the Return key to accept the default (PRESERVE).

3.3.3 Specifying the Target Disk

The procedure next asks you for the name of the target disk. If you enter a question mark (?), the system displays a list of devices on your system. Select the appropriate disk and respond to the prompt. For example:

You must enter the device name for the target disk on which
OpenVMS Alpha will be installed.

Enter device name for target disk: (? for choices) DKB400

If you select a device that is not available or that cannot be used for some other reason, the system displays information indicating why the device cannot be used. For example, if you enter MKA500, a tape device, a message similar to the following is displayed:

MKA500 is not a disk device

3.3.4 Specifying the Volume Label

The system then prompts you for the volume label and asks if the information is correct. You can keep the label already assigned to the disk, accept the default label assigned by the system (ALPHASYS), or specify a different volume label (with a limit of 12 characters that can include the letters A to Z, numbers 0 through 9, and the dollar sign($), hyphen (-), and underscore (_) characters).

$Q:\adept8\entities\note.eps$ Note

Compaq strongly recommends that the volume labels for all disks on your system or OpenVMS Cluster have unique labels. If a disk having the same label as the system disk is mounted, various OpenVMS components will not function as intended.

3.3.5 Specifying the On-Disk Structure Level

After you enter the volume label for the target system disk, you will be asked if you want to initialize the target system disk with On-Disk Structure Level 2 (ODS-2) or Level 5 (ODS-5).

    Enter volume label for target system disk: [ALPHASYS] 

       The target system disk can be initialized with On-Disk Structure
       Level 2 (ODS-2) or Level 5 (ODS-5). (? for more information)

   Do you want to initialize with ODS-2 or ODS-5? (2/5/?)

For details about ODS-2 and ODS-5 file systems, refer to the OpenVMS System Manager’s Manual. A brief summary follows:

• ODS-2

ODS-2 allows for full compatibility with all OpenVMS VAX systems and with OpenVMS Alpha systems prior to Version 7.2.

• ODS-5

– ODS-5 supports file names that are longer and have a wider range of legal characters. This feature permits use of file names similar to those in a Windows or UNIX environment.

– ODS-5 supports hard links to files, access dates, and files whose names differ only by case.

– ODS-5 volumes cannot be mounted on any version of OpenVMS prior to Version 7.2.

– Systems running OpenVMS VAX Version 7.2 and later can mount ODS-5 volumes, but cannot create or access files having extended names. (Lowercase file name characters are seen in uppercase on OpenVMS VAX systems.)

Select ODS-2 or ODS-5 by entering 2 or 5 at the prompt. If you select ODS-5, you are asked whether you want to enable hard links. For more information about hard links, refer to the OpenVMS Alpha Version 7.3–1 New Features and Documentation Overview.

        Hard links can be enabled on ODS-5 disks. (? for more information)
        (***Enabling hard links can take up to 5-10 minutes or more.***)

    Do you want to enable hard links? (Yes/No)

Enter Yes or No to indicate your choice. Your target system disk choices are displayed, and you are asked to confirm that they are correct.

       You have chosen to install OpenVMS Alpha on a new disk.

       The target system disk, DKB400:, will be initialized
       with structure level 5 (ODS-5).
       Hard links will NOT be enabled.
       It will be labeled ALPHASYS.
       Any data currently on the target system disk will be lost.

   Is this OK? (Yes/No) Y

         Initializing and mounting target....

       Creating page and swap files....

3.3.6 Setting the SYSTEM Account Password

Before you respond to the system prompt asking you to enter a password for the SYSTEM account, note the following:

• Passwords must be at least eight characters in length; they do not appear on the display.

• Press the Return key after you enter the password.

• After you enter the password, the procedure checks to make sure it meets the requirements for a valid password.

• Reenter the password for verification.

The following is a sample display:

    You must enter a password for the SYSTEM account.

    The password must be a minimum of 8 characters in length,
    and may not exceed 31 characters.
    It will be checked and verified.
    The system will not accept passwords that can be guessed easily.

    The password will not be displayed as you enter it.

Password for SYSTEM account: 

Reenter SYSTEM password for verification:

If you reenter the password incorrectly or if the system determines that the password is too easy for another user to guess, the system displays an error message and gives you the opportunity to specify a valid password.

3.3.7 Becoming a Cluster Member

The procedure now asks if your system will be part of a cluster. The display is similar to the following:

Will this system be a member of an OpenVMS Cluster? (Yes/No) Yes

You should answer Yes if the system will be an OpenVMS Galaxy instance or a member of an OpenVMS cluster. Answering Yes to this question causes SYS$MANAGER:CLUSTER_CONFIG.COM to run automatically when your newly installed system is first booted. The CLUSTER_CONFIG procedure will ask a series of questions about the cluster. Refer to the Guidelines for OpenVMS Cluster Configurations for more information.

If you answer No to the cluster question, the system can still be a member of an OpenVMS Cluster. However, in this case you will have to explicitly configure the cluster when your newly installed system is first booted. You can do this by executing a command similar to the following:

$ @SYS$MANAGER:CLUSTER_CONFIG

For detailed information about cluster configuration, refer to the OpenVMS Cluster Systems manual.

3.3.8 Becoming an OpenVMS Galaxy Instance

The procedure next asks if your system will be an instance in an OpenVMS Galaxy. The display is similar to the following:

Will this system be an instance in an OpenVMS Galaxy? (Yes/No) Yes

If you answer Yes to this question, and you also answered Yes to the OpenVMS Cluster question, information about required remedial kits is displayed.

3.3.9 Installing Windowing and Networking Products

The procedure next asks if you want to install the following Compaq windowing and networking software:

• DECwindows Motif for OpenVMS

• DECnet-Plus for OpenVMS or DECnet Phase IV for OpenVMS (but not both)

• TCP/IP Services for OpenVMS

This software is included with the OpenVMS Alpha operating system. You can change the default values for these products later in the installation procedure.

$Q:\adept8\entities\note.eps$ Note

The OpenVMS Alpha installation menu offers the choice to install either DECnet-Plus for OpenVMS or DECnet Phase IV for OpenVMS networking software. However, you cannot have both installed on your system at the same time. Install one or the other.

Once you have DECnet and TCP/IP installed on your system, you can run DECnet applications over your TCP/IP network. Please see the DECnet-Plus for OpenVMS Management Guide for more information on DECnet over TCP/IP.

The display is similar to the following:

You can install the following products along with the OpenVMS operating 
system:
 
        o DECwindows Motif for OpenVMS Alpha
        o DECnet-Plus for OpenVMS Alpha
        o DECnet Phase IV for OpenVMS Alpha
        o Compaq TCP/IP Services for OpenVMS

    If you want to change your selections, you can do so later in the
    installation by answering "NO" to the following question:
                                
        "Do you want the defaults for all product options?"    

    Do you want to install DECwindows Motif for OpenVMS Alpha V1.2-6?
(Yes/No) [YES] y


    Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with the
    OpenVMS operating system kit.  Compaq recommends that DECnet
    users install DECnet-Plus.  DECnet Phase IV applications are
    supported by DECnet-Plus.

    DECnet Phase IV is also provided as an option.  Support for
    DECnet Phase IV is available through a Prior Version Support
    Contract available through Compaq’s Services.

    If you install DECnet-Plus and TCP/IP  you can run DECnet 
    applications over a TCP/IP network.  Please see the OpenVMS 
    Management Guide for information on running DECnet over TCP/IP.    

    Do you want to install DECnet-Plus for OpenVMS Alpha V7.3-1?
(Yes/No) [YES] y


    Do you want to install Compaq TCP/IP Services for OpenVMS V5.1?
(Yes/No) [YES] n

Note that if you answer No to the prompt to install DECnet-Plus for OpenVMS, you will be prompted to install DECnet Phase IV for OpenVMS.

3.3.10 Setting System Parameters

The procedure now asks you to set values for the parameters SCSNODE and SCSSYSTEMID. SCSNODE is a name that can be from 1 to 6 letters or numbers; it must include at least one letter. If this system is part of an OpenVMS Cluster, SCSNODE must be unique within the cluster. If you are using DECnet Phase IV for OpenVMS or DECnet-Plus for OpenVMS with DECnet Phase IV addresses, then SCSNODE must be the same as your DECnet node name.

SCSSYSTEMID must also be unique within an OpenVMS Cluster. In addition, if you are using DECnet Phase IV for OpenVMS or DECnet-Plus for OpenVMS with DECnet Phase IV addresses, SCSSYSTEMID depends on the DECnet Phase IV address that your system is using.

The following is an example of the display and valid responses:

    For your system to operate properly, you must set two parameters:
    SCSNODE and SCSSYSTEMID.
      
    SCSNODE can be from 1 to 6 letters or numbers.  It must contain at
    least one letter.

    If you plan to use DECnet, SCSNODE must be the DECnet Phase IV
    node name, or the DECnet-Plus node synonym.

    If you have multiple OpenVMS systems, the SCSNODE on each system 
    must be unique.

Enter SCSNODE: alpcsi

    If you plan to use DECnet, SCSSYSTEMID must be set based on the
    DECnet Phase IV address.

    DECnet Phase IV addresses are in the format

        DECnet_area_number.DECnet_node_number

    DECnet_area_number is a number between 1 and 63.
    DECnet_node_number is a number between 1 and 1023.

    If you plan to use DECnet WITHOUT Phase IV compatible addresses, 
    enter 0.0.


Enter DECnet (Phase IV) Address [1.1]: 63.180

    SCSSYSTEMID will be set to 64692.

        This was calculated as follows:

        (DECnet_area_number * 1024) + DECnet_node_number

If you are not using DECnet, or if you enter 0.0 as the DECnet Phase IV address, you are prompted to enter a SCSSSYSTEMID in the range of 1 to 65535. If this is a standalone system, the default 65534 is acceptable. However, if this system is part of an OpenVMS Cluster, you must enter a unique SCSSYSTEMID. The following is a sample display:

   Please choose a SCSSYSTEMID between 1 and 65535.  If you have multiple
   OpenVMS systems, the SCSSYSTEMID on each system must be unique.

Enter SCSYSTEMID [65535]: 12345

3.3.11 Setting Time Zone Information

At this point in the installation, the procedure asks you for information that is used for providing local time zone support. Time zone information is always set on new installations. It may be set on upgrades. (See Section 7.2.10.)

For local time zone support to work correctly, the installation procedure must set the time zone that accurately describes the location you want to be considered as your default time zone. Usually, this is the time zone in which your system is running. In addition, your system must be correctly configured to use a valid OpenVMS time differential factor (TDF).

The procedure displays a series of time zone menus and prompts you to make selections from each. Begin by selecting the desired time zone from the main time zone menu.

If you choose a time zone that has subcomponents, the system displays an additional menu. For example, if you choose the United States (US) time zone from the main menu, a second menu displays the specific time zones within the United States. You then select the menu item that best represents the desired time zone.

The procedure then prompts you for the TDF. The TDF is the difference between your system time and Coordinated Universal Time (UTC), which is an international standard (similar to Greenwich Mean Time) for measuring time of day. The procedure supplies a default for TDF, which is generally the correct response.

The following is a sample display:

  Configuring the Local Time Zone


  TIME ZONE SPECIFICATION -- MAIN Time Zone Menu

      1) AFRICA               16) GREENWICH            31) POLAND
      2) AMERICA              17) HONGKONG             32) PRC
      3) ANTARCTICA           18) ICELAND              33) ROC
      4) ASIA                 19) INDIAN               34) ROK
      5) ATLANTIC             20) IRAN                 35) SINGAPORE
      6) AUSTRALIA            21) ISRAEL               36) SYSTEMV
      7) BRAZIL               22) JAMAICA              37) TURKEY
      8) CANADA               23) JAPAN                38) UCT
      9) CET                  24) LIBYA                39) UNIVERSAL
     10) CHILE                25) MET                  40) US
     11) CUBA                 26) MEXICO               41) UTC
     12) EET                  27) NAVAJO               42) W-SU
     13) EGYPT                28) NZ-CHAT              43) WET
     14) FACTORY              29) NZ                   44) ZULU
     15) GB-EIRE              30) PACIFIC

      0) GMT

Select the number above that best represents the desired time zone: 40

  US Time Zone Menu

      1) ALASKA                5) EAST-INDIANA          9) MICHIGAN
      2) ALEUTIAN              6) EASTERN              10) MOUNTAIN
      3) ARIZONA               7) HAWAII               11) PACIFIC
      4) CENTRAL               8) INDIANA-STARKE       12) SAMOA

      0) return to Main Time Zone Menu

Select the number above that best represents the desired time zone: 6

You selected EASTERN / US as your time zone.
Is this correct? (Yes/No) [YES]:

    Configuring the Time Differential Factor (TDF)


    Default Time Differential Factor for standard time is -5:00.
    Default Time Differential Factor for daylight saving time is -4:00.


    The Time Differential Factor (TDF) is the difference between your
    system time and Coordinated Universal Time (UTC).  UTC is similar
    in most respects to Greenwich Mean Time (GMT).

    The TDF is expressed as hours and minutes, and should be entered
    in the hh:mm format.  TDFs for the Americas will be negative
    (-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia and Australia
    will be positive (1:00, 2:00, etc.).

This time zone supports daylight saving time.
Is this time zone currently on daylight saving time? (Yes/No): n

Enter the Time Differential Factor [-5:00]:

    NEW SYSTEM TIME DIFFERENTIAL FACTOR = -5:00

Is this correct? [Y]:

For more information about TDF and local time zone support, see the OpenVMS System Manager’s Manual.

3.4 Registering Licenses

Before you can use the OpenVMS Alpha operating system and its components, you must register all licenses in one of two ways:

• During the installation (which Compaq recommends), by responding to the prompts displayed by the SYS$UPDATE:VMSLICENSE.COM procedure. This procedure is executed if you answer Yes (the default) to the following question:

	     Do you want to register any Product Authorization Keys?

• After the installation, by using the LICENSE REGISTER command or by invoking SYS$UPDATE:VMSLICENSE.COM.

In addition to reviewing the license information provided in this chapter, you can also refer to the following:

• Appendix C, which contains notes and supplemental information about licenses and licensing procedures

• The OpenVMS License Management Utility Manual, which contains complete, detailed information about the licensing procedure

3.4.1 Types of OpenVMS Alpha Licenses

The operating system uses one or more of the following types of licenses, depending on your hardware and software configuration.

$Q:\adept8\entities\note.eps$ Note

All OpenVMS Alpha Base and SMP licenses include the NO_SHARE attribute and remain with the initial host computer.

Table 3–3 Types of OpenVMS Alpha Licenses

Type of License	Description
Operating System Base License	Grants the right to noninteractive use of the remote batch, print, application, and computing services of the operating system on a single processor and authorizes one direct login (for system management purposes only). This license is a prerequisite for OpenVMS Alpha Interactive User Licenses.
Interactive User Licenses	Grant the right to interactive use of the OpenVMS Alpha operating system, provided you have previously installed the appropriate OpenVMS Alpha Operating System Base License on your Alpha computer. These licenses, which are concurrent, are available in any quantity desired or as an unlimited user license. You can add interactive users to the computer at any time by specifying the same node name on the additional Interactive User License PAK and by following the license combination procedure described in the OpenVMS License Management Utility Manual.
Symmetric Multiprocessing (SMP) Extension to the Operating System Base License	Upgrades the Operating System Base License and all Interactive User licenses (including Unlimited) to the matching multiprocessing level of your Alpha SMP system. Because the Symmetric Multiprocessing (SMP) Extension grants all the rights the existing Base and User licenses provided at the uniprocessing level, you do not need to reinstall those licenses when you upgrade to a multiprocessing system. Each time you upgrade your system to a new multiprocessing level (for example, from a DEC 7000 Model 620 Alpha system to a DEC 7000 Model 630 Alpha system), you add an SMP Extension to your existing licenses.

3.4.2 How to Register Licenses

After you install the OpenVMS Alpha operating system, the system displays the following message:

    If you have Product Authorization Keys (PAKs) to register,
    you can register them now.

Do you want to register any Product Authorization Keys? (Yes/No) [Yes]

Respond to the prompt as follows:

IF ...	THEN ...
you choose to register your licenses at this time (which Compaq recommends),	do the following: 1. Be sure you review Appendix C and have the OpenVMS License Management Utility Manual available. 2. Be sure you have a copy of the Product Authorization Key (PAK) for each license that you will register. 3. Type Y and press the Return key. 4. Register your licenses, as described in the next section.
you choose not to register your licenses at this time,	do the following: 1. Type N and press the Return key. 2. Skip the next section about registering licenses and follow the directions in Section 3.5. 3. After completing the installation, register your licenses using the LICENSE REGISTER command or by invoking SYS$UPDATE:VMSLICENSE.COM before performing any other postinstallation tasks.

3.4.3 Using the Licensing Procedure

Entering Y (Yes) to register your licenses during the installation invokes the SYS$UPDATE:VMSLICENSE.COM procedure, which displays the following message:

VMS License Management Utility Options:
     
    1. REGISTER a Product Authorization Key
    2. AMEND an existing Product Authorization Key
    3. CANCEL an existing Product Authorization Key
    4. LIST Product Authorization Keys
    5. MODIFY an existing Product Authorization Key
    6. DISABLE an existing Product Authorization Key
    7. DELETE an existing Product Authorization Key
    8. COPY an existing Product Authorization Key
    9. MOVE an existing Product Authorization Key
   10. ENABLE an existing Product Authorization Key
   11. SHOW the licenses loaded on this node
   12. SHOW the unit requirements for this node
            
   99. Exit this procedure

   Type ’?’ at any prompt for a description of the information 
   requested. Press Ctrl/Z at any prompt to return to this menu.
     
Enter one of the above choices [1]

1. Select the appropriate options (beginning with 1, as indicated in the display) until you have successfully registered all required PAKs.

2. After you register all your licenses, exit from the License Management procedure by entering option 99.

3.5 Completing the Installation

The following sections describe the remaining steps that you need to perform to complete the installation.

3.5.1 Choosing Descriptive Help Text

Next, the system prompts you as follows:

The installation can provide brief or detailed descriptions.
In either case, you can request the detailed descriptions by typing "?".

Do you always want detailed descriptions? (Yes/No) [No]

If you answer Yes, the system will display additional explanatory text with each prompt.

3.5.2 Selecting Components

The system next displays the following message, indicating that the procedure is ready to install the operating system:

The following product has been selected:
    DEC AXPVMS OPENVMS V7.3-1                    Platform (product suite)
 

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.
 
DEC AXPVMS OPENVMS V7.3-1: OpenVMS and related products Platform
 
    COPYRIGHT (c) 27-MAY-2002 -- All rights reserved
 
    Compaq Information Technologies Group, L.P.

After the system displays a series of additional messages, the procedure prompts you to choose the default values for all the options and suboptions for each component included in the operating system. The display is similar to the following:

    Do you want the defaults for all options? [YES]

When selecting components, note the following:

• If you want all the default values, press the Return key.

If you want to select components individually, answer NO. The system will then prompt you for each option and suboption.

• You should review the list of options and compare them with the requirements for your system. If you are selecting components individually, be sure that you include all components necessary to support the needs of your users. Note also that certain components are dependent upon the installation of other components.

• If you are not sure whether you want certain options, request help by entering a question mark (?) at the prompt for that option.

• After you select all the options you want, you will have an opportunity to view your selections and make changes (if necessary).

• OpenVMS Management Station software is automatically installed on your OpenVMS system disk when you accept all the default values. If you do not accept the default values, you must select the OpenVMS Management Station component (server and client files) if you plan to use that product. After the installation is complete, you can then prepare your OpenVMS Alpha system and your PC to run OpenVMS Management Station by following the procedures described in Appendix D.

• If you decide after the installation to change which OpenVMS Alpha operating system options you want installed on your system, you must reconfigure the installation as described in Section 1.3.3.2 and Section 4.10.

• After you boot the new system disk and log in, you can obtain information about individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($).

$Q:\adept8\entities\note.eps$ Note

Unless you have specific reasons to do otherwise, Compaq recommends that you accept the defaults and install all OpenVMS options. OpenVMS and layered products have various dependencies on many of these options. Even if you think you do not need certain options, some OpenVMS or layered product operations may not work correctly if other OpenVMS options are not installed.

3.5.3 List of Components

The following components are included with the OpenVMS Alpha Version 7.3–1 operating system:

    Accounting Log Report Generator Utility
    Access Control List Utilities 
    Print and Batch Queue Utilities
    DECdtm Distributed Transaction Manager
    LDAP (Lightweight Directory Access Protocol) files
    Support for DECnet-Plus or DECnet for OpenVMS
        DECnet Incoming Remote File Access
        DECnet Incoming Remote Terminal
        DECnet Network Test
        DECnet Remote Task Loading
    Programming Support
        Debugger Utility
        Image Dump Utility
        RMS Analyze and FDL Editor Utilities
        Message Utility
        System Shareable Image and Object Module Libraries
        Macro libraries
        Macro-32 Migration Compiler
        TLB intermediary form of STARLET
        Fortran Require Files
        C Object Libraries
        C Header Files
        VMS text libraries of Ada declarations
    RMS Journaling Recovery Utility
    System Programming Support
        Support for ISO 9660 and High Sierra CDrom Formats
        MONITOR
        Analyze Object File Utility
        Delta Debugger
        System Dump Analyzer Utility
        Miscellaneous Symbol Table Files
    OpenVMS Management Station Software -- PC files
    Utilities
        OpenVMS Mail Utility
        Dump Utility
        DIGITAL Standard Runoff (DSR) Text Formatter
        Phone Utility
        Help Library
        Foreign Terminal Support
        LAT-11 Terminal Server (via Ethernet)
        Error Log Generator Utility
        Terminal Fallback Facility
        TECO Interactive Text Editor
        National Character Set Utility (NCS)
        DIAGNOSE Utility
        XPG4 Internationalization Utilities
        World Wide PostScript Printing Subsystem
    Bliss Require Files
    Example Files
    Message Facility Files (HELP/MESSAGE)
    Translated Image Support
    UETP Files
    Support for DECwindows
        DECwindows workstation files
        Video fonts
            100 dots-per-inch video fonts
    Delete any obsolete OpenVMS files
    Delete files archived by OpenVMS remedial kits

3.5.4 Completing the Procedure

When you have answered all the prompts and selected the components you want installed, the system allows you to review your selections (and make changes if necessary), then installs the product, provides informational messages, and returns you to the menu. The following is a sample display:

$Q:\adept8\entities\note.eps$ Note

If you perform two installations at the same time to systems connected by MEMORY CHANNEL, you may see a message similar to the following every 5 seconds:

             
%PMA0 CPU00: 30-MAY-2002 14:58:40 Remote System Conflicts with 
Known System - REMOTE NODE
%PMA0 CPU00: 30-MAY-2002 14:58:45 Remote System Conflicts with 
Known System - REMOTE NODE

Disregard the message. The installation or upgrade will proceed normally and the messages will not be present when the system reboots with its actual node name.

    Do you want to review the options? [NO] 

Execution phase starting ...

The following products will be installed to destinations:
    CPQ AXPVMS CDSA V1.0                  DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS DECNET_OSI V7.3-1          DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS DWMOTIF V1.2-6             DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS OPENVMS V7.3-1             DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS TCPIP V5.1                 DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS VMS V7.3-1                 DISK$ALPHASYS:[VMS$COMMON.]

Portion done: 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100%

The following products have been installed:
    CPQ AXPVMS CDSA V1.0                   Layered Product
    DEC AXPVMS DECNET_OSI V7.3-1           Layered Product
    DEC AXPVMS DWMOTIF V1.2-6              Layered Product
    DEC AXPVMS OPENVMS V7.3-1              Platform (product suite)
    DEC AXPVMS TCPIP V5.1                  Layered Product
    DEC AXPVMS VMS V7.3-1                  Operating System

    The installation is now complete.

    When the newly installed system is first booted, a special
    startup procedure will be run.  This procedure will:

    o  Configure the system for standalone or OpenVMS Cluster operation.
    o  Run AUTOGEN to set system parameters.
    o  Reboot the system with the newly set parameters.


    You may shut down now or continue with other operations.


  Process AXPVMS_INSTALL logged out at 27-MAY-2002 14:45:49.54

Press Return to continue...

    ****************************************************************

    You can install or upgrade the OpenVMS Alpha operating system
    or you can install or upgrade layered products that are included
    on the OpenVMS Alpha operating system CD-ROM.
    
    You can also execute DCL commands and procedures to perform
    "standalone" tasks, such as backing up the system disk.
    
    Please choose one of the following:

        1)  Install or upgrade OpenVMS Alpha Version 7.3-1
        2)  Display products and patches that this procedure can install
        3)  Install or upgrade layered products and patches
        4)  Show installed products
        5)  Reconfigure installed products
        6)  Remove installed products
        7)  Execute DCL commands and procedures
        8)  Shut down this system

    Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?)

If you want to install layered products, go to Section 3.6.

If you do not want to install layered products or perform any other operations prior to booting the new system disk, choose option 8 from the menu to shut down the system. The system display is similar to the following:

Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 8

Shutting down the system

SYSTEM SHUTDOWN COMPLETE

After you complete the installation and shut down the system, go to Section 3.7.

3.6 Installing Layered Products

You can use the menu system included on the operating system CD–ROM to install certain layered products with the POLYCENTER Software Installation utility. You can view a list of the layered products that can be installed in this way by choosing option 2 from the menu. (To install layered products that are not listed, see Chapter 4, After Installing the OpenVMS Alpha Operating System and the installation documentation for each layered product.)

You may see the following product name while installing layered products:

        DEC AXPVMS UCX V4.2-PLACEHOLDER

Do not attempt to install this kit. This is a "dummy" that is needed to facilitate upgrading from the prior UCX implementation of TCP/IP Services for OpenVMS to the new implementation.

If you do attempt to install this kit, the following message will be displayed:

          The UCX implementation of TCP/IP Services is obsolete and is not
          supported on OpenVMS V7.2 and higher versions.

          Starting with OpenVMS V7.2, the UCX implementation of TCP/IP
          services is replaced by the new TCPIP product.

          This is a placeholder kit to satisfy OpenVMS upgrade requirements
          so that UCX can be automatically upgraded to TCPIP.

          You cannot use this kit to install UCX.

The installation will then terminate.

You can install (or upgrade to) the new implementation of TCP/IP Services for OpenVMS, Version 5.1, as part of the OpenVMS upgrade. If you want to install Version 5.1 separately, choose the product:

        DEC AXPVMS TCPIP V5.1

To install layered products using the POLYCENTER Software Installation utility, choose option 2 to view the list and then option 3 to perform the installation. For example:

Please choose one of the following:

        1) Upgrade, install or reconfigure OpenVMS Alpha Version 7.3-1
        2) Display products and patches that this procedure can install
        3) Install or upgrade layered products and patches
        4) Show installed products
        5) Reconfigure installed products
        6) Remove installed products
        7) Execute DCL commands and procedures
        8) Shut down this system

        Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 2

            The following versions of the OpenVMS operating system, the
            DECwindows graphical user interface and network products.
            are available on the OpenVMS Distribution compact disk.
            They can be installed by selecting choice 1:

        DEC AXPVMS VMS version V7.3-1
        DEC AXPVMS DWMOTIF version V1.2-6
        DEC AXPVMS DECNET_OSI version V7.3-1
        DEC AXPVMS DECNET_PHASE_IV version V7.3-1
        DEC AXPVMS TCPIP version V5.1

            The following Layered Product kits are available on the OpenVMS
            Distribution Compact Disk.  They can be installed by selecting
            choice 3.  If already installed, they can be reconfigured by
            selecting choice 5, or removed by selecting choice 6.
        ----------------------------------- ----------- ----------
        PRODUCT                             KIT TYPE    KIT FORMAT
        ----------------------------------- ----------- ----------
        DEC AXPVMS DECNET_OSI V7.3-1        Full LP     Sequential
        DEC AXPVMS DECNET_PHASE_IV V7.3-1   Full LP     Sequential
        DEC AXPVMS DWMOTIF V1.2-6           Full LP     Sequential
        DEC AXPVMS TCPIP V5.1               Full LP     Sequential
        DEC AXPVMS UCX V4.2-99PLACEHOLDER   Full LP     Sequential
        ----------------------------------- ----------- ----------

        5 items found

        Press Return to continue...

            ****************************************************************

            You can install or upgrade the OpenVMS Alpha operating system
            or you can install or upgrade layered products that are included
            on the OpenVMS Alpha operating system CD-ROM.

            You can also execute DCL commands and procedures to perform
            "standalone" tasks, such as backing up the system disk.

            Please choose one of the following:

        1) Upgrade, install or reconfigure OpenVMS Alpha Version 7.3-1
        2) Display products and patches that this procedure can install
        3) Install or upgrade layered products and patches
        4) Show installed products
        5) Reconfigure installed products
        6) Remove installed products
        7) Execute DCL commands and procedures
        8) Shut down this system

        Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 3
            ***********************************************************

            If you choose to install or upgrade DECwindows Motif,
            please note the following:

              o If you did not select the OpenVMS DECwindows base support
                and workstation files options, DECwindows Motif will not run.
                You must add these options to use DECwindows Motif.

              o If you are upgrading DECwindows Motif from version V1.1 and
                want to save the OSF/Motif Release 1.1.3 programming files,
                DO NOT upgrade now.  Instead, see the DECwindows Motif
                installation manual and follow the instructions for running
                PCSI_INSTALLATION.COM.

            If you choose to install or upgrade DECnet-Plus or DECnet Phase IV,
            please note the following:

        o If you did not select the OpenVMS DECNET option, neither version
          of DECnet will run.  You must add this option to use DECnet.

        Press Return to continue...
           ***********************************************************

            The installation procedure will ask a series of questions.

                  () - encloses acceptable answers
                  [] - encloses default answers

            Type your response and press the Return key.  Type:

                  ? - to repeat an explanation
                  ^ - to change prior input (not always possible)
                  Ctrl-Y - to exit the installation procedure

            You must enter the device name for the target disk on which
            the layered product(s) installation will be performed.

        Enter device name for target disk: [DKB400:] (? for choices)

            DKB400: is labeled V73_TCPIPV51.

            The install operation can provide brief or detailed descriptions.
            In either case, you can request the detailed descriptions by typing
            "?".

        Do you always want detailed descriptions? (Yes/No) [No]
           1 - DEC AXPVMS DECNET_OSI V7.3-1        Layered Product
           2 - DEC AXPVMS DECNET_PHASE_IV V7.3-1   Layered Product
           3 - DEC AXPVMS DWMOTIF V1.2-6           Layered Product
           4 - DEC AXPVMS TCPIP V5.1               Layered Product
           5 - DEC AXPVMS UCX V4.2-99PLACEHOLDER   Layered Product
           6 - All products listed above
           7 - Exit

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

Note that the UCX V4.2-99PLACEHOLDER kit is not a valid UCX (TCP/IP) kit. It is present only to support upgrading UCX to the new TCPIP implementation of TCP/IP Services for OpenVMS. Any attempt to install this PLACEHOLDER kit will terminate with an error.

If you do not want to perform any other operations after you install the layered products, enter option 8 to shut down the system. The system display is similar to the following:

Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 8

Shutting down the system

SYSTEM SHUTDOWN COMPLETE

After you complete the installation and shut down the system, go to the next section to boot the new system disk.

3.7 Booting the New System Disk

After you have successfully installed the operating system, boot the new system disk, as described in the following sections.

3.7.1 Preparing to Boot the New System Disk

Before you boot the new system disk, you must do the following:

1. Halt the system by entering Ctrl/P or by pressing the Halt button.^{1 (SEE NOTE)}

2. At the console prompt (>>>), enter the SET BOOTDEF_DEV command in the following format:

SET BOOTDEF_DEV target-drive

Substitute the device name of the system disk for target-drive. The SET BOOTDEF_DEV command tells the system which disk to boot from. For example, if the system disk has the device name DKA400, enter the following command and press the Return key:

>>> SET BOOTDEF_DEV DKA400

If the system disk is connected to a hierarchical storage device (HSx), the format for specifying that drive is different. For example, on a DEC 7000 series system connected to an HSC device, the command is similar to the following:

>>> SET BOOTDEF_DEV DUA20.14.0.2.0

For more information about setting and showing the default boot device, see Appendix A.

3.7.2 How to Boot the New System Disk

To boot the system disk, enter the following command and press the Return key:

>>> BOOT -FLAGS 0,0

When the system finishes booting, it displays informational messages that begin as follows:

    OpenVMS (TM) Alpha Operating System, Version 7.3-1

%DECnet-I-LOADED, network base image loaded, version = 05.0D.00

$!  Copyright (c) 2002 Compaq Information Technologies Group, L.P.  
$!  All rights reserved.

    Installing required known files...

    Configuring devices...
.
.
.

3.8 Joining an OpenVMS Cluster

If during the installation, you previously answered Yes to the question about joining an OpenVMS Cluster, the system now asks a series of questions about your configuration (CI, DSSI, SCSI, local area, or mixed-interconnect).

You might need to refer to OpenVMS Cluster Systems or Guidelines for OpenVMS Cluster Configurations to answer these questions.

3.8.1 OpenVMS Cluster Prompts

Table 3 –5 lists the OpenVMS Cluster prompts and suggested responses. Note that, depending on your responses and particular cluster configuration, some prompts will not be displayed.

Table 3–5 Prompts for OpenVMS Cluster Configurations

Question	How to Respond
Will this node be a cluster member (Y/N)?	Enter Y.
What is the node’s DECnet node name?	Enter the DECnet node name (for example, MYNODE). The DECnet node name may be from one to six alphanumeric characters in length and cannot include dollar signs or underscores.
What is the node’s DECnet node address?	Enter the DECnet node address --- for example, 2.2.
Will the Ethernet be used for cluster communications (Y/N)?	Enter N for a CI only or DSSI-only OpenVMS Cluster. Otherwise, answer Y. ^{2 (SEE NOTE)}
Enter this cluster’s group number:	Enter a number in the range from 1 to 4095 or 61440 to 65535.
Enter this cluster’s password:	Enter the cluster password. The password must be from 1 to 31 alphanumeric characters in length and may include dollar signs and underscores.^{3 (SEE NOTE)}
Reenter this cluster’s password for verification:	Reenter the password.
Will MYNODE be a disk server (Y/N)?	Enter Y if you want local disks to be served to the cluster (mandatory for local area and mixed-interconnect configurations). Refer to OpenVMS Cluster Systems for information about served cluster disks.
Will MYNODE serve RFxx disks (Y)?	Enter a response appropriate for your DSSI configuration, if such disks are available to your system.
Enter a value for MYNODE’s ALLOCLASS parameter:	In a CI only system (connected to a dual-ported disk), a DSSI-only system, or a local area or mixed-interconnect configuration where nodes serve DSSI or CI disks, enter the appropriate allocation class value (1 to 255). Otherwise, enter 0. For information about selecting the ALLOCLASS parameter, see OpenVMS Cluster Systems.
Does this cluster contain a quorum disk (Y/N)?	For CI only, SCSI, local area, and mixed-interconnect configurations, enter Y or N, depending on your configuration. For most DSSI systems, enter Y. However, if you are adding a two-system DSSI configuration to an existing cluster (in which case you might not need a quorum disk), you can answer N. If you enter Y, the system asks for the name of the quorum disk. Enter the device name of the quorum disk. Refer to OpenVMS Cluster Systems for information about quorum disks.

3.9 Running AUTOGEN

The system next runs AUTOGEN to evaluate your hardware configuration and estimate typical work loads. AUTOGEN then sets system parameters, the sizes of page, swap, and dump files, and the contents of VMSIMAGES.DAT. When AUTOGEN finishes and you reboot your system, the installation procedure is complete.

The installation procedure displays messages similar to the following:

    AUTOGEN will now be run to compute the new SYSGEN parameters. The system
    will then shut down and reboot, and the installation or upgrade will be
    complete.

    After rebooting you can continue with such system management tasks as:

            Decompressing the System Libraries
            Configuring DECnet
            Using SYS$MANAGER:CLUSTER_CONFIG.COM to create an OpenVMS Cluster
            Creating FIELD, SYSTEST, and SYSTEST_CLIG accounts if needed

%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
        You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
         You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
        You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;1 extended
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1 created

%AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages that
        have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may
        wish to review the information in that file.

%AUTOGEN-I-END, GENFILES phase has successfully completed.
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.
.
.
.

3.9.1 Automatic Reboot after Autogen

After AUTOGEN finishes, the system shuts down, displaying messages similar to the following:

The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.

The system will automatically reboot after the shutdown and the
installation will be complete.



        SHUTDOWN -- Perform an Orderly System Shutdown
                    on node ALPCSI

%SHUTDOWN-I-BOOTCHECK, performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, basic reboot consistency check completed
.
.
.

3.9.2 Manual Reboot after Autogen

If the system does not reboot automatically, reboot the system manually.

For example, if the system disk is on an RZ25 disk drive with a unit number of 1, enter the following command and press the Return key:

>>> BOOT DKA1

After the system reboots, a message similar to the following is displayed:

     OpenVMS (TM) Alpha Operating System, Version 7.3-1

    Copyright (c) 2002 -- All rights reserved.

    Compaq Information Technologies Group, L.P.
    
%STDRV-I-STARTUP, OpenVMS startup begun at 27-MAY-2002 14:50:18.35
.
.
.

The system next displays informational messages and accounting information indicating that your OpenVMS Alpha operating system is running. For example:

%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
  SYSTEM       job terminated at  27-MAY-2002 14:51:23.47

  Accounting information:
  Buffered I/O count:            2177         Peak working set size:   6848
  Direct I/O count:              1358         Peak page file size:   179552
  Page faults:                   1805         Mounted volumes:            0
  Charged CPU time:     0 00:00:13.37         Elapsed time:   0 00:01:06.20

At this time, you can log in to the SYSTEM account (so you can perform postinstallation tasks), as described in the following sections.

3.10 Logging in to the SYSTEM Account from a Character Cell Terminal

Log in to a character cell terminal by entering the user name SYSTEM followed by the password. The display is similar to the following:

OpenVMS (TM) Alpha Operating System, Version 7.3-1

Username: SYSTEM
Password:
.
.
.
      OpenVMS (TM) Alpha Operating System, Version 7.3-1

If you forget your password, follow the instructions in Appendix A to perform an emergency startup.

3.11 Logging in to the SYSTEM Account from a Workstation

If you installed the DECwindows Motif for OpenVMS software on your workstation, do the following after the login window displays on your screen:

1. Enter the user name SYSTEM followed by the password.

2. Click on the OK button.

3.12 Postinstallation Tasks

After you have successfully installed the OpenVMS Alpha operating system and logged in to the SYSTEM account, you must perform certain postinstallation tasks before you can use the system. For complete information, go to Chapter 4, After Installing the OpenVMS Alpha Operating System.

4 After Installing the OpenVMS Alpha Operating System

After you have installed the OpenVMS Alpha operating system, you must perform several important tasks to prepare the system for operation. This chapter describes the following postinstallation tasks in the order in which you perform them:

• Registering licenses

• Creating accounts

• Backing up the system disk

• Customizing the system

• Initializing CDSA

• Configuring and starting networking software

• Testing the system with UETP

• Expanding the system libraries

• Adding and removing files

• Preparing your OpenVMS Alpha system and your PC to run OpenVMS Management Station

• Installing layered products

• Installing OpenVMS Debugger clients on a PC

• Backing up the customized system disk

• Configuring a multihead system

• Running AUTOGEN

• Using the postinstallation checklist

4.1 Registering Your Licenses

The installation procedure gave you the opportunity to register any software product licenses. If you did not register your OpenVMS Alpha licenses at that time, you must do so before you can use the OpenVMS Alpha operating system. You must also register the licenses for OpenVMS Alpha layered products.

You can invoke the OpenVMS License utility by entering the following command:

$ @SYS$UPDATE:VMSLICENSE

(You can also use the LICENSE REGISTER command.)

For information about registering licenses, see the following:

• Section 3.4

• Appendix C

• The OpenVMS License Management Utility Manual

4.2 Creating Accounts

During the installation, DEFAULT and SYSTEM accounts are created for you automatically. However, if you plan to have Compaq service representatives test your system or if you plan to run testing software such as UETP, you must create accounts for each representative and a SYSTEST (standalone system) or SYSTEST_CLIG (OpenVMS Cluster system) account to run UETP.

For complete information about creating accounts for Compaq service representatives and UETP, see the OpenVMS System Manager’s Manual.

4.3 Backing Up Your System Disk

After you install the operating system, protect your work by making a backup copy of the system disk in case you have any problems while customizing it.

To back up the system disk:

1. Shut down the system (described in Appendix A ).

2. Boot the operating system CD–ROM (locally or from the InfoServer).

3. Use the menu system to enter the DCL environment (option 7).

4. Mount the system disk and the target device on which you will make the backup copy.

5. Enter backup commands to back up the system disk to supported media.

6. Log out from the DCL environment.

7. Shut down the system by selecting option 8 from the menu.

8. Boot from the system disk.

In addition to backing up the system disk now before you customize it, you should back up your system disk again after you successfully complete your customization tasks and install layered products.

For complete information about backup operations, including a description of an alternate method that does not require booting from the operating system CD–ROM and that allows you to back up a shadowed disk without disabling the shadow set, see Appendix B.

4.4 Customizing the System

You can customize the system to meet your site-specific needs. In addition, if your Alpha computer is part of an OpenVMS Cluster environment, you must prepare the cluster environment and configure the cluster.

For instructions on customizing the system, review the following documentation:

• OpenVMS Cluster Systems (if the computer is part of an OpenVMS Cluster environment)

• The release notes, for notes and restrictions that might be relevant to your customization plans

• The OpenVMS System Manager’s Manual, for instructions on customizing and using your system. You will find information about the following tasks:

– Editing the template files SYCONFIG.COM, SYLOGICALS.COM, SYLOGIN.COM, and SYSTARTUP_VMS.COM

– Starting the queue manager and creating a queue database

– Setting up user accounts

– Adjusting system parameters

– Setting up your system to run DECdtm services

• Section 4.7, for information about configuring and starting networking software

$Q:\adept8\entities\note.eps$ Note

If you have installed the DECwindows Motif for OpenVMS layered product (see Section 4.12 ), you can customize your DECwindows environment.

4.5 Initializing CDSA

The Common Data Security Architecture (CDSA) is automatically installed with the operating system. However, before you can use CDSA, you must perform the following one-time, manual setup and initialization procedure. You must have SYSPRV privileges to do this.

1. Increase your FILLM process quota by 100 before you initialize CDSA.

2. Execute the following command:

$ @SYS$STARTUP:CDSA$INITIALIZE

If you attempt to run this procedure when it has been run previously, you will get an error message.

$Q:\adept8\entities\note.eps$ Note

Do not attempt to remove CDSA from your system. The PRODUCT REMOVE command is not supported for CDSA even though there appears to be an option to remove CDSA. CDSA is installed with the operating system and is tightly bound with it. Any attempt to remove it will not work cleanly, and could create other undesirable side effects. An attempt to remove it results in the following message:

%PCSI-E-HRDREF, product CPQ AXPVMS CDSA Vn.n is referenced
by DEC AXPVMS OPENVMS V7.3-1
-PCSI-E-HRDRF1, the two products are tightly bound by this
software dependency

For more information about CDSA, refer to Open Source Security for OpenVMS Alpha, Volume 1: Common Data Security Architecture.

4.6 Configuring Kerberos

Kerberos Version 1.0 for OpenVMS Security Client, based on MIT Kerberos V5 Release 1.0.5, is now integrated into the OpenVMS Alpha Version 7.3-1 operating system. Previously, Kerberos was shipped as a layered product.

To configure Kerberos, perform the following steps from a privileged OpenVMS username (for example, SYSTEM).

1. Insert the following line into SYS$MANAGER:SYSTARTUP_VMS.COM. This line must be entered after the startup command for Compaq TCP/IP Services for OpenVMS. (If you start Compaq TCP/IP Services for OpenVMS as a batch job, be sure that TCP/IP has started before you start Kerberos.)

$ @SYS$STARTUP:KRB$STARTUP.COM

2. Add the following line to your SYLOGIN command procedure, or into the LOGIN.COM of each user who will use Kerberos.

$ @SYS$MANAGER:KRB$SYMBOLS

3. Run the following command procedure to configure the Kerberos clients and servers.

$ @SYS$STARTUP:KRB$CONFIGURE.COM

Refer to the Kerberos for OpenVMS Security Client Installation Guide and Release Notes for additional setup and configuration information. This document contains links to the MIT Kerberos documentation, and is available from the OpenVMS Alpha Version 7.3-1 documentation CD-ROM.

4.7 Configuring and Starting Networking Software

The following sections describe how to configure and start your networking software.

4.7.1 DECnet-Plus for OpenVMS

If you installed DECnet-Plus for OpenVMS software, refer to the DECnet-Plus for OpenVMS Release Notes and DECnet-Plus for OpenVMS Installation and Basic Configuration for postinstallation instructions.

4.7.2 DECnet Phase IV for OpenVMS

$Q:\adept8\entities\note.eps$ Note

Support for DECnet Phase IV is available only under Compaq’s Prior Version Support Program. Contact your local Compaq support representative for additional information.

If you plan to run DECnet Phase IV for OpenVMS software, note the following:

• After you have registered the license for the DECnet Phase IV for OpenVMS software, execute the interactive command procedure SYS$MANAGER:NETCONFIG.COM to automatically configure your system for networking. See the DECnet for OpenVMS Guide to Networking for instructions on using NETCONFIG.COM.

• After you start the queue manager (see the OpenVMS System Manager’s Manual), edit the commands in SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM that pertain to networking so that the DECnet Phase IV for OpenVMS software starts automatically when your system is booted. Edit the file as follows:

– If you have batch queues set up on your system, choose the following command by removing the comment delimiter (!) from the command line. Enabling this command allows the system to start up more quickly and decreases the amount of time you must wait to log in.

!$ SUBMIT SYS$MANAGER:STARTNET.COM

– If you do not have batch queues set up on your system, remove the comment delimiter (!) from the following lines:

$! DECNET_VERSION = F$INTEGER(F$EXTRACT(2,2,F$GETSYI("DECNET_VERSION") ) )
$! IF DECNET_VERSION .GE. 5
$!     THEN 
$!         START/NETWORK "DECNET/OSI"$!     ELSE 
$!         START/NETWORK DECNET
$! ENDIF

• If you plan to run both DECnet Phase IV for OpenVMS and DECwindows software, you must also edit SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM to add a comment delimiter (!) immediately following the dollar sign ($) in the following command:

$ DEFINE DECW$IGNORE_DECNET TRUE

If you are not going to start the DECnet Phase IV for OpenVMS software or have not yet started it, this command tells the DECwindows software not to wait for the DECnet Phase IV for OpenVMS software.

4.7.3 Compaq TCP/IP Services for OpenVMS

If you installed TCP/IP Services for OpenVMS software, refer to the Compaq TCP/IP Services for OpenVMS Installation and Configuration manual for information about how to configure this software using the TCPIP$CONFIG.COM procedure.

4.8 Testing the System with UETP

The User Environment Test Package (UETP) is a software package designed to test whether the OpenVMS Alpha operating system is installed correctly. As part of the postinstallation procedure, Compaq recommends that you run UETP to verify the installation.

For complete information about using UETP, see the OpenVMS System Manager’s Manual.

4.9 Expanding the System Libraries

Some of the larger system libraries ship with the OpenVMS operating system in a data-reduced (compressed) format. Expanding (that is, decompressing) these libraries gives the system faster access to them, but also consumes more disk space. Table 4 –1 lists the libraries that ship in data-reduced format on OpenVMS Alpha Version 7.3–1 and shows the approximate sizes of the libraries in both data-reduced and expanded format.

Table 4–1 Reduced and Expanded Library Sizes

Library Name	Reduced Size (as shipped)	Expanded Size	Description
[SYSHLP] directory; Help library files (.HLB)

ACLEDT.HLB	70	102	Access Control List Editor help
BKM$HELP.HLB	156	248	Backup Manager help
DBG$HELP.HLB	1234	2133	OpenVMS Debugger help
DBG$UIHELP.HLB	269	438	OpenVMS Debugger help
EDTHELP.HLB	154	229	EDT Editor help
EVE$HELP.HLB	676	1197	EVE Editor help
EVE$KEYHELP.HLB	99	145	EVE Keypad help
EXCHNGHLP.HLB	83	118	Exchange Utility help
HELPLIB.HLB	9179	16662	DCL help
LANCP$HELP.HLB	119	174	LAN Control Program help
LATCP$HELP.HLB	157	243	LAT Control Program help
MAILHELP.HLB	211	316	Mail Utility help
NCPHELP.HLB	261	412	Network Control Program help
SDA.HLB	308	457	System Dump Analyzer help
SHWCLHELP.HLB	103	151	Show Cluster utility help
SYSGEN.HLB	337	526	System Generation utility help
SYSMANHELP.HLB	492	786	System Management utility help
TPUHELP.HLB	575	1036	Text Processing Utility help
UAFHELP.HLB	241	377	Authorize Utility help

[SYSLIB] directory; Macro library files (.MLB)

LANIDEF.MLB	181	241	LAN internal driver macros
LIB.MLB	2715	4679	Operating system macros
STARLET.MLB	2335	3467	Operating system macros

[SYSLIB] directory; Object library files (.OLB)

STARLET.OLB	27461	44256	System object library and run-time library
VAXCRTL.OLB	1163	1557	Compaq C RTL routine name entry points; VAX G_floating double-precision, floating-point entry points
VAXCRTLD.OLB	1587	2542	Limited support of VAX D_floating double-precision, floating-point entry points
VAXCRTLDX.OLB	1506	2391	VAX D_floating support; support for /L_DOUBLE_SIZE=128 compiler qualifier
VAXCRTLT.OLB	1434	2234	IEEE T_floating double-precision, floating-point entry points
VAXCRTLTX.OLB	1449	2244	IEEE T_floating support; support for /L_DOUBLE_SIZE=128 compiler qualifier
VAXCRTLX.OLB	1285	1811	G_floating support; support for /L_DOUBLE_SIZE=128 compiler qualifier
VMS$VOLATILE_ PRIVATE_INTERFACES.OLB	445	635	OpenVMS bugcheck processing codes

[SYSLIB] directory; Text library files (.TLB)

ERFLIB.TLB	64	85	ANALYZE/ERROR device descriptions
LIB_ADA_SUBSET.TLB	1839	3385	Ada programmers toolkit of operating system definitions
NTA.TLB	34	42	Files to build against NTA facility
STARLET_RECENT_ ADA_SUBSET.TLB	1100	1942	Ada programmers toolkit of operating system definitions
STARLETSD.TLB	3940	7208	STARLET definitions used during layered product installations
SYS$LIB_C.TLB	9442	20214	Header files for C language; derived from LIB
SYS$STARLET_C.TLB	5864	12752	Public header files for Compaq C

TOTALS:

78568

137435

$Q:\adept8\entities\note.eps$ Note

File sizes are subject to change. For the most accurate information, run the Library Decompression utility (LIBDECOMP.COM) on your own system and review the output from the list function.

To expand all the libraries, you would need approximately 60,000 free disk blocks. However, you can choose to expand only selected libraries. For complete details about expanding and reducing system library files and using LIBDECOMP.COM, refer to the OpenVMS System Manager’s Manual.

4.10 Adding and Removing Operating System Files

If you decide after the installation to change which OpenVMS Alpha operating system files you want installed on your system, you can use the menu system contained on the OpenVMS Alpha operating system CD–ROM to add or remove files.

$Q:\adept8\entities\note.eps$ Note

You can obtain information about individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($).

To add or remove operating system files:

1. Mount and boot the OpenVMS Alpha operating system CD–ROM.

2. Choose option 1 from the menu.

3. Choose the PRESERVE option.

4. Enter the name of the device that contains the system disk and answer the questions.

5. After you answer the question “Do you want detailed descriptions?,” information regarding reconfiguring or reinstalling is displayed. Read the instructions, then choose the desired entry from the menu of options.

The following is a sample display:

    Please choose one of the following:

        1)  Upgrade, install or reconfigure OpenVMS Alpha Version 7.3-1
        2)  Display products and patches that this procedure can install
        3)  Install or upgrade layered products and patches
        4)  Show installed products
        5)  Reconfigure installed products
        6)  Remove installed products
        7)  Execute DCL commands and procedures
        8)  Shut down this system

Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1
    ***********************************************************

.
.
.

Do you want to INITIALIZE or to PRESERVE? [PRESERVE] 

.
.
.
    Version 7.3-1 of the OpenVMS operating system is already installed
    on the target disk.  You may choose one of the following actions:

    o Reconfigure the OpenVMS platform.

      This action will allow you to change your selections of which
      of the windowing and network products you included with your
      OpenVMS operating system installation.

    o Reconfigure the OpenVMS operating system.

      This action will allow you to change your choices about which
      options you included for the OpenVMS operating system.

    o Reinstall the OpenVMS operating system.

      This action will cause ALL operating system  files to be replaced.
      You can also change your choices about which options you included
      for the OpenVMS operating system.

      Reinstall will take longer than Reconfigure.  Reinstall may be
      appropriate if you suspect that files in the operating system,
      or in the windowing and network products have become corrupted.

    If you want to reinstall any of the windowing and network products,
    choose "Install or upgrade layered products and patches" (option 3)
    from the main menu.

    If you want to change your choices about which options you included
    for any of the windowing and network products, choose "Reconfigure
    installed products" (option 5) from the main menu.

    Please choose one of the following:

        1)  Reconfigure the OpenVMS platform.
        2)  Reconfigure the OpenVMS operating system.
        3)  Reinstall the OpenVMS operating system.
        4)  Return to the Main Menu (abort the upgrade/installation).


Enter choice or ? for help: (1/2/3/4/?) 2
The following product has been selected:
    DEC AXPVMS VMS V7.3-1              Operating System


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.

DEC AXPVMS VMS V7.3-1: OpenVMS Operating System

    COPYRIGHT (c) 12-MAY-2002 -- All rights reserved
   
    Compaq Information Technologies Group, L.P.  

Do you want the defaults for all options? [YES]

Answer No to this question, and select the options you want as described in Section 3.5.2. A list of components is provided in Section 3.5.3. After you respond to the prompts, the display continues and the installation procedure completes as described in Section 3.5.4. The following is a continuation of the sample display:

    Do you want to review the options? [NO] 
 
Execution phase starting ...
The following product will be reconfigured:
    DEC AXPVMS VMS V7.3-1
Portion done: 0%...10%...20%...30%...40%...50%...60%...80%...90%...100%
The following product has been reconfigured:
    DEC AXPVMS VMS V7.3-1
.
.
.

For detailed instructions on how to remove the OpenVMS Alpha operating system from your disk, see Appendix E.

4.11 Preparing to Use OpenVMS Management Station

If you installed the OpenVMS Management Station software on your system (either by accepting all default values or by selecting the component manually during the installation procedure), you must perform several tasks on your OpenVMS Alpha system and your PC before you can use OpenVMS Management Station. These tasks include the following:

• Editing system files

• Starting OpenVMS Management Station on other nodes

• Verifying that you have the proper memory, disk space, media, and the required software to install and run OpenVMS Management Station on your PC

• Installing the client software on your PC

• Defining DECnet nodes

For complete information about preparing your OpenVMS system and your PC to run the OpenVMS Management Station server and client software, see Appendix D.

$Q:\adept8\entities\note.eps$ Note

After you complete the tasks described in Appendix D, you can then remove those files from your system to save disk space. Do not use the DELETE command to remove the files. Instead, reconfigure the OpenVMS Alpha operating system as described in Section 4.10.

4.12 Installing Layered Products

You can use the menu system included on the operating system CD–ROM to install certain layered products with the POLYCENTER Software Installation utility. If you did not install those layered products previously during the installation procedure, you can do so using the following procedure. To install layered products that require VMSINSTAL, see Section 4.12.1.

$Q:\adept8\entities\note.eps$ Note

To use this procedure, the target system must have the exact same version of the OpenVMS Alpha operating system as the CD–ROM. If you need to install layered products on a target system that has a different version of the operating system, use the alternate procedure described in the next section.

1. Shut down the system (described in Appendix A ).

2. Boot the operating system CD–ROM (locally or from the InfoServer).

3. Choose option 2 from the menu to view which layered products can be installed using the POLYCENTER Software Installation utility.

4. Choose option 3 from the menu to install the layered products.

5. Shut down the system by selecting option 8 from the menu.

6. Boot from the system disk.

If the layered product that you want to install is not listed in the display, see the documentation you received with that layered product for installation information.

For additional information about installing layered products, see the OpenVMS System Manager’s Manual.

Be sure you back up the system disk after you install all your layered products.

4.12.1 Alternate Procedure

Following is another method for installing layered products from the OpenVMS Alpha operating system CD–ROM:

1. From your running OpenVMS system (the target system disk), mount the OpenVMS Alpha operating system CD–ROM.

2. Locate the directories and files containing the available layered products by entering the following command (where, in the example, DKA400: is the device name of the CD–ROM):

$ DIRECTORY /NOHEAD/NOTRAIL DKA400:[*.KIT]

You can use the PRODUCT FIND command to locate kits that are installed using the POLYCENTER Software Installation utility. For example:

$ PRODUCT FIND * /SOURCE=DKA400:[*.KIT]

3. To install layered products that require VMSINSTAL (indicated in the directories by save-set file names with file types of .A, .B, and so on), enter the @SYS$UPDATE:VMSINSTAL command and then specify the CD–ROM device and directory. For example:

$ @SYS$UPDATE:VMSINSTAL
* Where will the distribution volumes be mounted: DKB400:[UCX032.KIT]

4. To install layered products that require the POLYCENTER Software Installation utility (indicated in the directories by file names with file types of .PCSI or .PCSI$DESCRIPTION), use the PRODUCT INSTALL command to specify the CD–ROM device name and directory. Following is an example of the PRODUCT INSTALL command:

$ PRODUCT INSTALL POSIX /SOURCE=DKB400:[POSIX020.KIT]

4.13 Installing OpenVMS Debugger Clients on a PC

OpenVMS Debugger includes a client/server interface. The debug server runs on OpenVMS; debug clients run on OpenVMS and on Microsoft Windows 95 and Windows NT. There is no special installation procedure for the components that run on OpenVMS. This section describes the procedure for installing the debug client on a PC.

The following table shows which client kit to use for each PC configuration:

CPU	Operating System	Client Kit
Alpha	Windows NT	40COMAXP.EXE
Intel	Windows NT	40COMUPD.EXE
Alpha	Windows NT	DEBUGALPHA011.EXE
Intel	Windows 95, 98, Me, NT, 2000, XP	DEBUGX86011.EXE

These client kits are self-extracting .EXE files. To make these clients available to PC users, copy these files from the distribution media to a suitable PATHWORKS or Advanced Server for OpenVMS share, FTP server, or other device available to the PC. (Refer to the Guide to OpenVMS Alpha Version 7.3–1 CD–ROMs for the directory where these kits ship on the media.)

Once the appropriate executable file has been transferred to the PC, the user can run the file to install the debug client on the PC. The InstallShield installation procedure guides the user through the installation.

By default, the debug client is installed in the \Programs\OpenVMS Debugger directory. Click Browse to select an alternate directory.

Choose one of the following options:

Install Option	Details
Typical	Debug client and OpenVMS Debugger Manual in HTML format
Compact	Debug client only
Custom	Choice of Debug Client and/or OpenVMS Debugger Manual in HTML format

The installation procedure creates an OpenVMS Debugger program folder that contains the following items:

• Debug client

• Debug client help file

• OpenVMS Debugger Manual in HTML format

• Readme file

• Uninstall procedure

4.14 Backing Up the Customized System Disk

After you have customized the OpenVMS Alpha operating system to your satisfaction and installed your layered products, protect your work by making a standalone backup copy of the system disk.

For complete information about backup operations, including a description of an alternate method that does not require booting from the operating system CD–ROM, see Appendix B.

To back up the system disk:

1. Shut down the system (described in Appendix A ).

2. Boot the operating system CD–ROM (locally or from the InfoServer).

3. Use the menu system to enter the DCL environment (option 7).

4. Mount the system disk and the target device on which you will make the backup copy.

5. Enter backup commands to back up the system disk to the target device.

6. Log out from the DCL environment.

7. Shut down the system by selecting option 8 from the menu.

8. Boot from the system disk.

4.15 Configuring a Multihead System

A multihead configuration consists of a single system (such as a Compaq AlphaServer ES40) that supports multiple graphics options. A graphics option consists of a graphics controller and a graphics display interface (monitor).

Your system can be automatically configured for multihead use if you rename the private server setup file from a template file type to a command procedure file type. The DECwindows Motif server loads this command procedure on startup or restart.

To set up your system for multihead support:

1. After installing the DECwindows Motif software on your system, log in to your system.

2. Copy the private server setup template file to a new .COM file by entering the following command:

$ COPY SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE
_To: SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM

3. Restart the DECwindows server by entering the following command:

$ @SYS$STARTUP:DECW$STARTUP RESTART

See the most recent version of the DECwindows Motif for OpenVMS Installation Guide and Managing DECwindows Motif for OpenVMS Systems for more information about customizing your DECwindows environment using the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file.

4.16 Running AUTOGEN

When you installed the OpenVMS Alpha operating system, the system executed the AUTOGEN.COM procedure to set the values of system parameters and the sizes of the page, swap, and dump files according to the system configuration. As a postinstallation procedure, you should run the AUTOGEN.COM procedure again to properly tune the system.

Run AUTOGEN as follows:

1. After 24 hours of operation, run AUTOGEN in feedback mode and reboot the system.

2. Run AUTOGEN again in feedback mode two workdays later, and then reboot the system. (For information about the importance of having a current AGEN$FEEDBACK.DAT file, see Section 5.5.)

3. Compaq recommends that you run AUTOGEN from SAVPARAMS through TESTFILES on a weekly basis thereafter, and examine AGEN$PARAMS.REPORT to determine the need for additional changes.

4.17 Modifying Parameters

Based on your examination of AGEN$PARAMS.REPORT, you might need to modify parameter values in MODPARAMS.DAT. If so, note the following:

• Hardcoded values in MODPARAMS.DAT should not hinder AUTOGEN’s ability to calculate feedback parameters. AUTOGEN generally does not reduce the value of parameters that allocate resources; it considers current parameter values to be minimum values, which means that you do not have to add MIN_* symbols to MODPARAMS.DAT.

• AUTOGEN does increase parameter values according to its calculations unless you have specified explicit or maximum values (by adding MAX_* symbols) in MODPARAMS.DAT.

For more information about the MODPARAMS.DAT file and about using AUTOGEN in general, see the OpenVMS System Manager’s Manual.

4.18 Tuning BAP System Parameters

OpenVMS Alpha Version 7.1 and later contains system parameters that control the operation of bus-addressable pool (BAP).

The CIPCA, CIXCD, KFMSB, and Qlogic 1020ISP adapters are some of the adapters that use bus-addressable pool to improve performance. BAP is a non-paged dynamic, physical-address-filtered memory pool used to overcome I/O bus and 32-bit adapter physical addressing limits.

The following table lists the system parameters that control BAP operation along with their default values:

System Parameter	Default Value
NPAG_BAP_MIN	0
NPAG_BAP_MAX	0
NPAG_BAP_MIN_PA	0
NPAG_BAP_MAX_PA	-1

The default values of these parameters allow the system to boot with any configuration. When AUTOGEN is run on a configured system, it resets these parameters to values that should enhance performance for the current system configuration.

If the system fails to boot after an installation, upgrade, or configuration change, and displays a message that refers to incorrect BAP parameters, Compaq recommends that you perform the following steps:

1. Reset the BAP parameters to the default values.

2. Reboot the system.

3. Allow the installation procedure to run AUTOGEN, or manually run AUTOGEN yourself.

A typical AUTOGEN with FEEDBACK command to set these parameters follows:

$ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK

$Q:\adept8\entities\note.eps$ Note

These parameters are critical. Compaq recommends that you run AUTOGEN as described to ensure that they are set correctly.

If you prefer not to use this command because you want to adjust only the BAP parameters settings, use the following procedure:

1. Boot the system using the default BAP parameter values.

2. Manually run SYS$SYSTEM:AGEN$FEEDBACK.EXE:

$ @SYS$SYSTEM:AGEN$FEEDBACK.EXE

3. Search SYS$SYSTEM:AGEN$FEEDBACK.DAT for the BAP_* system parameter values:

$ SEARCH SYS$SYSTEM:AGEN$FEEDBACK.DAT "BAP_"

4. Run SYSGEN to set the following system parameters with the BAP values you obtained in Step 3:

AGEN$FEEDBACK Data	System Parameter	Units
BAP_MIN	NPAG_BAP_MIN	bytes
BAP_MAX	NPAG_BAP_MAX	bytes
BAP_MIN_PA	NPAG_BAP_MIN_PA	Mbytes^{1 (SEE NOTE)}
BAP_MAX_PA	NPAG_BAP_MAX_PA	Mbytes¹

The BAP allocation amount (specified by BAP_MIN and BAP_MAX) depends on the adapter type, the number of adapters, and the version of the operating system. The physical address range (specified by BAP_MIN_PA and BAP_MAX_PA) depends on the adapter type and the way the Galaxy logical partitions, if any, are defined.

$Q:\adept8\entities\note.eps$ Note

If you manually set parameters NPAG_BAP_MIN_PA and NPAG_BAP_MAX_PA, be sure to specify the value for each parameter in the correct units (bytes or megabytes) for your operating system version.

4.19 Postinstallation Checklist

Use the following checklist to make sure you perform all the necessary postinstallation tasks:

[ ] Register your licenses if you did not do so during the installation procedure.

[ ] Create accounts.

[ ] Back up the system disk as a safeguard before customizing the system.

[ ] Customize the system.

[ ] Initialize CDSA.

[ ] Configure and start the DECnet Phase IV for OpenVMS software.

[ ] Run the User Environment Test Package (UETP) to test the system.

[ ] Expand the system libraries using LIBDECOMP.COM.

[ ] Add and remove files.

[ ] Prepare your OpenVMS Alpha system and your PC to run OpenVMS Management Station by following the procedures described in Appendix D.

[ ] Install layered products.

[ ] Back up the system disk after you have customized it and installed layered products.

[ ] Configure your multihead system (if applicable).

[ ] After the system has been running for at least 24 hours, run AUTOGEN to collect feedback information and modify the MODPARAMS.DAT file (if necessary).

5 Before Upgrading the OpenVMS Alpha Operating System

This chapter describes which tasks you should perform prior to beginning an upgrade. Tasks described in this chapter include:

• Reviewing notes, cautions, and restrictions

• Preparing to upgrade in a volume shadowing environment

• Backing up the current system disk

• Preparing the system disk for the upgrade

• Shutting down the system

• Using the preupgrade checklist

In addition to reviewing the information in this chapter, you might need to refer to the following sources of information as well:

• OpenVMS Alpha Version 7.3–1 Release Notes

• OpenVMS System Manager’s Manual, for information about using AUTOGEN, modifying the system parameters file (MODPARAMS.DAT), and related operations

• OpenVMS System Management Utilities Reference Manual, for information about using system management utilities such as SYSMAN and ANALYZE/DISK_STRUCTURE

• OpenVMS Guide to System Security, for information about reestablishing your security environment after the upgrade

5.1 Notes, Cautions, and Restrictions

This section provides important information that can affect the success of your upgrade. Review the cautions, restrictions, and notes carefully before you begin the upgrade.

5.1.1 Spiralog File System Not Supported

The Spiralog file system will not work with OpenVMS Alpha Version 7.3–1. If Spiralog is installed on your system, you must uninstall it before upgrading to OpenVMS Alpha Version 7.3–1.

5.1.2 Upgrade Paths

The following sections describe the various types of upgrades to Version 7.3–1.

5.1.2.1 Direct Upgrade Paths

You can upgrade directly to OpenVMS Alpha Version 7.3–1 from only the following versions of OpenVMS Alpha:

Version 7.3

Version 7.2-2

Version 7.2-1

Version 7.2-1H1

Version 7.1-2

If you are currently running OpenVMS Alpha Version 6.2x, you can do a two-step upgrade: first to Version 7.2-2 or 7.3, and then to Version 7.3–1.

5.1.2.2 Cluster Concurrent Upgrades

During a concurrent upgrade, you must shut down the entire cluster and upgrade each system disk. No one can use the cluster until you upgrade and reboot every computer. Once you reboot, each computer will be running the upgraded version of the operating system.

5.1.2.3 Cluster Rolling Upgrades

During a cluster rolling upgrade, you upgrade each system disk individually, allowing old and new versions of the operating system to run together in the same cluster. There must be more than one system disk. The systems that are not being upgraded remain available.

Only the following OpenVMS Alpha and OpenVMS VAX versions are supported in mixed-version clusters that include OpenVMS Alpha Version 7.3–1:

Version 7.3–1 (Alpha)

Version 7.3 (Alpha and VAX)

Version 7.2–2 (Alpha)

Version 7.2–1 (Alpha)

Version 7.2–1H1 (Alpha)

Version 7.2 (VAX)

If you are upgrading in a cluster environment, rolling upgrades are supported from Version 7.2-x and 7.3 of the OpenVMS Alpha operating system. If you have other versions in a cluster, you cannot do a rolling upgrade until those versions are upgraded to a supported version. See Chapter 6, Preparing to Upgrade in an OpenVMS Cluster Environment for more information about upgrading clusters.

5.1.3 Update License

To upgrade to OpenVMS Alpha Version 7.3–1, you must have an appropriate license. Compaq’s software licenses grant the right to use the current version of a product or any previous version of the product at the time of purchase. If you have an OpenVMS Alpha license prior to Version 7.3–1 and are not covered by a Software Product Services agreement, which includes the right to use new versions (RTNV), you must purchase an Update License before upgrading to OpenVMS Alpha Version 7.3–1.

If you do not have an Update License, please contact your Compaq support representative who will assist you in obtaining the correct Product Authorization Key (PAK) needed to access the OpenVMS operating system.

5.1.4 Files and Directories

If you choose not to install optional OpenVMS Alpha software during the upgrade, the upgrade procedure removes existing files for those components from the system disk.

If you have changed directory structure on your system disk, the upgrade procedure will not work correctly. Restore your system disk to a standard directory structure before you attempt an upgrade.

The OpenVMS Alpha Version 7.3–1 upgrade procedure provides new files and directories in the directory [VMS$COMMON...]. If you had any special protections and access control lists (ACLs) before the upgrade, you need to reapply them to reestablish the security environment you had previously set up. For more information about creating and maintaining a secure environment, see the OpenVMS Guide to System Security.

5.1.5 Licenses and Layered Products

The upgrade procedure is designed so that you should not have to reinstall most layered products after the upgrade. However, you might need to reinstall certain layered products because of product-specific installation procedures.

The upgrade procedure leaves your OpenVMS Alpha license and layered product licenses intact. You do not need to reinstall these licenses after you upgrade.

5.2 Preparing to Upgrade in a Volume Shadowing Environment

Because you cannot upgrade the operating system on a shadowed system disk (the upgrade will fail), you need to disable shadowing on that disk and perform other operations before you can upgrade the operating system.

There are several methods for creating a nonshadowed target disk. This chapter describes how to change one of your existing shadowed system disks in a multimember shadow set to a nonshadowed disk that you can use as your target disk for the upgrade.

If you have a larger configuration with disks that you can physically access, you may want to use a copy of the system disk as your target disk. Volume Shadowing for OpenVMS describes two methods you can use to create this copy (using volume shadowing commands or BACKUP commands) and how to disable volume shadowing.

5.2.1 Creating a Nonshadowed Target Disk

Follow the procedure described in this section to change one of your existing shadowed system disks to a nonshadowed disk.

$Q:\adept8\entities\note.eps$ Caution

If you simply use a MOUNT/OVERRIDE=SHADOW_MEMBERSHIP command to mount the volume to be upgraded, volume shadowing can overwrite the newly upgraded disk with information from a prior volume that has not been upgraded.

1. Shut down all systems booted from the shadowed system disk.

2. Perform a conversational boot (see Appendix A if necessary) on the system disk you have chosen for your target disk. For example:

>>> BOOT -FLAGS 0,1 DKA100

3. At the SYSBOOT>prompt, enter the following command to disable volume shadowing on the disk:

SYSBOOT> SET SHADOW_SYS_DISK 0

4. Enter the CONTINUE command to resume the boot procedure. For example:

SYSBOOT> CONTINUE

5. After the boot completes, log in to the system.

After you have created a nonshadowed system disk that you can use for the upgrade, perform the additional preupgrade procedures described in the balance of this chapter.

5.2.2 Changing the Label

If you want to change the label on the upgrade disk, use the DCL command SET VOLUME/LABEL=volume-label device-spec[:] to perform this optional task. (The SET VOLUME/LABEL command requires write access [W] to the index file on the volume. If you are not the volume owner, you must have either a system UIC or the SYSPRV privilege.)

For OpenVMS Cluster systems, be sure that the volume label is a unique name across the cluster. Compaq strongly recommends that a volume label contain only alphanumeric characters and the dollar sign ($), underscore (_), and hyphen (-) characters. You can include other characters in a volume label, but doing so on a system disk can cause the upgrade procedure to fail.

$Q:\adept8\entities\note.eps$ Note

If you need to change the volume label of a disk that is mounted across the cluster, be sure you change the label on all nodes in the OpenVMS Cluster system. The following example shows how to use the SYSMAN utility to define the environment as a cluster and propagate the volume label change to all nodes in that cluster:

SYSMAN> SET ENVIRONMENT/CLUSTER
SYSMAN> DO SET VOLUME/LABEL=new-label disk-device-name:

5.2.3 Setting the Boot Device

Be sure your system is set to boot from the upgrade disk by default. Use the SHOW BOOTDEF_DEV and SET BOOTDEF_DEV console commands to accomplish this task. (See Appendix A for more information.)

5.3 Backing Up the System Disk

Compaq strongly recommends that you make a backup copy of the system disk and, if your configuration allows it, upgrade the backup copy. Then, if there are problems, you will still have a working system disk.

$Q:\adept8\entities\note.eps$ Note

OpenVMS Engineering has encountered cases where recovery from a failed upgrade has been difficult, expensive, or impossible because no backup of the preupgrade system disk was available. Various hardware or software failures or a power failure can make a partially upgraded system disk unusable. A backup copy may be the only route to recovery. The minimal time required to make a backup is a very wise investment!

To back up the system disk, do the following:

1. Shut down the system (described in Appendix A ).

2. Boot the operating system CD–ROM (locally or from the InfoServer).

3. Use the menu system to enter the DCL environment (option 7 ).

4. Mount the system disk and the target device on which you will make the backup copy.

5. Enter backup commands to back up the system disk to the target device.

6. Log out from the DCL environment.

7. Shut down the system by selecting option 8 from the menu.

8. Boot from the system disk.

For complete information about backup operations, including a description of an alternate method that does not require booting from the operating system CD–ROM, see Appendix B.

5.4 Preparing the System Disk

The following sections describe how to prepare the system disk for the upgrade. The operations include the following:

• Examining the system disk

• Checking the size of the system disk

• Verifying system parameters

5.4.1 Examining the System Disk

Examine and repair (if necessary) the system disk using the ANALYZE/DISK_STRUCTURE command. (See the OpenVMS System Management Utilities Reference Manual for more information about this command.) Use the following procedure:

1. Analyze the system disk for inconsistencies and errors in the file structure by entering the following command:

$ ANALYZE/DISK_STRUCTURE SYS$SYSDEVICE

Ignore the following message:

%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS

2. If you find any other errors on the system disk, repair the errors by entering the following command:

$ ANALYZE/DISK_STRUCTURE/REPAIR SYS$SYSDEVICE

5.4.2 Checking the SYSCOMMON Directories

For the upgrade to be successful, the SYSCOMMON directories in all system roots must be aliases (or hard links) for the VMS$COMMON directory. To check whether this is the case, execute the following DIRECTORY/FILE_ID commands and compare the displayed file identifiers to ensure that they are all the same.

$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING device:[000000]VMS$COMMON.DIR
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING device:[SYS*]SYSCOMMON.DIR

If you are booted from the system disk that you will be upgrading, you can use SYS$SYSDEVICE as the device name in these commands, as follows:

$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[000000]VMS$COMMON.DIR
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[SYS*]SYSCOMMON.DIR

If you did not boot from the system disk that you will be upgrading, mount the disk to be upgraded and specify the actual device name in the command. For example, if the system disk to be upgraded is mounted on DKA100, you would use commands similar to the following:

$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING DKA100:[000000]VMS$COMMON.DIR
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING DKA100:[SYS*]SYSCOMMON.DIR

Output from the first command should list a single file. Output from the second command should list one file for each system root on the disk. Check whether the file ID is the same for all of the listed files and take action as follows:

• If all the file IDs are the same, continue with the procedure described in the next section.

• If all the file IDs are not the same, this system disk does not have the directory structure that OpenVMS requires, and the upgrade will not succeed.

Correcting this problem requires detailed knowledge about how the problem was created. There is no general solution. Because it can be difficult to correct this problem, it is often easier to reinstall OpenVMS (and any layered products) on a new system disk.

5.4.3 Checking the Size of the System Disk

It is difficult to determine in advance how many blocks of disk space you will need for the upgrade. It depends on how many files you have on the target disk already and on how many components you select during the upgrade procedure. However, the following information will help:

• The maximum amount of disk space you will need is approximately 360,000 blocks, but your system might use substantially less.

• After you select the components you want installed on the system for the upgrade, the upgrade procedure calculates whether you have enough disk space, displaying the number of available blocks and the number required for the upgrade. If the procedure determines that your disk does not have enough space to perform the upgrade, it displays a message to alert you and allows you to terminate the upgrade so you can create more disk space and try the upgrade again.

To see how much space you have on the system disk, enter the following command:

$ SHOW DEVICE SYS$SYSDEVICE

5.4.4 Verifying System Parameters

Verify (and modify if necessary) system parameters, described as follows. (If necessary, see the OpenVMS System Manager’s Manual for more information about modifying system parameters.) Any system parameters that you modified and did not enter in SYS$SYSTEM:MODPARAMS.DAT are lost during the upgrade. To retain these parameters, enter their names in SYS$SYSTEM:MODPARAMS.DAT and the value that AUTOGEN needs to add to the default minimum value. (When AUTOGEN runs after the upgrade, it uses the values in SYS$SYSTEM:MODPARAMS.DAT.)

For example, if you modified GBLPAGES by 128 pages above the default, add the following line to SYS$SYSTEM:MODPARAMS.DAT:

ADD_GBLPAGES=128

If your system was upgraded previously, a new SYS$SYSTEM:MODPARAMS.DAT file was created then. This file has comments and possibly duplicated entries that were created during that upgrade. If you upgrade again, SYS$SYSTEM:MODPARAMS.DAT can become unnecessarily large and potentially confusing. Compaq recommends that you edit and reorganize SYS$SYSTEM:MODPARAMS.DAT before you upgrade again.

$Q:\adept8\entities\note.eps$ Note

On a cluster system disk, MODPARAMS.DAT should exist in SYS$SYSROOT:[SYSEXE] for each root. You must edit MODPARAMS.DAT as necessary for each root.

5.5 FEEDBACK.DAT File

Compaq recommends that, before upgrading your system, you have a recent SYS$SYSTEM:AGEN$FEEDBACK.DAT file. In OpenVMS Cluster systems, there should be a copy of this file on each node. When the system (or each system in a cluster) is rebooted after the upgrade, AUTOGEN is run. If a recent AGEN$FEEDBACK.DAT file is available, it is used. The data in this file helps AUTOGEN set system parameters for your specific applications and workload.

$Q:\adept8\entities\note.eps$ Note

If you do not have a current AGEN$FEEDBACK.DAT file, AUTOGEN may calculate system parameters that do not reflect your system’s requirements. In that case, it can take multiple cycles of running AUTOGEN and rebooting before all layered products can be started. In some cases, successful startup can require additional entries in MODPARAMS.DAT. This should not be necessary when a current AGEN$FEEDBACK.DAT file is available.

You should create a current AGEN$FEEDBACK.DAT during a time when your system is running under a typical workload. When this condition exists, enter the following command:

$ SYS$UPDATE:AUTOGEN SAVPARAMS

This runs very quickly and should not affect the performance of your system while it executes. It is a good idea to run AUTOGEN in FEEDBACK mode on a weekly — or even daily — basis.

You can also specify the SAVE_FEEDBACK option when you execute SYS$SYSTEM:SHUTDOWN.COM. However, the data captured may not fully reflect the typical workload on your system.

5.6 Finish and Shutdown

Continue the preupgrade tasks as follows, depending on whether you are upgrading in a standalone or OpenVMS Cluster environment:

IF ...

THEN ...

you are upgrading a standalone system,

do the following:

1. Log in to the SYSTEM account.

2. Enter the following command and then press the Return key:

$ @SYS$SYSTEM:SHUTDOWN

3. When the procedure asks if an automatic system reboot should be performed, enter N (No) and press the Return key.

4. Go to the checklist at the end of this chapter to verify that you have performed the necessary tasks; then go to Chapter 7, Upgrading the OpenVMS Alpha Operating System to begin the upgrade procedure.

you are upgrading an OpenVMS Cluster system,

do the following:

1. Review the checklist at the end of this chapter.

2. Go to Chapter 6, Preparing to Upgrade in an OpenVMS Cluster Environment.

5.7 Preupgrade Checklist

Use the following checklist to make sure you have performed all the tasks before beginning the upgrade:

[ ] Review all cover letters and the release notes.

[ ] Review all cautions and notes.

[ ] If your system disk is part of a shadow set, create a nonshadowed system disk to upgrade.

[ ] Set up your system to record the upgrade procedure on either a hardcopy terminal or a printer attached to the console terminal. If you do not do this, the screen messages will be lost. You will need a transcript in case there is a problem during the upgrade. For information on how to record the procedure, see the hardware manuals that came with your Alpha computer.

[ ] Make a backup copy of the system disk.

[ ] Examine and repair (if necessary) the system disk using the ANALYZE/DISK_STRUCTURE command.

[ ] Check the size of the system disk.

[ ] Verify system parameters.

[ ] Shut down the system (if you are upgrading in a standalone environment).

[ ] If you are upgrading an OpenVMS Cluster system, go to Chapter 6, Preparing to Upgrade in an OpenVMS Cluster Environment. If you are not upgrading an OpenVMS Cluster system, go to Chapter 7, Upgrading the OpenVMS Alpha Operating System to begin the upgrade procedure.

6 Preparing to Upgrade in an OpenVMS Cluster Environment

This chapter describes how to prepare to upgrade in an OpenVMS Cluster environment, depending on the type of upgrade you perform and whether you need to add any new computers to the cluster.

$Q:\adept8\entities\note.eps$ Note

Be sure you have performed the preupgrade tasks described in Chapter 5, Before Upgrading the OpenVMS Alpha Operating System before you upgrade your OpenVMS Cluster system.

When you upgrade the operating system in an OpenVMS Cluster environment, be sure the following information is available to review:

• The cover letters and the software product descriptions included with your distribution kit

• OpenVMS Alpha Version 7.3–1 Release Notes

• OpenVMS Cluster Systems

• Guidelines for OpenVMS Cluster Configurations

• OpenVMS Alpha Version 7.3–1 New Features and Documentation Overview

6.1 Mixed-Version Support

Warranted support means that Compaq has fully qualified the two versions coexisting in an OpenVMS Cluster and will answer all problems identified by customers using these configurations.

Migration support is a superset of the Rolling Upgrade support provided in earlier releases of OpenVMS and is available for mixes that are not warranted. Migration support means that Compaq has qualified the versions for use together in configurations that are migrating in a staged fashion to a newer version of OpenVMS VAX or OpenVMS Alpha. Problem reports submitted against these configurations will be answered by Compaq. However, in exceptional cases, Compaq may request that you move to a warranted configuration as part of the solution.

Compaq supports only two versions of OpenVMS running in a cluster at the same time, regardless of architecture. Migration support helps customers move to warranted OpenVMS Cluster pairs. Table 6 –1 shows the level of support provided for all possible version pairings.

Table 6–1 OpenVMS Cluster Warranted and Migration Support

	Alpha V7.3x and VAX V7.3	Alpha V7.2-x^{1 (SEE NOTE)} and VAX V7.2
Alpha V7.3x and VAX V7.3	WARRANTED	Migration
Alpha V7.2-x¹ and VAX V7.2	Migration	WARRANTED

In a mixed-version cluster, you might need to install remedial kits on earlier versions of OpenVMS. For a complete list of required remedial kits, see the OpenVMS Alpha Version 7.3–1 Release Notes.

6.2 Adding a New System to the Cluster

If you need to add a new computer supported by OpenVMS Alpha Version 7.3–1 to an existing OpenVMS Cluster configuration, Compaq supports two options, listed in the following preferred order:

1. Upgrade the entire cluster to OpenVMS Alpha Version 7.3–1 and add the new computer as a member.

2. If you need to keep some systems in the cluster running an older version of OpenVMS Alpha, you must upgrade a system disk in the cluster to OpenVMS Alpha Version 7.3–1 using the rolling upgrade procedure. Then boot the new computer into the cluster using that upgraded system disk.

6.3 Types of Upgrades

There are two types of cluster upgrades: concurrent and rolling. The type of upgrade you use depends on whether you want to maintain the availability of the cluster during the upgrade and whether you have more than one system disk. Review this chapter and then perform the preliminary tasks for the upgrade procedure (concurrent or rolling) that best suits your configuration.

6.4 Concurrent Upgrade

This section describes the following:

• How a concurrent upgrade works

• Preparing your system for a concurrent upgrade

6.4.1 How a Concurrent Upgrade Works

During a concurrent upgrade, you must shut down the entire cluster and upgrade each system disk. No one can use the cluster until you upgrade each system disk and reboot each Alpha computer. When the cluster reboots, each Alpha computer will be running the upgraded version of the OpenVMS Alpha operating system.

If all Alpha systems in the OpenVMS Cluster environment are booted from one system disk, you must perform a concurrent upgrade.

6.4.2 Preparing Your System for a Concurrent Upgrade

To prepare for a concurrent upgrade:

1. Log in locally to the SYSTEM account.

2. Shut down all systems by entering the following command on each system (satellites first, then the boot nodes):

$ @SYS$SYSTEM:SHUTDOWN

3. When the procedure asks if an automatic system reboot should be performed, enter N (No) and press the Return key.

4. Choose the CLUSTER_SHUTDOWN option.

5. When the shutdown procedure is finished on all nodes, halt each system by entering Ctrl/P or by pressing the Halt button.^{2 (SEE NOTE)}

6. If you have only one system disk for your cluster, go to Chapter 7, Upgrading the OpenVMS Alpha Operating System to begin the upgrade procedure.

If you have more than one system disk, make sure that you have performed the preupgrade tasks on each system disk that you will be upgrading. Then go to Chapter 7, Upgrading the OpenVMS Alpha Operating System and perform an upgrade on each system disk. You do not have to reboot the operating system CD–ROM for each upgrade. You only need to choose option 1 from the menu for each upgrade.

After the upgrade is complete, you will be instructed to reboot each computer in the OpenVMS Cluster environment before beginning other postupgrade procedures.

6.5 Rolling Upgrade

This section describes the following:

• How a rolling upgrade works

• Notes and restrictions

• Preparing your system for a rolling upgrade

6.5.1 How a Rolling Upgrade Works

During a rolling upgrade, you upgrade each system disk individually, allowing old and new versions of the operating system to run together in the same cluster, creating a mixed-version cluster. Because rolling upgrades allow mixed-version clusters, the systems that you are not upgrading remain available. During a rolling upgrade, you keep some of the computers in the cluster running while you upgrade others (you must have more than one system disk).

6.5.2 Notes and Restrictions

The following restrictions apply to rolling upgrades. See the OpenVMS Alpha Version 7.3–1 Release Notes for additional compatibility issues and restrictions.

• Rolling upgrades are supported from Version 7.2-x and 7.3 of the OpenVMS Alpha operating system. Rolling upgrades in mixed-architecture OpenVMS Cluster environments are supported with VAX computers running Versions 7.2 or 7.3 of the OpenVMS VAX operating system (see Table 6 –1).

• The system being upgraded does not attempt to access any disk that is being accessed by one or more of the remaining OpenVMS Cluster systems.

• The remaining OpenVMS Cluster systems do not attempt to access the target disk of the system being upgraded.

If the target disk being upgraded is locally attached to the system performing the upgrade, then it is not accessible to the remaining OpenVMS Cluster systems. (The OpenVMS system booted from the operating system CD–ROM does not MSCP serve local disks.) Whenever possible, Compaq recommends that you perform the upgrade on a local disk or that you perform a concurrent upgrade.

During the upgrade, be sure that the target disk you select, as well as any disk you access from the DCL menu option, is either a local disk or one that is not being accessed by any of the remaining OpenVMS Cluster members.

$Q:\adept8\entities\note.eps$ Note

Any attempt to access the target disk from the remaining OpenVMS Cluster members will corrupt the target disk in most cases. Even if the target disk is only mounted by a remaining cluster member, and no file access is done, the target disk will probably be corrupted. If a disk is corrupted in this way, the only supported recovery is to restore the backup copy of the corrupted disk.

• Compaq recommends that all Alpha computers in a cluster run the same (and preferably the latest) version of the OpenVMS Alpha operating system.

• You cannot perform a rolling upgrade if all systems boot from a single system disk. Perform a concurrent upgrade instead.

• The upgrade procedure affects the queuing system as follows:

– The queuing system is not active on the system you are upgrading; do not attempt to execute a START/QUEUE/ MANAGER command.

– You cannot create a queue database on the operating system CD–ROM (because it is not writable).

– The queue manager process on other nodes in the cluster can continue to run during the upgrade if the queue database is not on the disk being upgraded.

6.5.3 Preparing Your System for a Rolling Upgrade

To prepare for a rolling upgrade:

1. Log in to any node where the target disk is mounted as a data disk, rather than as the system disk. (That disk must be the one on which you already performed the preupgrade tasks described in Chapter 5, Before Upgrading the OpenVMS Alpha Operating System.)

2. Check the votes and make adjustments to maintain the proper quorum so the cluster can continue to operate throughout the upgrade. (OpenVMS Cluster Systems describes this procedure in detail.)

3. Use the DCL command DISMOUNT/CLUSTER to dismount the data disk. (You can also perform this operation using the SYSMAN utility.)

Note that you can ignore messages from nodes where the specified data disk is being used as the system disk.

4. Verify that the data disk has been dismounted successfully by entering the following commands:

$ MCR SYSMAN
SYSMAN> SET ENVIRONMENT/CLUSTER
SYSMAN> DO SHOW DEVICE disk-name

Examine the display to be sure the disk is not mounted on any nodes as a data disk. Noting the value listed in the Trans Count field can help you make that determination: A value of less than 50 indicates that the disk is mounted as a data disk rather than as the system disk; a much larger value (for example, 300) indicates that the disk most likely is the system disk.

5. If the disk is still mounted on any nodes as a data disk, use the SYSMAN utility to dismount the disk; otherwise, exit from the SYSMAN utility.

6. Shut down all nodes that boot from the system disk you are upgrading, including the node from which you will perform the upgrade. Enter the following command on each node:

$ @SYS$SYSTEM:SHUTDOWN

7. When the procedure asks if an automatic system reboot should be performed, enter N (No) and press the Return key.

8. Choose the REMOVE_NODE option.

9. If proper quorum is not maintained at any time during the upgrade procedure, the shutdown procedure will hang the cluster. If the cluster hangs during a shutdown, enter the following commands on the system console of a system that is still a cluster member:

$ [Ctrl/P]
>>> D SIRR C
>>> C
IPC> Q
IPC> [Ctrl/Z]

10. After the shutdown procedure is finished on all nodes, go to Chapter 7, Upgrading the OpenVMS Alpha Operating System to begin the upgrade procedure.

$Q:\adept8\entities\note.eps$ Caution

During the upgrade it is very important that the system disk being upgraded is accessed only by the node on which the upgrade is being performed. If the disk can be accessed from other nodes in the cluster, for example, through an HSC or HSJ device, you must ensure that this does not happen. Even if the disk is only mounted and no file access is performed, the disk can still become corrupted.

Ensure that any users who might mount disks know that they must not access the system disk being upgraded. Also make sure that any procedures that might mount the disk do not run during the upgrade. If you have automatic procedures that periodically check and remount disks, it might be wise to disable them during the upgrade.

7 Upgrading the OpenVMS Alpha Operating System

This chapter describes the following tasks:

• Beginning the upgrade from the operating system CD–ROM

• Specifying the target disk

• Specifying the volume label

• Updating time zone information

• Choosing descriptive help text

• Completing the upgrade

• Performing postupgrade tasks (including booting the upgraded system)

• Installing layered products

7.1 Booting the Operating System CD–ROM

The OpenVMS Alpha Version 7.3–1 operating system includes procedures that allow you to easily upgrade the operating system using the POLYCENTER Software Installation utility. To get started, boot the OpenVMS Alpha operating system CD–ROM either from your local CD–ROM drive or from a CD–ROM drive connected to the InfoServer, as described in the following sections.

7.1.1 Booting from the Local Drive

To boot the operating system CD–ROM from the local drive, follow these steps:

1. Insert the operating system CD–ROM into the local CD–ROM drive.

2. At the console prompt (>>>), enter the SHOW DEVICE command so you can identify the name of the CD–ROM drive (for example, DKA400:)

3. Enter the boot command in the following format:

BOOT -FLAGS 0,0 source-drive

Substitute the device name of the CD–ROM drive (as listed in the SHOW DEVICE display) for source-drive.

For example, if the SHOW DEVICE display lists the device name of your CD–ROM drive as DKA400, enter the following command and press the Return key:

>>> BOOT -FLAGS 0,0 DKA400

7.1.2 Booting from the InfoServer

To boot the operating system CD–ROM using the InfoServer, follow these steps:

>>>SHOW DEVICE

dva0.0.0.1000.0    DVA0                     RX23
dka200.2.0.5.0     DKA200                   RZ28M  1004
dka300.3.0.5.0     DKA300                   RZ29B  0016
dka400.4.0.5.0     DKA400                   RZ26L  442E
ewa0.0.0.3.0       00-00-F8-1F-70-3D        Twisted-Pair

For additional information, refer to the Compaq OpenVMS Operating System for Alpha and VAX Software Product Description and the hardware manuals that you received with your Alpha computer.

2. At the console prompt, enter the following command:

>>> BOOT -FLAGS 0,0 -FILE APB_1073
lan-device-name

Note the following conventions:

• lan-device-name is the name of the local area network (LAN) device identified with your computer, as determined by using the SHOW DEVICE command in the previous step.

$Q:\adept8\entities\note.eps$ Note

If you are using a DEC 3000 or 4000 series system, note the following:

• On DEC 3000 series systems, you can boot through the InfoServer with an Ethernet PMAD device or FDDI DEFTA device by specifying the device name as “n/ESA0”. The value forn is the TURBOchannel slot number, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. For more information, see Section A.1.8.

• On DEC 4000 series, you must specify the ISL file name in uppercase (APB_1073).

3. The InfoServer ISL program then displays the following menu:

   
Network Initial System Load Function
Version 1.2


  FUNCTION         FUNCTION
    ID
    1     -        Display Menu
    2     -        Help
    3     -        Choose Service
    4     -        Select Options
    5     -        Stop

Enter a function ID value:

4. Respond to the prompts as follows, pressing the Return key after each entry:

a. Enter 3 for the function ID.

b. Enter 2 for the option ID.

c. Enter the service name (ALPHA0731).

A sample display follows:

Enter a function ID value: 3[Return]

OPTION          OPTION
   ID
   1     -       Find Services
   2     -       Enter known Service Name

Enter an Option ID value: 2[Return]
Enter a Known Service Name: ALPHA0731[Return]

$Q:\adept8\entities\note.eps$ Note

If you boot the OpenVMS Alpha operating system CD–ROM from an InfoServer system but lose your connection during the upgrade procedure (the system is unresponsive and pressing Ctrl/Y does not return you to the menu), do the following:

1. Reboot the OpenVMS Alpha operating system CD–ROM.

2. Enter the DCL environment by choosing option 7 from the menu.

3. Mount the device containing your backup copy of the target disk and the device that is your target disk.

4. Restore the backup copy of your target disk by entering the appropriate BACKUP commands. (See Appendix B for complete information about using MOUNT and BACKUP commands to restore a system disk.)

5. Log out from the DCL environment.

6. Perform the upgrade again by choosing the upgrade option (1) from the menu and following the procedures described in this chapter.

7.2 Performing the Upgrade

The following sections describe how to upgrade from the operating system CD–ROM.

7.2.1 Choosing the Upgrade Option

After you boot the operating system CD–ROM, choose the upgrade option (1) from the menu displayed on the screen. The display is similar to the following:

     OpenVMS (TM) Alpha Operating System, Version 7.3-1

    Copyright (c) 2002 -- All rights reserved.

    Compaq Information Technologies Group, L.P.

    Installing required known files...

    Configuring devices...

    ****************************************************************

    You can install or upgrade the OpenVMS Alpha operating system
    or you can install or upgrade layered products that are included
    on the OpenVMS Alpha operating system CD-ROM.
    
    You can also execute DCL commands and procedures to perform
    "standalone" tasks, such as backing up the system disk.
    
    Please choose one of the following:

        1)  Upgrade, install or reconfigure OpenVMS Alpha Version 7.3-1
        2)  Display products and patches that this procedure can install
        3)  Install or upgrade layered products and patches
        4)  Show installed products
        5)  Reconfigure installed products
        6)  Remove installed products
        7)  Execute DCL commands and procedures
        8)  Shut down this system

Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1

The OpenVMS Alpha operating system CD-ROM may contain patch kits. If it does, information similar to the following will be displayed:

    The following PATCH kits are present on the OpenVMS Alpha
    distribution media.

    ----------------------------------- ----------- ----------
    PRODUCT                             KIT TYPE    KIT FORMAT
    ----------------------------------- ----------- ----------
    DEC AXPVMS DNVOSIECO01 V7.3         Patch       Sequential
    DEC AXPVMS TCPIP_ECO V5.1-153       Patch       Sequential
    DEC AXPVMS TCPIP_ECO V5.1-152       Patch       Sequential
    DEC AXPVMS TCPIP_ECO V5.1-151       Patch       Sequential
    DEC VAXVMS TCPIP_ECO V5.1-153       Patch       Sequential
    DEC VAXVMS TCPIP_ECO V5.1-152       Patch       Sequential
    DEC VAXVMS TCPIP_ECO V5.1-151       Patch       Sequential
    ----------------------------------- ----------- ----------

    7 items found

    Please consult the OpenVMS Alpha Upgrade and Installation Manual,
    the Release Notes, and the Cover Letter to determine if any or
    all of these patches may be required for your system.

7.2.2 Choosing INITIALIZE or PRESERVE

After you choose the upgrade option, the system displays the following information and prompts:

***********************************************************

    The installation procedure will ask a series of questions.

          () - encloses acceptable answers
          [] - encloses default answers

    Type your response and press the <Return>key.  Type:

          ? - to repeat an explanation
          ^ - to change prior input (not always possible)
          Ctrl/Y - to exit the installation procedure

    There are two choices for Installation/Upgrade:

    INITIALIZE - removes all software and data files that were
        previously on the target disk and installs OpenVMS Alpha.

    PRESERVE -- installs or upgrades OpenVMS Alpha on the target disk
        and retains all other contents of the target disk.

   * NOTE: You cannot use PRESERVE to install OpenVMS Alpha on a disk on
        which OpenVMS VAX or any other operating system is installed.

Do you want to INITIALIZE or to PRESERVE? [PRESERVE])

For an upgrade, press the Return key to accept the default (PRESERVE).

7.2.3 Specifying the Target Disk

Next, the procedure asks you for the name of the target disk. If you enter a question mark (?), the system displays a list of devices on your system. Select the appropriate disk and respond to the prompt. For example:

You must enter the device name for the target disk on which
OpenVMS Alpha will be installed.

Enter device name for target disk: (? for choices) dkb400

MKA500 is not a disk device

7.2.4 Specifying the Volume Label

The system then prompts you for the volume label and asks if the information is correct. You can accept the default label assigned by the system (AXPVMSSYS) or specify a different volume label (with a limit of 12 characters that can include the letters A to Z, numbers 0 through 9, and the dollar sign($), hyphen (-), and underscore(_) characters).

$Q:\adept8\entities\note.eps$ Note

Compaq strongly recommends that the volume labels for all disks on your system or OpenVMS Cluster have unique labels. If a disk that has the same label as the system disk is mounted, various OpenVMS components will not function as intended.

                  
    DKB400: is now labeled ALPHASYS.

Do you want to keep this label? (Yes/No)

7.2.5 Specifying the On-Disk Structure Level

If the target disk is currently initialized with On-Disk Structure Level 2 (ODS-2), you now have the option to convert the disk to On-Disk structure Level 5 (ODS-5).

For details about ODS-2 and ODS-5 file systems, refer to the OpenVMS System Manager’s Manual. A brief summary follows:

• ODS-2

ODS-2 allows for full compatibility with all OpenVMS VAX systems and with OpenVMS Alpha systems prior to Version 7.2.

• ODS-5

– ODS-5 supports file names that are longer and have a wider range of legal characters. This feature permits use of file names similar to those in a Windows or UNIX environment.

– ODS-5 supports hard links to files, access dates, and files whose names differ only by case.

– ODS-5 volumes cannot be mounted on any version of OpenVMS prior to Version 7.2.

The  target  system disk is currently at On-Disk Structure Level 2
    (ODS-2).  It can be converted to On-Disk Structure Level 5 (ODS-5).
    (? for more information)

If you choose not to change to ODS-5, the upgrade continues. The target disk is mounted and page and swap files are created. For example:

  Do you want to convert the target system disk to ODS-5? (Yes/No/?) No

    OpenVMS Alpha will be upgraded on DKB400:.

If you choose to change to ODS-5, you will be given the option to enable hard links. For more information about hard links, refer to the OpenVMS Alpha Version 7.3–1 New Features and Documentation Overview. The upgrade will then continue.

  Do you want to convert the target system disk to ODS-5? (Yes/No/?) Yes

    DKB400: has been converted to ODS-5.

    Information on converting ODS-5 disks back to ODS-2 can be found
     in the Compaq OpenVMS System Manager’s Manual.

    Hard links can be enabled on ODS-5 disks. (? for more information)
    (***Enabling hard links can take up to 5-10 minutes or more.***)

  Do you want to enable hard links? (Yes/No)

If you choose to enable hard links, the procedure automatically executes an ANALYZE/DISK_STRUCTURE/REPAIR operation to correctly set the reference counts. This operation can take 5 to 10 minutes or longer, depending on the complexity of the system disk configuration, the number of layered products installed, and the number of user files. When the process completes, a message similar to the following is displayed:

    Hard links have been enabled on DKB400:.

    OpenVMS Alpha will be upgraded on DKB400:.

7.2.6 Checking Related Software

At this point the upgrade performs checks of some related software products.

7.2.6.1 Spiralog

If your system has Spiralog installed, the following message is displayed:

Either SPIRALOG is installed or SYS$SYSTEM:SPIRALOG.EXE is present on
the target system. SPIRALOG is no longer supported; it will not work
and can cause serious problems that are difficult to diagnose.

If installed, SPIRALOG must be removed before upgrading.

If SPIRALOG is not installed but SYS$SYSTEM:SPIRALOG.EXE is present
on the target system, this file must be deleted in order to prevent
the upgraded system from generating errors.
(Check common and specific directories for SPIRALOG.EXE.)

Termination is strongly recommended.

Do you want to terminate? (Yes/No) [YES]

Spiralog will not work with OpenVMS Alpha Version 7.3–1. If you have any version of Spiralog installed on your system, uninstall it before upgrading to OpenVMS Alpha Version 7.3–1.

7.2.6.2 DECamds

Beginning with OpenVMS Version 7.3 and DECamds Version 7.3, certain parts of DECamds that were previously supplied with the layered product kit are now incorporated into OpenVMS. Because of this, prior versions of DECamds must be removed.

If the upgrade procedure detects a prior version of DECamds, it will display the following message and automatically remove the prior version of DECamds. Note that you must reinstall DECamds if you wish to continue using it.

            The target system contains a version of DECamds that is not
            compatible with this version of the operating system.

            If you continue DECamds will be removed.  A current version of
            DECamds can be installed after the upgrade completes.

7.2.6.3 PATHWORKS

If PATHWORKS is installed on the system, OpenVMS Version 7.3–1 requires PATHWORKS Version V6.1 or later. The installation determines the PATHWORKS version and displays the following message if PATHWORKS Version 5 or earlier is present:

PATHWORKS V5 is installed on the target system.

This version of PATHWORKS will not work on OpenVMS V7.3-1.

Before you upgrade OpenVMS you must either upgrade to a supported
version of PATHWORKS or migrate to Advanced Server.

Please refer to the PATHWORKS or Advanced Server installation
guides for additional information.

Do you want to continue? (Yes/No) [NO]

The default is to terminate the upgrade. You must explicitly enter Yes and press the Return key to continue.

7.2.6.4 Advanced Server for OpenVMS

If Advanced Server for OpenVMS is installed on the system, OpenVMS Version 7.3–1 requires Advanced Server for OpenVMS Version 7.3 or higher.

If you plan to upgrade your OpenVMS system, and a version of Advanced Server for OpenVMS earlier than V7.3 is present, first upgrade Advanced Server for OpenVMS to V7.3 before you upgrade the OpenVMS operating system.

7.2.7 Checking OpenVMS Cluster Membership

The procedure now asks if your system will be part of a cluster. The display is similar to the following:

Will this system be a member of an OpenVMS Cluster? (Yes/No) Yes

You should answer Yes if the system will be an OpenVMS Galaxy instance or a member of an OpenVMS cluster. Unlike an installation, answering Yes to this question will not cause SYS$MANAGER:CLUSTER_CONFIG.COM to be run. However, correct cluster membership information is required by the upgrade procedure.

7.2.8 Becoming an OpenVMS Galaxy Instance

The procedure next asks if your system will be an instance in an OpenVMS Galaxy. The display is similar to the following:

Will this system be an instance in an OpenVMS Galaxy? (Yes/No) Yes

If you answer Yes to this question, and you also answered Yes to the OpenVMS Cluster question, then information about required remedial kits is displayed.

7.2.9 Upgrading Windowing and Networking Products

The procedure next selects the following Compaq software that is installed on your system:

• DECwindows Motif for OpenVMS

• DECnet-Plus for OpenVMS or DECnet Phase IV for OpenVMS

• TCP/IP Services for OpenVMS

$Q:\adept8\entities\note.eps$ Note

If you do not have DECnet for OpenVMS Alpha software installed on your system, you can install that software during the upgrade. Note, however, that you cannot have DECnet-Plus and DECnet Phase IV concurrently installed on your system.

Once you have DECnet-Plus and TCP/IP installed on your system, you can run DECnet applications over your TCP/IP network. Please see the DECnet-Plus for OpenVMS Management Guide for more information on DECnet over TCP/IP.

Beginning with OpenVMS V7.3–1, a new implementation of TCP/IP Services for OpenVMS is available. This new implementation replaces the UCX product. Older, UCX versions of TCP/IP Services for OpenVMS can be upgraded to this new implementation. Note, however, that you CANNOT have both the new TCPIP implementation and the older UCX implementation concurrently installed on your system.

If you are upgrading DECnet, the procedure removes the existing version of DECnet during the upgrade. For example, if DECnet Phase IV for OpenVMS is installed on your system, and you upgrade to DECnet-Plus for OpenVMS, DECnet Phase IV for OpenVMS will be removed during the upgrade procedure.

The display is similar to the following:

    If necessary, the following products will be upgraded along with 
    the OpenVMS operating system:

        o DECwindows Motif for OpenVMS Alpha
        o DECnet-Plus for OpenVMS Alpha
        o DECnet Phase IV for OpenVMS Alpha
        o Compaq TCP/IP Services for OpenVMS

    If you want to add or delete these products, you can do so later in
    the upgrade by answering NO to the following question:

        "Do you want the defaults for all product options?"    

    Beginning with OpenVMS V7.1, DECnet-Plus is provided with the
    OpenVMS operating system.  Compaq recommends that DECnet
    users install DECnet-Plus.  DECnet Phase IV applications are
    supported by DECnet-Plus.

    DECnet Phase IV is also provided as an option.  Support for
    DECnet Phase IV is available through a Prior Version Support
    Contract available through Compaq Services.

    Once you have DECnet-Plus and TCP/IP installed on your
    system, you can run DECnet applications over your 
    TCP/IP network.  Please see the DECnet-Plus for OpenVMS 
    Management Guide for more information on DECnet over
    TCP/IP.    


    Do you want to install DECnet-Plus for OpenVMS Alpha V7.3-1? (Yes/No) [YES] n

    DECnet Phase IV for OpenVMS Alpha is installed on your system.
    It will be upgraded.

    Beginning with OpenVMS V7.2, a new implementation of Compaq
    TCP/IP Services became available.  This new implementation replaces
    the UCX product.  Older, UCX version of Compaq TCP/IP Services for OpenVMS
    can be upgraded to this new implementation.

    Compaq TCP/IP Services for OpenVMS is not installed on your system.
    It will not be installed.

Some of the windowing and networking products may have versions installed that are below the current versions, but will still work on OpenVMS Version 7.3–1. In this case you will see messages similar to the following:

    DECwindows Motif is already installed.
    You can keep the installed version or upgrade to V1.2-6.

    Do you want to upgrade to V1.2-6? (Yes/No) [YES]

You can choose to keep the currently-installed version, or to upgrade to the latest version supplied with OpenVMS Version 7.3–1. If you choose to keep the currently-installed version, you should verify what level of support is available from Compaq for this version.

7.2.10 Updating Time Zone Information

For local time zone support to work correctly, the time zone that accurately describes the location you want to be considered as your default time zone must be set. In addition, your system must be correctly configured to use a valid OpenVMS time differential factor (TDF). The time zone installation is always set on new installations, producing the three following files on your system:

[VMS$COMMON.SYSEXE]SYS$TIMEZONE.DAT
[VMS$COMMON.SYSEXE]SYS$TIMEZONE_SRC.DAT
[VMS$COMMON.SYS$STARTUP]TDF$UTC_STARTUP.COM

If these files are present, the procedure continues with Section 7.2.11. If any of these files are missing, the time zone setting procedure will be invoked.

The procedure displays a series of time zone menus, and prompts you to make selections from each. You begin by selecting the desired time zone from the main time zone menu.

Some time zone choices cause an additional menu to be displayed. This happens when the time zone you select has subcomponents. For example, if you choose the United States (US) time zone from the main menu, a second menu displays the specific time zones within the United States. You then select the menu item that best represents the desired time zone.

A sample display follows:

  Configuring the Local Time Zone


  TIME ZONE SPECIFICATION -- MAIN Time Zone Menu

      1) AFRICA               16) GREENWICH            31) POLAND
      2) AMERICA              17) HONGKONG             32) PRC
      3) ANTARCTICA           18) ICELAND              33) ROC
      4) ASIA                 19) INDIAN               34) ROK
      5) ATLANTIC             20) IRAN                 35) SINGAPORE
      6) AUSTRALIA            21) ISRAEL               36) SYSTEMV
      7) BRAZIL               22) JAMAICA              37) TURKEY
      8) CANADA               23) JAPAN                38) UCT
      9) CET                  24) LIBYA                39) UNIVERSAL
     10) CHILE                25) MET                  40) US
     11) CUBA                 26) MEXICO               41) UTC
     12) EET                  27) NAVAJO               42) W-SU
     13) EGYPT                28) NZ-CHAT              43) WET
     14) FACTORY              29) NZ                   44) ZULU
     15) GB-EIRE              30) PACIFIC

      0) GMT
 
Select the number above that best represents the desired time zone: 40

  US Time Zone Menu

      1) ALASKA                5) EAST-INDIANA          9) MICHIGAN
      2) ALEUTIAN              6) EASTERN              10) MOUNTAIN
      3) ARIZONA               7) HAWAII               11) PACIFIC
      4) CENTRAL               8) INDIANA-STARKE       12) SAMOA

      0) return to Main Time Zone Menu

Select the number above that best represents the desired time zone: 6

You selected EASTERN / US as your time zone.
Is this correct? (Yes/No) [YES]:

    Configuring the Time Differential Factor (TDF)


    Default Time Differential Factor for standard time is -5:00.
    Default Time Differential Factor for daylight saving time is -4:00.


    The Time Differential Factor (TDF) is the difference between your
    system time and Coordinated Universal Time (UTC).  UTC is similar
    in most respects to Greenwich Mean Time (GMT).

    The TDF is expressed as hours and minutes, and should be entered
    in the hh:mm format.  TDFs for the Americas will be negative
    (-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia and Australia
    will be positive (1:00, 2:00, etc.).

This time zone supports daylight saving time.
Is this time zone currently on daylight saving time? (Yes/No): n

Enter the Time Differential Factor [-5:00]:

    NEW SYSTEM TIME DIFFERENTIAL FACTOR = -5:00

Is this correct? [Y]:

For more information about TDF and local time zone support, see the OpenVMS System Manager’s Manual.

7.2.11 Choosing Descriptive Help Text

The system next prompts you as follows:

     The installation operation can provide brief or detailed descriptions.
     In either case, you can request the detailed descriptions by typing "?".

Do you always want detailed descriptions? (Yes/No) [No]

If you answer Yes, the system will display additional explanatory text with each prompt.

7.2.12 Configuration Options

If you are using the OpenVMS Alpha Version 7.3–1 CD-ROM and have selected a target disk that already has Version 7.3–1 installed, you are presented with several configuration options. A sample display follows:

Version 7.3-1 of the OpenVMS operating system is already installed 
on the target disk.  You may choose one of the following actions:

  o Reconfigure the OpenVMS platform.
    This action will allow you to change your selections of which of  
    the windowing and network products you included with your OpenVMS 
    operating system installation.

  o Reconfigure the OpenVMS operating system.
    This action will allow you to change your choices about which
    options you included for the OpenVMS operating system.

  o Reinstall the OpenVMS operating system.
    This action will cause ALL operating system  files to be replaced.
    You can also change your choices about which options you included
    for the OpenVMS operating system.

    Reinstall will take longer than Reconfigure.  Reinstall may be
    appropriate if you suspect that files in the operating system,
    or in the windowing and network products have become corrupted.


If you want to reinstall any of the windowing and network products, 
choose "Install or upgrade layered products and patches" (option 3) 
from the main menu.

If you want to change your choices about which options you included
for any of the windowing and network products, choose "Reconfigure
installed products" (option 5) from the main menu.

Please choose one of the following:

    1)  Reconfigure the OpenVMS platform.
    2)  Reconfigure the OpenVMS operating system.
    3)  Reinstall the OpenVMS operating system.
    4)  Return to the Main Menu (abort the upgrade/installation).


Enter choice or ? for help: (1/2/3/4/?)

See Section 8.9 for additional configuration information.

7.2.13 Saving Archived Files

By default, the OpenVMS upgrade deletes files that were archived as filename.extension_OLD by OpenVMS remedial kits. If you do not want to delete these files, you can save them by taking one of the following steps:

1. When the script asks if you want the defaults for all options, answer NO. (This script is shown in the example in Section 7.2.14.) Step through the options and deselect the option to delete files archived by remedial kits. This will save all such files.

2. Before beginning the upgrade, rename any _OLD files that you want to save. Files that you do not rename will be deleted.

Note that the upgrade will not delete all files with an extension ending in _OLD. Only those _OLD files that were archived by OpenVMS remedial kits will be deleted.

7.2.14 Selecting Components

As you begin the upgrade procedure, the system asks if you want all the default values, meaning all the files and subgroups of files for each component included in the operating system. The display is similar to the following:

The following product has been selected:
     DEC AXPVMS OPENVMS V7.3-1       Platform (product suite) 
 

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.
 
DEC AXPVMS OPENVMS V7.3-1: OpenVMS and related products platform
 
    COPYRIGHT (c) 14-MAY-2002 -- All rights reserved
 
    Compaq Information Technologies Group, L.P.
 
Do you want the defaults for all options? [YES] 

    DEC AXPVMS DECNET_PHASE_IV V7.3-1: DECNET_PHASE_IV

      Support addendum to DECnet Phase IV service contract required

      Do you want to continue? [YES]

During an upgrade, the POLYCENTER Software Installation utility defines “default values” as the values that you selected when you last installed or upgraded the OpenVMS Alpha operating system on your system. Therefore, before you respond to the prompt, note the following:

• If you answer YES (by pressing the Return key) to accept the default values, you will receive the same components that you selected when you last installed or upgraded the system (instead of all the components currently available) plus any new components that were not in the previous version of the OpenVMS Alpha operating system.

• If you want to include or exclude any components differently from the last installation or upgrade, you must answer NO and then respond to the prompts for each option, even those that you are not changing.

• If you want to review the current defaults first, you can answer NO. Then answer YES when the system asks if you want to view the values.

If you review the defaults and are satisfied, answer YES to the prompt asking if you are satisfied with the values. However, if you want to make changes, answer NO to that question and then answer YES when the system asks if you want to reenter the values.

When selecting components, note the following as well:

• Whether you choose all the default values or select individual files, the system will allow you to view your selections and make changes (if necessary).

• If you are not sure whether you want certain components, request help by entering a question mark (?) at the prompt for that component (or group of components).

• If you decide after the upgrade to change which OpenVMS Alpha operating system components you want installed on your system, you must reconfigure the installation as described in Section 1.3.3.2.

• After you boot the upgraded system disk and log in, you can obtain information about individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($).

$Q:\adept8\entities\note.eps$ Note

For a complete list of components included with the OpenVMS Alpha Version 7.3–1 operating system, see Section 3.5.3.

7.2.15 Completing the Upgrade

When you have answered all the prompts and selected the components you want installed, the system allows you to review your selections (and make changes if necessary) and then displays messages about the following:

• Notification that DECwindows Motif for OpenVMS, DECnet-Plus for OpenVMS, DECnet Phase IV for OpenVMS, or TCP/IP Services for OpenVMS has been upgraded (or installed) on your system.

• Notification that the upgrade has been completed.

• Information about running AUTOGEN.

• The menu.

The following is a sample display.

$Q:\adept8\entities\note.eps$ Note

If you perform two installations at the same time to systems connected via MEMORY CHANNEL, you may see a message similar to the following every 5 seconds:

%PMA0 CPU00: 30-MAY-2002 14:58:40 Remote System Conflicts with 
Known System - REMOTE NODE
%PMA0 CPU00: 30-MAY-2002 14:58:45 Remote System Conflicts with 
Known System - REMOTE NODE

Disregard the message. The installation or upgrade will proceed normally and the messages will not be present when the system reboots with its real node name.

Do you want to review the options? [NO] 

Execution phase starting ...

The following products will be installed to destinations:
    CPQ AXPVMS CDSA V1.0                   DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS DECNET_OSI V7.3-1           DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS DWMOTIF V1.2-6              DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS OPENVMS V7.3-1              DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS VMS V7.3-1                  DISK$ALPHASYS:[VMS$COMMON.]

The following products will be removed from destinations:
    DEC AXPVMS DECNET_OSI V7.3             DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS DWMOTIF V1.2-5              DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS OPENVMS V7.3                DISK$ALPHASYS:[VMS$COMMON.]
    DEC AXPVMS VMS V7.3                    DISK$ALPHASYS:[VMS$COMMON.]

Portion done: 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100%

The following products have been installed:
    CPQ AXPVMS CDSA V1.0                   Layered Product
    DEC AXPVMS DECNET_OSI V7.3-1           Layered Product
    DEC AXPVMS DWMOTIF V1.2-6              Layered Product
    DEC AXPVMS OPENVMS V7.3-1              Platform (product suite)
    DEC AXPVMS VMS V7.3-1                  Operating System
The following products have been removed:
    DEC AXPVMS DECNET_OSI V7.3             Layered Product
    DEC AXPVMS DWMOTIF V1.2-5              Layered Product
    DEC AXPVMS OPENVMS V7.3                Platform (product suite)
    DEC AXPVMS VMS V7.3                    Operating System

    The upgrade is now complete.

    When the newly upgraded system is first booted, a special
    startup procedure will be run.  This procedure will:

        o  Run AUTOGEN to set system parameters.
        o  Reboot the system with the newly set parameters.

    You may shut down now or continue with other operations.


  Process AXPVMS_INSTALL logged out at 12-MAY-2002 15:34:22.47

Press Return to continue...

    ****************************************************************

    You can install or upgrade the OpenVMS Alpha operating system
    or you can install or upgrade layered products that are included
    on the OpenVMS Alpha operating system CD-ROM.
    
    You can also execute DCL commands and procedures to perform
    "standalone" tasks, such as backing up the system disk.
    
    Please choose one of the following:

        1)  Upgrade, install or reconfigure OpenVMS Alpha Version 7.3-1
        2)  Display products and patches that this procedure can install
        3)  Install or upgrade layered products and patches
        4)  Show installed products
        5)  Reconfigure installed products
        6)  Remove installed products
        7)  Execute DCL commands and procedures
        8)  Shut down this system

7.2.16 Install Layered Products or Shut Down

If you want to install layered products, go to Section 7.3.

If you do not want to install layered products or perform any other operations prior to booting the upgraded disk, do the following:

1. Shut down the system by choosing the shutdown option (8) from the menu.

2. Go to Section 7.4.

7.3 Installing Layered Products

You may see the following product name while installing layered products:

        DEC AXPVMS UCX V4.2-PLACEHOLDER

Do not attempt to install this kit. This is a "dummy" that is needed to facilitate upgrading from the prior UCX implementation of TCP/IP Services for OpenVMS to the new implementation.

If you do attempt to install this kit, the following message will be displayed:

          The UCX implementation of TCP/IP Services is obsolete and is not
          supported on OpenVMS V7.3-1 and higher versions.

          Starting with OpenVMS V7.3-1, the UCX implementation of TCP/IP
          services is replaced by the new TCPIP product.

          This is a placeholder kit to satisfy OpenVMS upgrade requirements
          so that UCX can be automatically upgraded to TCPIP.

          You cannot use this kit to install UCX.

The installation will then terminate.

You can install (or upgrade to) the new implementation of TCP/IP Services for OpenVMS, version 5.1, as part of the OpenVMS upgrade. If you wish to install version 5.1 separately, choose the product:

        DEC AXPVMS TCPIP V5.1

To install layered products using the POLYCENTER Software Installation utility, choose option 2 to view the list and then option 3 to perform the installation. For example:

    Please choose one of the following:

        1)  Upgrade, install or reconfigure OpenVMS Alpha Version 7.3-1
        2)  Display products and patches that this procedure can install
        3)  Install or upgrade layered products and patches
        4)  Show installed products
        5)  Reconfigure installed products
        6)  Remove installed products
        7)  Execute DCL commands and procedures
        8)  Shut down this system

Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 2

        The following versions of the OpenVMS operating system, the
        DECwindows graphical user interface and network products.
        are available on the OpenVMS Distribution compact disk.
        They can be installed by selecting choice 1:

    DEC AXPVMS VMS version V7.3-1
    DEC AXPVMS DWMOTIF version V1.2-6
    DEC AXPVMS DECNET_OSI version V7.3-1
    DEC AXPVMS DECNET_PHASE_IV version V7.3-1
    DEC AXPVMS TCPIP version V5.1  

        The following Layered Product kits are available on the OpenVMS
        Distribution Compact Disk.  They can be installed by selecting
        choice 3.  If already installed, they can be reconfigured by
        selecting choice 5, or removed by selecting choice 6.

    ----------------------------------- ----------- ----------
    PRODUCT                             KIT TYPE    KIT FORMAT
    ----------------------------------- ----------- ----------
    DEC AXPVMS DECNET_OSI V7.3-1        Full LP     Sequential
    DEC AXPVMS DECNET_PHASE_IV V7.3-1   Full LP     Sequential
    DEC AXPVMS DWMOTIF V1.2-6           Full LP     Sequential
    DEC AXPVMS TCPIP V5.1               Full LP     Sequential
    DEC AXPVMS UCX V4.2-99PLACEHOLDER   Full LP     Sequential
    ----------------------------------- ----------- ----------

    5 items found

    Press Return to continue...

    ****************************************************************

    You can install or upgrade the OpenVMS Alpha operating system
    or you can install or upgrade layered products that are included
    on the OpenVMS Alpha operating system CD-ROM.
    
    You can also execute DCL commands and procedures to perform
    "standalone" tasks, such as backing up the system disk.
    
    Please choose one of the following:

        1)  Upgrade, install or reconfigure OpenVMS Alpha Version 7.3-1
        2)  Display products and patches that this procedure can install
        3)  Install or upgrade layered products and patches
        4)  Show installed products
        5)  Reconfigure installed products
        6)  Remove installed products
        7)  Execute DCL commands and procedures
        8)  Shut down this system


Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 3
    
    ***********************************************************

    If you choose to install or upgrade to DECwindows Motif,
    please note the following:

      o If you did not select the OpenVMS DECwindows base support
        and workstation files options, DECwindows Motif will not run.
        You must add these options to use DECwindows Motif.

      o If you are upgrading DECwindows Motif from Version 1.1 and
        want to save the OSF/Motif Release 1.1.3 programming files,
        DO NOT upgrade now.  Instead, see the DECwindows Motif
        Installation Manual and follow the instructions for running
        PCSI_INSTALLATION.COM.

    If you choose to install or upgrade DECnet-Plus or DECnet Phase IV,
    please note the following:

      o If you did not select the OpenVMS DECNET option, neither version
        of DECnet will run.  You must add this option to use DECnet.


    You must enter the device name for the target disk on which
    the layered product(s) install will be performed.

Enter device name for target disk: (? for choices) DKB400

    DKB400: is labeled ALPHASYS.


The installation can provide brief or detailed descriptions.
In either case, you can request the detailed descriptions by typing "?".

Do you always want detailed descriptions? (Yes/No) [No]

   1 - DEC AXPVMS DECNET_OSI V7.3-1        Layered Product
   2 - DEC AXPVMS DECNET_PHASE_IV V7.3-1   Layered Product
   3 - DEC AXPVMS DWMOTIF V1.2-6           Layered Product
   4 - DEC AXPVMS TCPIP V5.1               Layered Product
   5 - DEC AXPVMS UCX V4.2-99PLACEHOLDER   Layered Product
   6 - All products listed above
   7 - Exit

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

If you do not want to perform any other operations after you install the layered products, do the following:

1. Shut down the system by choosing the shutdown option (8) from the menu.

2. Go to the next section to perform specific tasks after the system shuts down.

7.4 What to Do After the Shutdown

After the system shuts down, you need to perform certain tasks, depending on the configuration of your system and the type of upgrade you are performing. Refer to the appropriate section.

$Q:\adept8\entities\note.eps$ Note

When you boot your system following the shutdown (regardless of the type of upgrade and configuration), note that your system will automatically run AUTOGEN and boot again.

7.4.1 Standalone Upgrade

If you are upgrading a standalone system:

1. Reboot the system.

2. Log in to the system.

3. Go to Chapter 8, After Upgrading the OpenVMS Alpha Operating System to perform additional postupgrade procedures.

7.4.2 Concurrent OpenVMS Cluster Upgrade

If you are performing a concurrent upgrade in an OpenVMS Cluster environment, refer to the following table:

IF ...

THEN ...

you have one system disk,

do the following:

1. Reboot each system that uses the upgraded disk.

2. Go to Chapter 8, After Upgrading the OpenVMS Alpha Operating System.

you have multiple system disks,

do the following:

1. Reboot the upgraded system.

2. Repeat the upgrade process for each system disk in the cluster, beginning with the preupgrade tasks described in Chapter 5, Before Upgrading the OpenVMS Alpha Operating System.

3. Reboot each system in the cluster.

4. Log in to an upgraded system.

5. Go to Chapter 8, After Upgrading the OpenVMS Alpha Operating System to perform additional postupgrade procedures.

7.4.3 Rolling OpenVMS Cluster Upgrade

If you are performing a rolling upgrade in an OpenVMS Cluster environment, do the following:

1. Log in to the upgraded system.

2. Go to Chapter 8, After Upgrading the OpenVMS Alpha Operating System to perform additional postupgrade procedures. (You will reboot the other systems that boot from the upgraded disk after you complete those tasks.)

8 After Upgrading the OpenVMS Alpha Operating System

After you upgrade the OpenVMS Alpha operating system, you need to perform several important tasks before you can use the system. These tasks, described in the order in which you perform them, are as follows:

• Reforming the shadow set (if applicable)

• Registering new licenses

• Examining the AUTOGEN report file

• Modifying the system parameters file (MODPARAMS.DAT)

• Examining your command procedures

• Initializing CDSA

• Testing the system with UETP, the user environment test package

• Expanding the system libraries

• Adding and removing operating system files

• Preparing your OpenVMS Alpha system and your PC to run OpenVMS Management Station

• Installing layered products

• Backing up the customized system disk

• Rebooting cluster members (if applicable)

• Running AUTOGEN

• Completing the postupgrade checklist

8.1 Reforming the Shadow Set

If you have upgraded a disk in a volume shadowing environment, you must now reform the shadow set as follows:

1. Enter the SHOW DEVICE D command to display a list of disks available on your system. For example:

$ SHOW DEVICE D
Device                Device     Error    Volume       Free  Trans Mnt
Name                 Status     Count     Label      Blocks Count Cnt
$11$DKB100:  (NODE1)  Online        0
$11$DKB200:  (NODE1)  Mounted       0      ALPHA070   918150    1  31

2. Enter a command in the following format:

MOUNT/CONFIRM/SYSTEM DSAn: /SHADOW=(upgraded-disk:,new-member:) volume-label

Note the following conventions:

• DSAn: is the virtual unit name of the shadow set.

• upgraded-disk: is the name of the shadowed system disk you just upgraded.

• new-member: is the name of the disk you want to add as a member of the shadow set.

• volume-label is the volume label of the shadowed system disk you just upgraded.

$Q:\adept8\entities\note.eps$ Note

When you reform the shadow set, the contents of the new member are replaced by the contents of the disk you upgraded. Specifying the /CONFIRM qualifier reminds you of this fact, confirming that you are specifying the correct name of a disk that either is blank or contains files you no longer need.

Example

$ MOUNT/CONFIRM/SYSTEM DSA54: /SHADOW=($11$DKB200:,$11$DKB100:) ALPHA0731

%MOUNT-F-SHDWCOPYREQ, shadow copy required
Virtual Unit - DSA54 Volume label ALPHA0731
Member Volume label Owner UIC
$11$DKB100: (NODE1) SCRATCH [100,100]
Allow FULL shadow copy on the above member(s)? [N]: YES

8.2 Registering New Licenses

If you need to register new OpenVMS Alpha or layered product licenses, you can do so by entering the following command:

$ @SYS$UPDATE:VMSLICENSE

You can also use the LICENSE REGISTER command.

For information about registering licenses, see the following:

• Section 3.4 in Chapter 3, Installing the OpenVMS Alpha Operating System

• Appendix C

• The OpenVMS License Management Utility Manual

8.3 Examining the AUTOGEN Report File

When AUTOGEN runs, it writes informational and, if necessary, warning messages to the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You should examine the contents of this report file.

To view AGEN$PARAMS.REPORT on your screen, enter the following command and press the Return key:

$ TYPE SYS$SYSTEM:AGEN$PARAMS.REPORT

You can also print this file or examine it using the EDIT/READ_ONLY command.

For more information on AGEN$PARAMS.REPORT, see the OpenVMS System Manager’s Manual.

If the report includes a message similar to the following, you might need to modify the size of the page, swap, or dump file:

%AUTOGEN-W-DSKSPC, The disk on which DKA0:[SYS0.SYSEXE]PAGEFILE.SYS
         resides would be over 95% full if it were modified to hold 20000
         blocks.

For more information about modifying the sizes of the page, swap, and dump files, see the next section.

8.4 Modifying the System Parameters File

Review the file SYS$SYSTEM:MODPARAMS.DAT. The upgrade procedure created a new version of this file. The old version is named SYS$SYSTEM:MODPARAMS.DAT_OLD. The new MODPARAMS.DAT file contains all the parameters in the old file, plus various parameters that the upgrade procedure added to ensure that all necessary system parameters are properly propagated from the prior version of OpenVMS. The upgrade procedure also adds comment lines to explain the source of the parameters in each section of the new MODPARAMS.DAT file.

Note that the old MODPARAMS.DAT is included in the new MODPARAMS.DAT each time an upgrade is performed. Because of this, if MODPARAMS.DAT is not reviewed and “cleaned up” after each upgrade, it will eventually contain many levels of duplicated parameters. For this reason, you should review MODPARAMS.DAT after each upgrade. This allows you to eliminate the duplication. You can also take this opportunity to modify any parameters, if necessary.

The following two sections are examples of instances where you need to modify parameters in MODPARAMS.DAT.

8.4.1 System File Sizes

AUTOGEN sets the following files at sizes appropriate for your system:

[SYSEXE]SYSDUMP.DMP

[SYSEXE]PAGEFILE.SYS

[SYSEXE]SWAPFILE.SYS

If you have special workloads or configurations, you can specify different sizes for these files by performing the following steps:

1. Log in to the SYSTEM account.

2. Enter the following command:

$ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES

3. If the file sizes displayed need to be adjusted, add symbols to the MODPARAMS.DAT file (described in detail in the OpenVMS System Manager’s Manual) and repeat step 2 until you are satisfied with the file sizes.

4. When you are satisfied with the file sizes, enter the following command to ensure that the modified system files are installed when the system is rebooted:

$ @SYS$UPDATE:AUTOGEN GENPARAMS REBOOT

8.4.2 OpenVMS Cluster Parameters

If you are upgrading an OpenVMS Cluster system, note the following:

• The upgrade procedure creates a new MODPARAMS.DAT for each system root on your system disk. Normally, there is one root for each Alpha computer that boots from the system disk. You must review each of these MODPARAMS.DAT files.

The MODPARAMS.DAT file for the system on which you are running is located in SYS$SYSTEM:MODPARAMS.DAT. The MODPARAMS.DAT files for other roots on the same system disk can be found in SYS$SYSDEVICE:[SYSx.SYSEXE]MODPARAMS.DAT, where x represents the root number; for example, SYS0, SYS1, SYS2, and so forth. (Valid root numbers may include hexadecimal digits -- SYSA, SYSB, and so forth.)

• Be sure the EXPECTED_VOTES value is correct. That value is the sum of all VOTES in the cluster. For example, if there are five Alpha computers in the cluster and each has one VOTE, the value is 5.

• As you reboot each Alpha computer, AUTOGEN runs automatically. The cluster forms when you have booted enough computers to attain cluster quorum.

8.5 Examining Your Command Procedures

The upgrade procedure retains the site-specific versions of the following files located in the [VMS$COMMON] directory:

[SYSMGR]LAT$SYSTARTUP.COM
[SYSMGR]LOGIN.COM
[SYSMGR]SYCONFIG.COM
[SYSMGR]SYLOGICALS.COM
[SYSMGR]SYLOGIN.COM
[SYSMGR]SYPAGSWPFILES.COM
[SYSMGR]SYSECURITY.COM
[SYSMGR]SYSHUTDWN.COM
[SYSMGR]SYSTARTUP_VMS.COM
[SYSMGR]TFF$SYSTARTUP.COM
[SYSMGR]WELCOME.TXT
[SYS$STARTUP]ESS$LAST_STARTUP.DAT

The upgrade procedure may provide new templates for some of these files with the .TEMPLATE extension. The new templates might include features that are not in your site-specific files. Check the templates against your site-specific files and edit your files as necessary.

8.6 Initializing CDSA

The Common Data Security Architecture (CDSA) is automatically installed with the operating system. However, before you can use CDSA, you must perform the following one-time, manual setup and installation procedure if CDSA has not been previously initialized on your system. You must have SYSPRV privileges to do this.

1. Increase your FILLM process quota by 100 before you initialize CDSA.

2. Execute the following command:

$ @SYS$STARTUP:CDSA$INITIALIZE

If you attempt to run this procedure when it has been run previously, you will get an error message.

$Q:\adept8\entities\note.eps$ Note

%PCSI-E-HRDREF, product CPQ AXPVMS CDSA Vn.n is referenced
by DEC AXPVMS OPENVMS V7.3-1
-PCSI-E-HRDRF1, the two products are tightly bound by this
software dependency

For more information about CDSA, refer to Open Source Security for OpenVMS Alpha, Volume 1: Common Data Security Architecture.

8.7 Testing the System with UETP

The User Environment Test Package (UETP) is a software package designed to test whether the OpenVMS Alpha operating sytem is installed correctly. As part of the postupgrade procedure, Compaq recommends that you run UETP to verify the upgrade.

For complete information about using UETP, see the OpenVMS System Manager’s Manual.

8.8 Expanding the System Libraries

Some of the larger system libraries ship with the OpenVMS operating system in a data-reduced (compressed) format. Expanding (that is, decompressing) these libraries gives the system faster access to them, but also consumes more disk space. See Section 4.9 and Table 4 –1 for more information about the libraries that ship in data-reduced format on OpenVMS Alpha systems. For complete details about expanding and reducing system library files and using LIBDECOMP.COM, refer to the OpenVMS System Manager’s Manual.

8.9 Adding and Removing Operating System Files

If you decide after the upgrade to change which OpenVMS Alpha operating system files you want installed on your system, you can use the menu system contained on the OpenVMS Alpha operating system CD–ROM to add or remove files.

Note that you can obtain information about individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($).

The procedure is as follows:

1. Mount and boot the OpenVMS Alpha operating system CD–ROM.

2. Choose option 1 from the menu.

3. Choose the PRESERVE option.

4. Enter the name of the device that contains the system disk and answer the questions.

The following is a sample reconfigure operation:

Answer NO to this question, and select the options you want as described in Section 3.5.2. A list of components is provided in Section 3.5.3. After you respond to the prompts, the display continues and the installation procedure completes as described in Section 3.5.4. The following is a continuation of the sample display:

    Do you want to review the options? [NO] 
 
Execution phase starting ...

The following product will be reconfigured:
    DEC AXPVMS VMS V7.3-1
Portion done: 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100%
The following product has been reconfigured:
    DEC AXPVMS VMS V7.3-1
.
.
.

For detailed instructions on how to remove the OpenVMS Alpha operating system from your disk, see Appendix E.

8.10 Preparing to Use OpenVMS Management Station

If you installed the OpenVMS Management Station software on your system (either by accepting all default values or by selecting the component manually during the upgrade procedure), you must perform several tasks on your OpenVMS Alpha system and your PC before you can use OpenVMS Management Station. These tasks include the following:

• Editing system files

• Starting OpenVMS Management Station on other nodes

• Verifying that you have the proper memory, disk space, media, and the required software to install and run OpenVMS Management Station on your PC

• Installing the client software on your PC

For complete information about preparing your OpenVMS system and your PC to run the OpenVMS Management Station server and client software, see Appendix D.

$Q:\adept8\entities\note.eps$ Note

8.11 Installing Layered Products

Except in certain instances, you should not have to reinstall layered products that you had on your system prior to the upgrade. However, if you need to install layered products, you can use the menu system included on the operating system CD–ROM to install certain layered products with the POLYCENTER Software Installation utility. If you did not install those layered products previously during the installation procedure, you can do so using the following procedure. To install layered products that require VMSINSTAL, see Section 8.11.1.

$Q:\adept8\entities\note.eps$ Note

1. Shut down the system (described in Appendix A ).

2. Boot the operating system CD–ROM (locally or from the InfoServer).

3. Choose option 2 from the menu to view which layered products can be installed using the POLYCENTER Software Installation utility.

4. Choose option 3 from the menu to install the layered products.

5. Shut down the system by selecting option 8 from the menu.

6. Boot from the system disk.

If the layered product that you want to install is not listed in the display, see the documentation you received with that layered product for installation information.

For additional information about installing layered products, see the OpenVMS System Manager’s Manual.

Be sure you back up the system disk after you install all your layered products.

$Q:\adept8\entities\note.eps$ Note

Compaq does not support PRODUCT INSTALL and other PRODUCT commands from the DCL option on the operating system CD–ROM. Not all products can be installed when booted from the CD–ROM. Those that can be installed in this manner require special considerations. If products do not appear in the layered products menu as described in the preceding steps in this section, please use the alternative procedure described in Section 8.11.1, or refer to the installation documentation for the specific product.

8.11.1 Alternate Procedure

The following is another method for installing layered products from the OpenVMS Alpha operating system CD–ROM:

1. From your running OpenVMS system (the target system disk), mount the OpenVMS Alpha operating system CD–ROM.

2. Locate the directories and files containing the available layered products by entering the following command (where, in the example, DKA400: is the device name of the CD–ROM):

$ DIRECTORY /NOHEAD/NOTRAIL DKA400:[*.KIT]

You can use the PRODUCT FIND command to locate kits that are installed using the POLYCENTER Software Installation utility. For example:

$ PRODUCT FIND * /SOURCE=DKA400:[*.KIT]

$ @SYS$UPDATE:VMSINSTAL
* Where will the distribution volumes be mounted: DKB400:[LP.KIT]

4. To install layered products that require the POLYCENTER Software Installation utility (indicated in the directories by file names with file types of .PCSI or .PCSI$DESCRIPTION), use the PRODUCT INSTALL command to specify the CD–ROM device name and directory. The following is an example of the PRODUCT INSTALL command:

$ PRODUCT INSTALL name /SOURCE=DKB400:[name.KIT]

8.12 Installing OpenVMS Debugger Clients on a PC

The OpenVMS Debugger Version 7.3–1 includes a client/server interface. The debug server runs on the OpenVMS operating system; there are debug clients that run on OpenVMS, Microsoft Windows 95, and Microsoft Windows NT. There is no separate installation procedure for the components that run on the OpenVMS operating system. They are installed when you install the operating system. This section describes the procedure for installing debug clients on a PC.

The following table shows which client kit to use for each PC configuration:

CPU	Operating System	Client Kit
Alpha	Windows NT	40COMAXP.EXE
Intel	Windows NT	40COMUPD.EXE
Alpha	Windows NT	DEBUGALPHA011.EXE
Intel	Windows 95, 98, Me, NT, 2000, XP	DEBUGX86011.EXE

The client kits are self-extracting .EXE files. To make these clients available to PC users, copy these files from the distribution media to a suitable PATHWORKS share, FTP server, or other device available to the PC. (Refer to the Guide to OpenVMS Alpha Version 7.3–1 CD–ROMs for the directory where these kits ship on the media.)

Once the appropriate executable file has been transferred to the PC, you can run the file to install the debug client on the PC. The InstallShield installation procedure guides you through the installation.

By default, the debug client is installed in the \Programs\OpenVMS Debugger directory. You can also click on the Browse button to select an alternate directory.

You can choose one of the following installation options:

Install Option	Details
Typical	Debug Client and theOpenVMS Debugger Manual in HTML format
Compact	Debug Client only
Custom	Choice of Debug Client and/or the OpenVMS Debugger Manual in HTML format

The Typical installation option creates an OpenVMS Debugger program folder that contains shortcuts to the following items:

• Debug client

• Debug client Help file

• The OpenVMS Debugger Manual in HTML format

• A Readme file

• An Uninstall procedure

For information about using the OpenVMS Debugger, see the OpenVMS Debugger Manual.

8.13 Backing Up the Customized System Disk

After you have upgraded and customized the OpenVMS Alpha operating system to your satisfaction and installed layered products, protect your work by making a backup copy of the system disk.

To back up the system disk:

1. Shut down the system (described in Appendix A ).

2. Boot the operating system CD–ROM (locally or from the InfoServer).

3. Use the menu system to enter the DCL environment (option 7).

4. Mount the system disk and the target device on which you will make the backup copy.

5. Enter backup commands to back up the system disk to the target device.

6. Log out from the DCL environment.

7. Shut down the system by selecting option 8 from the menu.

8. Boot from the system disk.

8.14 Rebooting Cluster Members

If you are performing a rolling upgrade in an OpenVMS Cluster environment and have completed all the postupgrade tasks required for your upgraded system disk, reboot each system that boots from that system disk.

For more information about booting your system, see Appendix A.

8.15 Running AUTOGEN

Although AUTOGEN runs automatically at the end of the upgrade procedure, Compaq recommends that you run AUTOGEN periodically after you perform an upgrade.

After 24 hours of operation, run AUTOGEN in FEEDBACK mode and reboot the system. Run AUTOGEN in this way again two workdays later. (For information about the importance of having a current AGEN$FEEDBACK.DAT file, see Section 5.5.)

AUTOGEN sets the values of system parameters and the sizes of the page and swap files according to the system’s work load. Compaq recommends that you run AUTOGEN from SAVPARAMS through TESTFILES on a weekly basis and examine AGEN$PARAMS.REPORT to determine the need for additional changes.

Hardcoded values in MODPARAMS.DAT should not hinder AUTOGEN’s ability to calculate feedback parameters. AUTOGEN generally does not reduce the value of parameters that allocate resources; it considers current parameter values to be minimum values, which means you do not have to add MIN_* symbols to MODPARAMS.DAT. AUTOGEN does increase parameter values according to its calculations unless you have specified explicit or maximum values (by adding MAX_* symbols) in MODPARAMS.DAT.

For more information about the MODPARAMS.DAT file and about using AUTOGEN in general, see the OpenVMS System Manager’s Manual.

8.16 Tuning BAP System Parameters

OpenVMS Alpha Version 7.1 and later contains system parameters that control the operation of bus-addressable pool (BAP).

The following table lists the system parameters that control BAP operation along with their default values:

System Parameter	Default Value
NPAG_BAP_MIN	0
NPAG_BAP_MAX	0
NPAG_BAP_MIN_PA	0
NPAG_BAP_MAX_PA	-1

1. Reset the BAP parameters to the default values.

2. Reboot the system.

3. Allow the installation procedure to run AUTOGEN, or manually run AUTOGEN yourself.

A typical AUTOGEN with FEEDBACK command to set these parameters follows:

$ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK

$Q:\adept8\entities\note.eps$ Note

These parameters are critical. Compaq recommends that you run AUTOGEN as described to ensure that they are set correctly.

If you prefer not to use this command because you want to adjust only the BAP parameters settings, use the following procedure:

1. Boot the system using the default BAP parameter values.

2. Manually run SYS$SYSTEM:AGEN$FEEDBACK.EXE:

$ @SYS$SYSTEM:AGEN$FEEDBACK.EXE

3. Search SYS$SYSTEM:AGEN$FEEDBACK.DAT for the BAP_* system parameter values:

$ SEARCH SYS$SYSTEM:AGEN$FEEDBACK.DAT "BAP_"

4. Run SYSGEN to set the following system parameters with the BAP values you obtained in Step 3:

AGEN$FEEDBACK Data	System Parameter	Units
BAP_MIN	NPAG_BAP_MIN	bytes
BAP_MAX	NPAG_BAP_MAX	bytes
BAP_MIN_PA	NPAG_BAP_MIN_PA	Mbyte^{1 (SEE NOTE)}
BAP_MAX_PA	NPAG_BAP_MAX_PA	Mbytes¹

$Q:\adept8\entities\note.eps$ Note

If you manually set parameters NPAG_BAP_MIN_PA and NPAG_BAP_MAX_PA, be sure to specify the value for each parameter in the correct units (bytes or megabytes) for your operating system version.

8.17 Postupgrade Checklist

Use the following checklist to make sure you have performed all the necessary tasks:

[ ] In a volume shadowing environment, reform the shadow set.

[ ] Register new licenses.

[ ] Examine AUTOGEN output stored in the file AGEN$PARAMS.REPORT.

[ ] Examine MODPARAMS.DAT.

[ ] Examine the command procedure templates supplied with the OpenVMS Alpha Version 7.3–1 operating system.

[ ] Initialize CDSA.

[ ] Run the User Environment Test Package (UETP) to test the system (described in the OpenVMS System Manager’s Manual).

[ ] Expand the system libraries using LIBDECOMP.COM.

[ ] Add and remove files.

[ ] Prepare your OpenVMS Alpha system and your PC to run OpenVMS Management Station by following the procedures described in Appendix D.

[ ] Install layered products, including DECwindows (if necessary).

[ ] Back up the customized system disk.

[ ] Reboot each system that boots from the upgraded system disk (for a rolling upgrade in an OpenVMS Cluster environment).

[ ] Run AUTOGEN.

A Halt, Boot, and Shutdown Procedures

This appendix contains the following information:

• Booting operations, including the following:

– Booting the operating system CD–ROM, locally and from an InfoServer system

– Booting manually from the system disk

– Performing a conversational boot

– Booting with minimum startup

– Booting with the XDelta utility (XDELTA)

– Booting from a different directory

– Booting with a PMAZB or PMAZC TURBOchannel adapter

– Booting over the network with an alternate TURBOchannel adapter

– Booting in an emergency

• Set, Show, and Writeboot operations, including the following:

– Setting the system for automatic booting

– Setting and showing boot devices

– Setting boot parameters

– Using the Writeboot utility

• Halt and shutdown operations

• Troubleshooting procedures

A.1 Booting Operations

The following sections describe different methods of booting your system.

A.1.1 Booting the Operating System CD–ROM

If you need to boot the OpenVMS Alpha operating system CD–ROM, either to perform an installation or upgrade or to perform related operations such as mounting or backing up the system disk, follow the steps in the following sections, depending on whether you are booting locally or from the InfoServer.

A.1.1.1 Booting from the Local Drive

Boot from the local drive as follows:

1. Insert the operating system CD–ROM into the local CD–ROM drive.

2. At the console prompt (>>>), enter the SHOW DEVICE command so you can identify the name of the CD–ROM drive (for example, DKA400:)

3. Enter the boot command in the following format:

BOOT -FLAGS 0,0 source-drive

Substitute the device name of the CD–ROM drive (as listed in the SHOW DEVICE display) for source-drive.

For example, if the SHOW DEVICE display lists the device name of your CD–ROM drive as DKA400, enter the following command and press the Return key:

>>> BOOT -FLAGS 0,0 DKA400

After you boot, the system displays a menu from which you can choose options to perform the following tasks:

• Install or upgrade the operating system using the POLYCENTER Software Installation utility.

• Enter a DCL environment from which you can perform preinstallation or maintenance tasks such as mounting or showing devices and backing up or restoring files on the system disk.

• Shut down the system.

A.1.1.2 Booting from the InfoServer

To boot the operating system CD–ROM using the InfoServer, do the following:

1. At the console prompt, enter the following command:

>>> B -FLAGS 0,0 -FILE APB_1073
lan-device-name

Note the following conventions:

• The APB file name is the unique file name that was assigned to the APB.EXE file when it was copied from the operating system CD–ROM to the Infoserver. This file is the name of the APB program used for the initial system load (ISL) boot program.

• lan-device-name is the name of the local area network (LAN) device identified with your computer. For information about the LAN devices your system supports, refer to the following table. For additional information, see the hardware manuals that you received with your Alpha computer and the OpenVMS software product description (SPD).

Alpha Computer	Ethernet Device	FDDI Device
ALPHAbook 1	EOA0	—
AlphaServer 400 series	EWA0	FWA0
AlphaServer 1000 series	ERA0, EWA0	FRA0
AlphaServer 1000A series	EWA0	FWA0
AlphaServer 1200 series	EWA0	FWA0
AlphaServer 2000 series	ERA0, EWA0	FRA0
AlphaServer 2100, 2100A series	ERA0, EWA0	FRA0
AlphaServer 4100 series	EWA0	FWA0
AlphaServer 8200 series	EXA0, EWA0	FXA0
AlphaServer 8400 series	EXA0, EWA0	FXA0
AlphaStation 200 series	EWA0	FWA0
AlphaStation 400 series	EWA0	FWA0
AlphaStation 500 series	EWA0	FWA0
AlphaStation 600 series	ERA0, EWA0	FWA0
DEC 2000 series	ERA0	—
DEC 3000 series	ESA0	"n/ESA0"
DEC 4000 series	EZA0	—
DEC 7000 series	EXA0	FXA0
DEC 10000 series	EXA0	FXA0
Digital Personal Workstation (DPWS) series	EWA0	FWA0

$Q:\adept8\entities\note.eps$ Note

If you are using a DEC 3000 or 4000 series system, note the following:

• On DEC 3000 series systems, you can boot through the InfoServer with an Ethernet PMAD device or FDDI DEFTA device by specifying the device name as “n/ESA0”. The value for n is the TURBOchannel slot number, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. For more information, see Section A.1.8.

• On DEC 4000 series, you must specify the ISL file name in uppercase (for example, APB_1073).

2. The InfoServer ISL program then displays the following menu:

   
Network Initial System Load Function
Version 1.2


  FUNCTION         FUNCTION
    ID
    1     -        Display Menu
    2     -        Help
    3     -        Choose Service
    4     -        Select Options
    5     -        Stop

Enter a function ID value:

3. Respond to the prompts as follows, pressing the Return key after each entry:

a. Enter 3 for the function ID.

b. Enter 2 for the option ID.

c. Enter the service name (ALPHA0731).

A sample display follows:

Enter a function ID value: 3[Return]

OPTION          OPTION
   ID
   1     -       Find Services
   2     -       Enter known Service Name

Enter an Option ID value: 2[Return]
Enter a Known Service Name: ALPHA0731[Return]

After you boot, the system displays a menu from which you can choose options to perform the following tasks:

• Install or upgrade the operating system using the POLYCENTER Software Installation utility.

• Enter a DCL environment from which you can perform preinstallation or maintenance tasks such as mounting or showing devices and backing up or restoring files on the system disk.

• Shut down the system.

A.1.2 Booting Manually from the System Disk

Boot the system disk manually as follows:

IF ...	THEN ...
the OpenVMS Alpha operating system is running,	go to step 1.
the OpenVMS Alpha operating system is not running,	go to step 4.

1. Log in to the SYSTEM account.

2. Enter the following command and press the Return key:

$ @SYS$SYSTEM:SHUTDOWN

3. Answer the questions displayed by the system. When the procedure asks if an automatic reboot should be performed, press the Return key for NO. When the procedure is finished, it displays the following message:

SYSTEM SHUTDOWN COMPLETE

4. Halt the system by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.)

5. Enter the BOOT command in the following format:

BOOT device-name

Substitute the device name of the system disk for device-name. For example, to boot from a drive with a device name of DKA400, enter the following command and press the Return key:

>>> BOOT DKA400

To boot from the network, enter the following command and press the Return key:

>>> BOOT ESA0

A.1.3 Performing a Conversational Boot

A conversational boot is most commonly used in research and development environments and during software upgrades. Perform a conversational boot to stop the boot process before it completes. The boot process stops after it loads SYS$SYSTEM:SYSBOOT.EXE and displays the SYSBOOT> prompt. At the SYSBOOT> prompt, you can enter specific OpenVMS System Generation utility (SYSGEN) commands to do the following:

• Examine system parameter values

• Change system parameter values

• Specify another parameter file

• Specify another system startup command procedure

• Select the default system parameter file if you modified system parameters to values that render the system unbootable

• Specify a minimum startup

There are several ways to perform a conversational boot. The following procedure is the most direct:

IF ...	THEN ...
the OpenVMS Alpha operating system is running,	go to step 1.
the OpenVMS Alpha operating system is not running,	go to step 4.

1. Log in to the SYSTEM account.

2. Enter the following command and press the Return key:

$ @SYS$SYSTEM:SHUTDOWN

SYSTEM SHUTDOWN COMPLETE

4. Halt the system by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.)

5. To begin the conversational boot, enter the BOOT command in the following format:

BOOT -FLAGS 0,1 [device-name]

Substitute the device name of the drive from which you want to boot for device-name. For example, if the system disk has a device name of DKA400, enter the following command and press the Return key:

>>> BOOT -FLAGS 0,1 DKA400

If you do not specify a device name, the system boots from the boot device assigned when you entered the SET BOOTDEF_DEV command.

6. At the SYSBOOT> prompt, you can enter any of the SYSGEN commands listed in Table A –4. For more information about these SYSGEN commands, see the OpenVMS System Management Utilities Reference Manual.

7. When you finish using the SYSGEN commands, enter the CONTINUE command to complete the boot process.

Table A–4 SYSGEN Commands Used in the SYSBOOT Procedure

Command	Description
CONTINUE	Resumes the boot procedure.
DISABLE CHECKS	Inhibits checking of parameter values specified with the SET command.
ENABLE CHECKS	Permits checking of parameter values specified with the SET command.
HELP	Displays a summary of the SYSBOOT commands on the terminal screen.
SET parameter-name	Establishes the value of a system parameter.
SET/STARTUP	Sets the name of the system startup command procedure.
SHOW [parameter]	Displays active, current, default, maximum, and minimum values for specific parameters. (Use qualifiers to display characteristics of parameters grouped by categories.)
USE [file-spec]	Specifies a parameter file to be used as a source of values. You must enter the entire file specification, including device and directory; you cannot specify a logical name.

For examples of using conversational booting, see Section A.1.4 and Section A.1.9.

A.1.4 Booting with Minimum Startup

In certain cases, you might want to boot your system without performing the full sequence of startup events. For example, if a startup event prevents you from logging in, you might want to boot the system without executing the startup so that you can log in and fix the problem. You can use the conversational boot to specify a minimum startup.

$Q:\adept8\entities\note.eps$ Note

Because this procedure bypasses specific startup operations, it does not autoconfigure the system’s peripheral devices.

Boot the system with minimum startup as follows:

1. Perform a conversational boot by entering the following command at the console prompt:

>>> BOOT -FLAGS 0,1 [device-name]

2. Enter the following command and press the Return key:

SYSBOOT> SET STARTUP_P1 "MIN"

3. Enter the following command to continue booting:

SYSBOOT> CONTINUE

4. After the system boots, log in and enter the following commands to invoke SYSMAN and clear the STARTUP_P1 parameter you set in step 2:

$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> PARAMETERS USE CURRENT
SYSMAN> PARAMETERS SET STARTUP_P1 ""
SYSMAN> PARAMETERS WRITE CURRENT

A.1.5 Booting with the XDelta Utility (XDELTA)

The XDelta utility (XDELTA) is a debugging tool that system programmers use. The procedure for booting all Alpha computers with XDELTA is the same.

The following table describes the valid values you can specify when booting with XDELTA:

Value	System Response
0	Normal, nonstop boot (default).
1	Begins a conversational boot and then displays the SYSBOOT prompt.
2	Includes XDELTA but does not take the initial breakpoint.
3	Displays the SYSBOOT prompt and includes XDELTA but does not take the initial breakpoint.
6	Includes XDELTA and takes the initial breakpoint.
7	Includes XDELTA, displays the SYSBOOT prompt, and takes the initial breakpoint at system initialization.

The following is an example of booting with XDELTA from the console prompt:

>>> BOOT -FLAGS 0,7

For more information about using XDELTA, see the OpenVMS Delta/XDelta Debugger Manual.

A.1.6 Booting from a Different Directory

By default, the OpenVMS Alpha operating system is installed in the system root directory [SYS0]. However, if you have created a cluster system disk, you can use the SYS$MANAGER:CLUSTER_CONFIG.COM procedure to add a copy of the operating system to a different root directory. (See the OpenVMS System Manager’s Manual for more information about using the SYS$MANAGER:CLUSTER_CONFIG.COM procedure.)

To boot from a different directory (for example, [SYS3]), enter the BOOT command as follows:

>>> BOOT -FLAGS 3,0 DKA200

A.1.7 Booting with a PMAZB or PMAZC TURBOchannel Adapter

PMAZB and PMAZC TURBOchannel adapters are adapters that are software-compatible with the integrated SCSI ports on DEC 3000 Alpha series systems.

The DEC 3000 Alpha series system consoles implement the SHOW CONFIGURATION console command, which displays information about the TURBOchannel options and the built-in adapters in the system. When a PMAZB or PMAZC adapter is installed in the TURBOchannel, the SHOW CONFIGURATION command displays the “PMAZB-AA” or “PMAZC-AA” string, the TURBOchannel slot number, and the device status.

The DEC 3000 Alpha series consoles also implement the SHOW DEVICE command, which displays information about the devices in the system. Because the integrated SCSI adapter is built into every DEC 3000 Alpha series system, the SHOW DEVICE console command can display the SCSI devices connected to the integrated SCSI ports. However, the SHOW DEVICE console command cannot display the SCSI devices connected to the PMAZB or PMAZC SCSI ports.

To make the console display the devices connected to the PMAZB or PMAZC SCSI ports, enter the following command at the console prompt, wherex is the TURBOchannel slot number in which the PMAZB or PMAZC adapter is installed:

>>> TEST TCx CNFG

This command displays the devices that are connected to each SCSI port of the PMAZB or PMAZC adapter. The device controller letters are either A or B, based upon the PMAZB or PMAZC ports to which the devices are connected. Do not confuse these devices with any DKAxxx or DKBxxx devices displayed by the SHOW DEVICE command, which shows SCSI devices on the integrated SCSI ports only.

To boot from a device connected to a PMAZB or PMAZC adapter, enter the boot command as follows:

>>> BOOT "x/dkyzzz"

The following conventions are used:

• x is the TURBOchannel slot number in which the PMAZB or PMAZC adapter is installed.

• dk is the device code of the boot device.

• y is either A or B, depending on the SCSI port of the PMAZB or PMAZC adapter that contains the boot device.

• zzz is the SCSI unit number of the boot device.

The OpenVMS Alpha operating system does not distinguish between the PMAZB or PMAZC adapter and the integrated SCSI adapter. The operating system views them as identical adapters. Because the operating system searches for I/O adapters in backplane slot number order, device controller letters are assigned that correspond to the backplane order of the TURBOchannel options, followed by the integrated adapters. This is different from console SCSI device naming, which always designates SCSI devices on the integrated SCSI ports as either "A" or "B" port devices.

Example

On a DEC 3000 Model 500 Alpha system with no TURBOchannel options installed, the OpenVMS Alpha operating system names the integrated SCSI ports PKA0 and PKB0, and the devices connected to the ports inherit the controller letter from the port controller letter (A or B). However, if a PMAZB or PMAZC adapter is installed in the TURBOchannel, the operating system names the PMAZB or PMAZC SCSI ports PKA0 and PKB0 and names the integrated SCSI ports PKC0 and PKD0. The devices connected to the ports inherit the controller letter from the port controller letter (A, B, C, or D).

A.1.8 Booting over the Network with an Alternate TURBOchannel Adapter

You can use an alternate TURBOchannel adapter to boot a DEC 3000 series Alpha computer (with the TURBOchannel option) over the network in an InfoServer or OpenVMS Cluster environment. Examples of alternate TURBOchannel adapters are the PMAD (which connects to the Ethernet) and the DEFTA (which connects to the FDDI).

To boot from a TURBOchannel device connected to one of these alternate adapters, enter the boot command as follows:

>>> BOOT "n/ESA0"

The value forn is the TURBOchannel slot number for the device, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. In the following example, the TURBOchannel slot number (listed under the “TCINFO” column) is 0:

>>> SHOW CONFIG

DEC 3000 - M300
Digital Equipment Corporation
     VPP PAL X5.56-80800101/OSF PAL X1.34-80800201 - Built on 18-DEC-1996 11:376

               TCINFO     DEVNAM     DEVSTAT
               ------     --------   --------
                 CPU      OK KN16-AA -V3.2-S6CD-I151-sV2.0-DECchip 21064 P3.0-150
                ASIC      OK
                 MEM      OK
                 MEM      OK
6
                 CXT      OK
5
                 NVR      OK
                 SCC      OK
                  NI      OK
                ISDN      OK
4
                SCSI      OK
0-PMAD-AA       TC0

A.1.9 Booting in an Emergency

If a system problem prevents your system from booting, you might need to perform an emergency boot operation. Table A –6 summarizes these emergency boot operations, and the sections that follow describe each boot operation in more detail.

Table A–6 Emergency Boot Procedures

Operation	When to Use
Booting with default system parameters	When parameter values in the parameter file have been modified so that the system is unbootable
Booting without startup and login procedures	If an error in the startup or login procedures prevents you from logging in
Booting without the user authorization file	If you have forgotten the password and cannot log in to a privileged account

A.1.9.1 Booting with Default System Parameters

If the current values stored in the parameter file have been incorrectly modified, these incorrect values might cause the system to become unbootable. With a conversational boot operation, you can reset the active values for all system parameters to the default value. (In most cases, Compaq recommends that you use AUTOGEN to modify system parameters. In certain cases, however, you can use a conversational boot to modify a parameter value temporarily. To change a parameter value permanently, you must edit MODPARAMS.DAT and run AUTOGEN. For instructions, see the OpenVMS System Manager’s Manual.) The default values allow you to boot the system temporarily so you can correct the problem.

How to Perform This Task

1. Perform a conversational boot by entering the following command at the console prompt:

>>> BOOT -FLAGS 0,1 [device-name]

2. At the SYSBOOT> prompt, enter the following command:

SYSBOOT> USE DEFAULT

This command specifies that default values should be used for all parameters.

3. Enter the following command to continue booting:

SYSBOOT> CONTINUE

4. When the system finishes booting, determine which changed parameter caused the problem and reset the parameter value. If you specified the value for the parameter in the AUTOGEN parameter file MODPARAMS.DAT, fix the value in that file and run AUTOGEN. For more information, see the OpenVMS System Manager’s Manual.

5. Shut down and reboot the system.

Example

SYSBOOT> USE DEFAULT
SYSBOOT> CONTINUE
Username: SYSTEM
Password:
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> PARAMETERS USE CURRENT
SYSMAN> PARAMETERS SET NPAGEDYN 2999808
SYSMAN> PARAMETERS WRITE CURRENT
SYSMAN> EXIT
$ EDIT SYS$SYSTEM:MODPARAMS.DAT

.
.
.

[Insert the following line in MODPARAMS.DAT:]
MIN_NPAGEDYN = 2999808

.
.
.

$ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT

A.1.9.2 Booting Without Startup and Login Procedures

If the system does not complete the startup procedures or does not allow you to log in, bypass the startup and login procedures. The startup and login procedures provided by Compaq should always work. However, if you introduce an error when modifying the startup or login procedures, it is possible to accidentally lock yourself out of the system.

How to Perform This Task

1. Perform a conversational boot by entering the following command at the console prompt:

>>> BOOT -FLAGS 0,1 [device-name]

2. Enter the following command at the SYSBOOT> prompt:

SYSBOOT> SET/STARTUP OPA0:

3. Enter the following command to continue booting:

SYSBOOT> CONTINUE

4. When the system is booted, the operator console displays the DCL command prompt ($). You are logged in.

5. Enter the following DCL command:

$ SET NOON

This command directs the operating system to ignore any errors that might occur. If you do not enter this command and you invoke an error, the system will log you out.

6. Correct the error condition that caused the login failure. (That is, make the necessary repairs to the startup or login procedures, or to the SYSUAF.DAT file.)

Invoke a text editor to correct the startup or login file. Note that some system consoles might not supply a screen-mode editor. You can also copy a corrected file and delete the incorrect version by using the RENAME and DELETE commands.

7. Invoke SYSMAN and enter the following commands to reset the startup procedure:

$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> PARAMETERS USE CURRENT
SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:STARTUP.COM
SYSMAN> PARAMETERS WRITE CURRENT
SYSMAN> EXIT
$

8. Perform a normal startup by entering the following command:

$ @SYS$SYSTEM:STARTUP

Example

SYSBOOT> SET/STARTUP OPA0:
SYSBOOT> CONTINUE
$ SET NOON
$ SET DEFAULT SYS$SYSROOT:[SYSEXE]
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> PARAMETERS USE CURRENT
SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:STARTUP.COM
SYSMAN> PARAMETERS WRITE CURRENT
SYSMAN> EXIT
$ @SYS$SYSTEM:STARTUP

A.1.9.3 Booting Without the User Authorization File

Ordinarily, the startup and login procedures provided by Compaq always work; however, certain user interventions can cause them to fail. A very simple way to lock yourself out of the system is to set passwords to login accounts and forget them. In such an emergency, you can use the alternate user authorization file rather than the standard user authorization file.

$Q:\adept8\entities\note.eps$ Note

You can use this method only to log in to the system from the console terminal; you cannot use other terminal lines.

Setting the system parameter UAFALTERNATE defines the logical name SYSUAF to refer to the file SYS$SYSTEM:SYSUAFALT.DAT. If this file is found during a normal login, the system uses it to validate the account and prompts you for the user name and password.

If it cannot find this file, the system assumes that the UAF is corrupt and accepts any user name and any two passwords to log you in to the system from the system console. Logins are prohibited from all other terminal lines.

When you perform this procedure, the system assigns the following values to your user account:

Field	Value
Name	User name
UIC	[001,004]
Command interpreter	DCL
Login flags	None
Priority	Value of the system parameter, DEFPRI
Resources	Values of the PQL system parameters
Privileges	All

The process name is usually the name of the device on which you logged in (for example, _OPA0:).

How to Perform This Task

1. Perform a conversational boot by entering the following command at the console prompt:

>>> BOOT -FLAGS 0,1 [device-name]

2. At the SYSBOOT> prompt, enter the following command:

SYSBOOT> SET UAFALTERNATE 1

3. If your system is running DECwindows software, you must also disable the windowing system by entering the following command:

SYSBOOT> SET WINDOW_SYSTEM 0

4. Enter the CONTINUE command to continue booting:

SYSBOOT> CONTINUE

5. When the startup procedure completes, log in on the console terminal by entering any user name and any two passwords in response to the Username: and Password: prompts.

6. Enter the following command to use the default UAF:

$ DEFINE/SYSTEM/EXECUTIVE_MODE SYSUAF SYS$SYSTEM:SYSUAF.DAT

7. Use the Authorize utility to fix the problem that caused you to be locked out of the system (for example, a forgotten password). Enter HELP MODIFY at the UAF> prompt for information about modifying passwords. For more details, see the OpenVMS System Management Utilities Reference Manual.

8. Enter the following commands to invoke SYSMAN and clear the UAFALTERNATE system parameter you set in step 2:

$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> PARAMETERS USE CURRENT
SYSMAN> PARAMETERS SET UAFALTERNATE 0

In most cases, Compaq recommends that you use AUTOGEN to modify system parameters. However, because this parameter is only being changed temporarily, you can use SYSMAN to change it back.

9. If you disabled the windowing system in step 3, reenable it by entering the following command:

SYSMAN> PARAMETERS SET WINDOW_SYSTEM 1

10. Enter the following command to save the changed system parameter values:

SYSMAN> PARAMETERS WRITE CURRENT

11. Shut down and reboot the system.

Example

SYSBOOT> SET UAFALTERNATE 1
SYSBOOT> SET WINDOW_SYSTEM 0
SYSBOOT> CONTINUE
Username: [Return]
Password: [Return]
Password: [Return]
$ DEFINE/SYSTEM/EXECUTIVE_MODE SYSUAF SYS$SYSTEM:SYSUAF.DAT
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
AUTHORIZE> MODIFY SYSTEM/PASSWORD=FGLFTUTU
AUTHORIZE> EXIT
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> PARAMETERS USE CURRENT
SYSMAN> PARAMETERS SET WINDOW_SYSTEM 1
SYSMAN> PARAMETERS SET UAFALTERNATE 0
SYSMAN> PARAMETERS WRITE CURRENT
SYSMAN> EXIT
$ @SYS$SYSTEM:SHUTDOWN

A.2 Set, Show, and Writeboot Operations

The following sections describe how to perform SET, SHOW, and Writeboot operations.

A.2.1 Setting the System for Automatic Booting

Alpha computers can boot automatically from a designated boot device. When you installed the OpenVMS Alpha operating system, you designated the system disk as the default boot device. Section A.2.2 describes how to change the default boot device.

Alpha computers can boot automatically from the default boot device under the following conditions:

• When you first turn on system power

• When system power comes on after a power failure

• After you shut down the system (if you enter Y when the shutdown procedure asks if an automatic reboot should be performed)

• After a bugcheck

• If the system halts under program control

Set the system to boot automatically by performing one of the following steps:

IF ...	THEN ...
the OpenVMS Alpha operating system is running,	go to step 1.
the OpenVMS Alpha operating system is not running,	go to step 4.

1. Log in to the SYSTEM account.

2. Enter the following command and press the Return key:

$ @SYS$SYSTEM:SHUTDOWN

SYSTEM SHUTDOWN COMPLETE

4. Halt the system by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.)

5. If you have an SMP system with multiple CPUs, enter the following command at the console prompt (>>>) to stop the other CPUs:

>>> INITIALIZE

6. Enter the following command to show whether the system has been set to boot automatically:

>>> SHOW AUTO_ACTION

The system displays one of the following:

• Restart

• Boot

• Halt

7. Enter the SET AUTO_ACTION command if you want to change the automatic booting behavior. For example, the following command sets the system to reboot automatically:

>>> SET AUTO_ACTION RESTART

8. After you set this variable, Compaq recommends that you set the boot device and operating system flags as well, using the SET BOOTDEF_DEV and SET BOOT_OSFLAGS commands described in the following sections.

A.2.2 Setting and Showing Boot Devices

Use the SET BOOTDEF_DEV command to tell the system which drive you want to boot from (that drive becomes the default boot device). Use the SHOW BOOTDEF_DEV command to display the current default boot device.

Note that when you set this variable, Compaq recommends that you set the operating system boot parameters as well, using the SET BOOT_OSFLAGS command.

At the console prompt (>>>), enter the SET BOOTDEF_DEV command in the following format:

SET BOOTDEF_DEV device-name

Substitute the device name of the system disk for device-name. For example, to boot from a drive with a device name of DKA400 on a DEC 3000 Alpha series computer, enter the following command and press the Return key:

>>> SET BOOTDEF_DEV DKA400

The next time you boot the system, you can enter the BOOT command without specifying a device name (because DKA400 is now the default boot device). For example:

>>> BOOT

$Q:\adept8\entities\note.eps$ Note

If you have not used the SET BOOTDEF_DEV command to set the drive to boot from and you enter the BOOT command without specifying a device name, the system displays an error message.

Use the SHOW BOOTDEF_DEV command to find out what drive was specified in the last SET BOOT command. For example:

>>> SHOW BOOTDEF_DEV

To cancel the drive specified in a previous SET BOOTDEF_DEV command, enter the following command and press the Return key:

>>> SET BOOTDEF_DEV

$Q:\adept8\entities\note.eps$ Note

This command is not valid on DEC 3000 Alpha series systems.

A.2.3 Setting Boot Parameters

By default, when you boot the operating system, the flags parameter is set to 0. If you want to define parameters to enable specific functions during the booting process, use the SET BOOT_OSFLAGS console command.

The following is a list of values you can specify with the SET BOOT_OSFLAGS command:

Hexadecimal Value	System Response
1	Allows a conversational boot (the system displays the SYSBOOT> prompt).
2	Maps XDELTA to a running system.
4	Stops the boot procedure at the initial system breakpoint.
8	Performs a diagnostic bootstrap.
10	Stops the boot procedure at the bootstrap breakpoints.
20	Omits header from secondary bootstrap image.
80	Prompts for the name of the secondary bootstrap file.
100	Halts the system before the secondary bootstrap.
2000	Marks corrected read data error pages as bad.
10000	Displays extensive, detailed debug messages during the boot process.
20000	Displays selected user-oriented messages during the boot process.

The following examples show how to use the SET BOOT_OSFLAGS command:

• The following command specifies the root directory as 0 and the parameter as 1, which sets the system to perform a conversational boot from the [SYS0] directory when you enter the BOOT command:

>>> SET BOOT_OSFLAGS 0,1

• The following command specifies the root directory as 1 and the parameter as 0, which sets the system (for example, the second host in a two-system DSSI OpenVMS Cluster configuration) to boot from the [SYS1] directory (instead of [SYS0]) when you enter the BOOT command:

>>> SET BOOT_OSFLAGS 1,0

• The following example specifies the root directory as 0 and the parameters as 1, 2, 4, and 20000 (for a total hexadecimal value of 20007). As a result, when you enter the BOOT command, the system will perform a conversational boot from the [SYS0] directory with XDELTA, stop at the initial system breakpoint, and display relevant user messages.

>>> SET BOOT_OSFLAGS 0,20007

To display the parameters you have just set, use the SHOW BOOT_OSFLAGS command. For example:

>>> SHOW BOOT_OSFLAGS
BOOT_OSFLAGS = 0,20007

A.2.4 Using the Writeboot Utility

The Writeboot utility (WRITEBOOT.EXE) is copied to your system disk during the installation procedure. It allows you to create a bootable OpenVMS Alpha system disk from one that was originally created by one of the following methods:

• A nonimage backup of an Alpha system disk (possibly corrupting the boot block)

• A nonimage restore of an Alpha system disk from an image save set

The Writeboot utility also allows you to rewrite the boot block of an OpenVMS Alpha system disk to point to a new version of the OpenVMS Alpha primary bootstrap file (APB.EXE) that you have previously copied to the disk. (Note that the file must be contiguous.)

To invoke the Writeboot utility, enter the following command:

$ RUN SYS$SYSTEM:WRITEBOOT

The utility prompts you as follows:

Update VAX portion of boot block (default is Y):
Update Alpha portion of boot block (default is Y):

Answer N (No) to the VAX prompt. If you answer Y (Yes) to update the Alpha boot block, the utility prompts you for the Alpha boot file:

Enter Alpha boot file:

Specify device-name:[VMS$COMMON.SYSEXE]APB.EXE in response to this prompt, wheredevice-name indicates the device on which the system disk is mounted.

A.3 Halt and Shutdown Operations

The following sections describe halt and shutdown operations for Alpha computers.

A.3.1 Halting the System

During installation, upgrade, and related system operations, you might need to halt your system. The methods for halting Alpha computers differ slightly with certain models, as described in the next section.

The following table summarizes the ways you can halt specific Alpha computers:

Alpha Computer	How to Halt
AlphaServer 300, 800, 1000, 1200, 2000, 2100 series	Do one of the following: • Press the Halt button. • Press Ctrl/P.
AlphaServer 8200, 8400 series	Press Ctrl/P.
AlphaStation 200, 400, 500, 600 series	Do one of the following: • Press the Halt button (if the graphics monitor is serving as the console). • Press Ctrl/P (if you are using the alternate console and port).
DEC 2000, 3000 series	Do one of the following: • Press the Halt button (if the graphics monitor is serving as the console). • Press Ctrl/P (if you are using the alternate console and port).
DEC 4000 series	Do one of the following: • Press the Halt button. • Press the Break key on the console (the default setting). • Press Ctrl/P, but only after using the console command SET TTA0_HALTSn to enable this key combination, where n can be 6 (enables the Break key and Ctrl/P) or 2 (enables Ctrl/P but disables the Break key).
DEC 7000, 10000 series	Press Ctrl/P.

A.3.2 Shutting Down the System

Before you shut down the operating system, decide if you want it to reboot automatically or if you want to enter console-mode commands after the shutdown completes.

You can perform the following three types of shutdown operations:

• An orderly shutdown with SYS$SYSTEM:SHUTDOWN.COM (see Section A.3.2.1 )

• An emergency shutdown with OPCCRASH.EXE (see Section A.3.2.2 )

• An emergency shutdown with crash commands (see Section A.3.2.3 )

If you want the system to reboot automatically after the shutdown, see Section A.2.1.

A.3.2.1 Orderly Shutdown

The SHUTDOWN.COM procedure shuts down the system while performing maintenance functions such as disabling future logins, stopping the batch and printer queues, dismounting volumes, and stopping user processes. To use the SHUTDOWN.COM command procedure, log in to the SYSTEM account, enter the following command, and press the Return key:

$ @SYS$SYSTEM:SHUTDOWN

For more information about the SHUTDOWN.COM command procedure, see the OpenVMS System Manager’s Manual.

A.3.2.2 Emergency Shutdown with OPCCRASH.EXE

If you cannot perform an orderly shutdown with the SHUTDOWN.COM procedure, run the OPCCRASH.EXE emergency shutdown program. To run the OPCCRASH.EXE program, log in to the SYSTEM account, enter the following command, and press the Return key:

$ RUN SYS$SYSTEM:OPCCRASH

For more information about the OPCCRASH program, see the OpenVMS System Manager’s Manual.

A.3.2.3 Emergency Shutdown with Crash Commands

Use crash commands only if the system is “hung” (stops responding to any commands) and you cannot log in to the SYSTEM account to use the SHUTDOWN.COM procedure or the OPCCRASH.EXE program.

$Q:\adept8\entities\note.eps$ Note

The method described here works on all Alpha computers. However, on certain systems, you can force your processor to fail (crash) by entering a specific console command. See the hardware manuals that came with your computer for that information.

To force your processor to fail, do the following:

1. Halt the system by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.)

2. To examine processor registers, enter the following commands and press the Return key:

>>> E -N F R0
>>> E PS

The system displays the contents of the registers. Write down these values if you want to save information about the state of the system.

3. Enter the following commands and press the Return key:

>>> D PC FFFFFFFF00000000
>>> D PS 1F00

By depositing these values, you cause the system to write a memory dump to the system dump file on the disk.

4. Enter the following command and press the Return key:

>>> CONTINUE

This causes the system to perform a bugcheck.

5. After the system reboots, log in to the SYSTEM account.

6. To examine the dump file, enter the following commands and press the Return key after each one:

$ ANALYZE/CRASH SYS$SYSTEM:SYSDUMP.DMP
SDA> SHOW CRASH

For more information about the System Dump Analyzer (SDA) utility, see the OpenVMS Alpha System Analysis Tools Manual.

A.4 Troubleshooting Procedures

The following sections describe procedures that you can follow if you encounter problems with your system.

A.4.1 If the System Does Not Boot

If the system does not boot because a hardware problem occurs, a question mark(?) usually precedes the error message displayed on the console terminal. An example of a hardware problem is a read error on a disk or tape cartridge drive.

A.4.1.1 For Hardware Problems

If you suspect a hardware problem, do the following:

1. Consult the hardware manual for your Alpha computer.

2. Contact a Compaq support representative.

A.4.1.2 For Software Problems

When the operating system is loaded into memory, a message similar to the following appears on the terminal screen:

SYSTEM   job terminated at 27-MAY-2002 15:05:03.17

If the system does not display this message, a software problem has probably occurred. Do the following:

1. Turn off the system. Turn it back on and try to reboot.

2. Perform a conversational boot using the default system parameters or try one of the emergency boot procedures.

3. If the system boots, run the AUTOGEN procedure. For more information about the AUTOGEN procedure, see the OpenVMS System Manager’s Manual.

A.4.2 Detecting and Responding to System Problems

If your system exhibits unexpected behavior, note the following:

• If the system displays a bugcheck message on the console terminal and shuts itself down, it means the system encountered a problem that made further operation impossible or dangerous. Reboot the system as explained in Section A.1.2, or let it reboot automatically as explained in Section A.2.1.

• If the system stops responding to your commands (that is, the system “hangs” ), there is a possible failure in a system software or hardware component or a possible power failure.

• If the system exhibits erratic behavior (it does not respond according to specifications), it indicates a possible failure in a system software or hardware component.

To determine if the failure is a system problem:

• Be sure that you did not press the F1 key (the Hold Screen key). The Hold Screen light goes on when you press either F1 or enter Ctrl/S.

• Enter Ctrl/T to check the status of your process. A status line should appear, indicating the name of the program that is executing and other information. If the status line does not appear, the program you are executing might be stalled or “hung.” (If you have disabled Ctrl/T by entering the command SET NOCONTROL=T or have set the terminal to NOBROADCAST mode by entering the command SET TERMINAL/NOBROADCAST, this procedure does not work.)

• Make sure the cable connecting the terminal or monitor to the system is secure.

If you determine that you have a system problem:

1. Force an exit from a stalled or “hung” program by entering Ctrl/Y. Note that when you enter Ctrl/Y, any work performed by the program and not saved on disk is lost.

2. If the system is still unresponsive, halt it by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.)

3. Note in detail the sequence of events that caused the problem and notify a Compaq support representative.

B Backing Up and Restoring the System Disk

This appendix describes how to perform backup and restore operations on the system disk. You perform these tasks by entering commands from a specialized backup environment. You access this environment through the menu that is displayed when you boot the OpenVMS Alpha operating system CD–ROM or through an alternate method that does not require the CD–ROM.

This specialized backup environment is required because it allows you to create an exact copy of the system disk. You cannot create an exact copy in a standard operating system environment because the OpenVMS Backup utility saves only what is on the disk at the moment the BACKUP command is executing, excluding portions of open files contained in memory or data about files not yet written back to the disk (cache).

For more information about backup operations, including procedures for backing up and restoring files and directories, see the OpenVMS System Manager’s Manual.

B.1 Reasons for Backing Up the System Disk

The primary reason why you should have a backup copy of the system disk is so you can fully restore your system in response to any hardware or software problem that affects the integrity of your original system disk or your ability to access it. For example, you would need to use the backup copy to restore your system under the following conditions:

• When a problem occurs during an OpenVMS Alpha upgrade or update, or during the installation of other software products. If you backed up the system disk before you attempted any of those procedures, you could restore the system disk and attempt the procedure again.

• When a system file that is accidentally deleted renders the system disk inoperable. If you backed up the system disk after you installed or upgraded the OpenVMS Alpha operating system and any other software products, you could restore the system disk.

• When the drive that holds the system disk malfunctions. If you have a backup copy of the system disk, you can restore it to a functioning disk and continue to use the system.

Another reason for backing up the system disk is to eliminate disk fragmentation, which occurs when files are stored noncontiguously on the disk. The BACKUP/IMAGE command creates a copy on which files are stored contiguously.

B.2 Suggested Procedures

Compaq recommends the following:

• The preferred method for performing system disk backup and restore operations is to boot the operating system CD–ROM, choose the DCL option from menu, and then enter the appropriate backup commands. The detailed procedures are described in Section B.4 and Section B.5.

However, if you do not have access to the compact disc or if you want to back up a shadowed system disk without disabling the shadow set, you can use a different procedure, described in Section B.6.

• Store the backup media in a safe place.

• If you have an OpenVMS Cluster environment with more than one system disk, be sure the volume label on each system disk and backup copies of system disks are unique. Use the SET VOLUME/LABEL command to change a volume label, if necessary.

B.3 OpenVMS Cluster Caution

If any nodes except the node used to run BACKUP are booted during the backup operations described in this appendix, your cluster will become partitioned, where nodes in the existing cluster divide into two or more independent clusters. This condition can cause data file corruption.

In addition, these backup environments do not restrict your use of DCL commands to the BACKUP command only, which further increases your risk of accidentally destroying or corrupting data on a disk. Therefore, to avoid jeopardizing the integrity of your data in any way, Compaq recommends that you shut down the entire OpenVMS Cluster system before you back up your system disk.

B.4 Backing Up the System Disk

The following sections describe how to back up the system disk.

B.4.1 Getting Started

Before you back up the system disk, do the following:

1. In an OpenVMS Cluster environment, dismount the system disk from all systems in the cluster that have the disk mounted as a data disk (rather than as the system disk).

2. Shut down all systems booted from that disk.

3. Boot the operating system CD–ROM locally or from the InfoServer (as described in Appendix A ).

4. Choose the DCL option (7) from the menu. For example:

 ****************************************************************

 You can install or upgrade the OpenVMS Alpha operating system
 or you can install or upgrade layered products that are included
 on the OpenVMS Alpha operating system CD-ROM.

 You can also execute DCL commands and procedures to perform
 "standalone" tasks, such as backing up the system disk.

 Please choose one of the following:

     1)  Upgrade, install or reconfigure OpenVMS Alpha Version 7.3-1
     2)  Display products and patches that this procedure can install
     3)  Install or upgrade layered products and patches
     4)  Show installed products
     5)  Reconfigure installed products
     6)  Remove installed products
     7)  Execute DCL commands and procedures
     8)  Shut down this system
        
 Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 7

5. At the triple dollar sign prompt ($$$), enter the SHOW DEVICES command.

6. Examine the list of devices so you can determine which device is the source drive (the system disk you want to back up) and which device is your target drive (the supported disk or tape device that will hold the backed up files).

B.4.2 Mounting Devices

When you have determined which devices will be the source drive and target drive, mount those devices (and any other output devices you plan to use) before you perform any backup operations. Enter the MOUNT commands in the following format:

$$$ MOUNT/OVERRIDE=IDENTIFICATION source-drive
$$$ MOUNT/FOREIGN target-drive

Note the following conventions:

• source-drive is the name of the drive holding the system disk

• target-drive is the name of the drive that will hold the backup files

B.4.3 Entering the BACKUP Command

When the system disk and output devices are mounted, back up the system disk by entering the BACKUP command in the following format:

$$$ BACKUP/IMAGE/VERIFY source-drive: target-drive:

Example 1

In this example the system disk and a target disk are mounted so the BACKUP command can create a backup disk. (You can use a backup disk as a system disk.)

$$$ MOUNT/OVERRIDE=IDENTIFICATION DKA200
$$$ MOUNT/FOREIGN DKA300
$$$ BACKUP/IMAGE/VERIFY DKA200: DKA300:

Example 2

In this example the system disk and a target tape device are mounted so the BACKUP command can create a backup tape.

$$$ MOUNT/OVERRIDE=IDENTIFICATION DKA200
$$$ MOUNT/FOREIGN MKA300
$$$ BACKUP/IMAGE/VERIFY DKA200: MKA300:APR_06_BACKUP.BCK/SAVE_SET

B.4.4 Changing the CLUSTER_SIZE Parameter

The BACKUP command creates a system disk that includes a set of volume parameters provided by Compaq, including a CLUSTER_SIZE (disk access scheme) that is appropriate for your system. (The CLUSTER_SIZE refers to the way files are stored on the disk, not to cluster environments.) You can change most volume parameters later with the SET VOLUME command.

However, to change the CLUSTER_SIZE, you must back up the system disk to a disk that has been previously initialized with the CLUSTER_SIZE that you want. For more information about initializing a disk and using the BACKUP command, see the OpenVMS System Manager’s Manual and the OpenVMS System Management Utilities Reference Manual, and see the description of the INITIALIZE and BACKUP commands in the OpenVMS DCL Dictionary.

B.4.5 Logout, Shutdown, and Reboot

After you complete the backup operation:

1. Enter the LOGOUT command to exit from the DCL environment and return to the menu.

2. Choose the shutdown option (8).

3. After the shutdown completes, boot from the system disk.

B.5 Restoring the System Disk

The following sections describe how to restore the system disk.

B.5.1 Getting Started

Before you can restore the system disk:

1. Shut down the system.

2. Boot the operating system CD–ROM locally or from the InfoServer (as described in Appendix A ).

3. Choose the DCL option (7) from the menu. For example:

You can install or upgrade the OpenVMS Alpha operating system
or you can install or upgrade layered products that are included
on the OpenVMS Alpha operating system CD-ROM.

You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.

Please choose one of the following:

    1)  Upgrade, install or reconfigure OpenVMS Alpha Version 7.3-1
    2)  Display products and patches that this procedure can install
    3)  Install or upgrade layered products and patches
    4)  Show installed products
    5)  Reconfigure installed products
    6)  Remove installed products
    7)  Execute DCL commands and procedures
    8)  Shut down this system
        
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 7

4. At the triple dollar sign prompt ($$$), enter the SHOW DEVICES command.

5. Examine the list of devices so you can determine which device is the source drive (the drive holding the backed up files you want to restore) and which device is your target drive (the disk on which you want the files restored).

B.5.2 Mounting Devices

When you have determined which devices will be the source drive and target drive, mount those devices (and any other output devices you plan to use) before you perform any restore operations. Enter the MOUNT commands in the following format:

$$$ MOUNT/OVERRIDE=IDENTIFICATION source-drive
$$$ MOUNT/FOREIGN target-drive

Note the following conventions:

• source-drive is the device holding the files you want to restore

(Note, however, that you must use the MOUNT/FOREIGN command if the source drive is a tape device.)

• target-drive is the destination

B.5.3 Entering the BACKUP Command

Enter the BACKUP command in the following format:

$$$ BACKUP/IMAGE/VERIFY source-drive: target-drive:

Example 1

In this example a backup disk and a target disk are mounted so the BACKUP command can restore the system disk from the backup disk:

$$$ MOUNT/OVERRIDE=IDENTIFICATION DKA300
$$$ MOUNT/FOREIGN DKA200
$$$ BACKUP/IMAGE/VERIFY DKA300: DKA200:

Example 2

In this example a backup tape and a target disk are mounted so the BACKUP command can restore the system disk from the backup tape:

$$$ MOUNT/FOREIGN MKA300
$$$ MOUNT/FOREIGN DKA200
$$$ BACKUP/IMAGE/VERIFY MKA300:APR_06_BACKUP.BCK/SAVE_SET DKA200:

B.5.4 Logout, Shutdown, and Reboot

After you complete the restore operation:

1. Enter the LOGOUT command to exit from the DCL environment and return to the menu.

2. Choose the shutdown option (8).

3. After the shutdown completes, boot from the system disk.

B.6 Alternate Backup and Restore Procedure

This section describes an alternate method of performing backup and restore operations on your system disk. With this method, you install the operating system (without options) on another disk and perform your backup and restore operations on the system disk from there. Use this method under the following conditions:

• If you do not have access to the operating system CD–ROM and its menu system

• If you want to back up a shadowed system disk without disabling the shadow set

$Q:\adept8\entities\note.eps$ Note

It is also possible to back up your running system disk by using the qualifier /IGNORE=INTERLOCK with the BACKUP command and ignoring warning messages. However, that method requires that all other use of the system be suspended, including disabling logins, stopping print and batch queues, and turning off networking software. In addition, you cannot use this method to restore files to the running system disk. Because of these limitations, Compaq recommends that if you must use an alternate method to back up or restore the system disk, you use the method described in this section.

B.6.1 Preparing an Alternate System Disk

Prepare an alternate system disk as follows:

1. Log in to a privileged account on your running OpenVMS Alpha system.

2. Using the SHOW DEVICE command, identify a data disk on which you can install the operating system, with no options. This will be your target disk during that installation. Note the following:

• You will need approximately 75,000 blocks to install the operating system with no options

• Existing data will remain on the disk

3. The target disk must be mounted privately to your process. (This prevents other users from accessing this disk during the installation and backup procedures.) Therefore, if the target disk was mounted with /SYSTEM, /CLUSTER, /GROUP, or /SHARE, dismount that disk and mount it without using those qualifiers or the /FOREIGN qualifier. For example:

$ MOUNT/OVERRIDE=IDENTIFICATION DKA200

4. Enter the following command to install the OpenVMS Alpha operating system, with no options, on the target disk:

$ @SYS$SYSTEM:AXPVMS$PCSI_INSTALL_MIN.COM [target-disk]

(The procedure will prompt you for a device name if you do not specify it on the command line.)

5. As the procedure completes the installation, the display is similar to the following:

DEC AXPVMS OPENVMS V7.3-1: OpenVMS and related products platform
 
    COPYRIGHT (c) 14-MAY-2002 -- All rights reserved
 
    Compaq Information Technologies Group, L.P.
 
Execution phase starting ...

The following product will be installed:
    DEC AXPVMS VMS V7.3-1

Portion Done: 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100%

The following product has been installed:
    DEC AXPVMS VMS V7.3-1
    .
    .
    .
    The installation of minimum OpenVMS Alpha is now complete.

    Use the following command to boot minimum OpenVMS:

        BOOT -FLAGS E,O device-name

    (Your system may require additional parameters to boot.)

$Q:\adept8\entities\note.eps$ Caution

If your system is a cluster member, Compaq recommends that you shut down the entire OpenVMS Cluster system before you back up your system disk. This will prevent you from creating a partitioned cluster and from jeopardizing the integrity of your data in any other way.

B.6.2 Using the Alternate System Disk

Use the alternate system disk (on which you installed the operating system with no options) to perform backup and restore operations as follows:

1. Shut down your system.

2. Boot the alternate system disk from the SYSE root. For example:

>>> BOOT -FLAGS E,0 DKA200

The system automatically logs you in to the SYSTEM account and then displays a triple dollar sign prompt ($$$).

$Q:\adept8\entities\note.eps$ Note

During the boot and login operations on this minimum version of the operating system, you can ignore license messages that are similar to the following:

%LICENSE-I-NOLICENSE, no license is active for this software product

3. If your system disk is shadowed, install and load a Volume Shadowing license on this data disk. You will then be able to back up the shadowed system disk from this data disk without disabling the shadow set.

$Q:\adept8\entities\note.eps$ Note

Compaq recommends that you do not install any other licenses, including OpenVMS licenses, on this alternate system. You will be able to use the system only from the console.

4. Mount the system disk and any output devices you plan to use during the backup or restore operations. See Section B.5.2 for more information.

5. Perform the necessary backup and restore operations by entering the appropriate BACKUP commands. See Section B.5.3 for more information.

6. Shut down the system.

7. Boot from your original system disk.

C License Management Supplement

This appendix contains information that supplements the license instructions in this manual and in the OpenVMS License Management Utility Manual.

After you install the OpenVMS Alpha operating system, you must register OpenVMS Alpha licenses, which let you use the OpenVMS Alpha operating system. You must also register the licenses for the OpenVMS Alpha layered products you have purchased, such as DECnet for OpenVMS. (Note that after an upgrade, however, you do not have to reregister licenses for the OpenVMS Alpha operating system or for the layered products.) To register a license, you need to obtain a Product Authorization Key (PAK). A PAK is a printed document provided by Compaq that contains the appropriate information to authorize access to software on an Alpha computer (or in an OpenVMS Cluster environment). You can obtain a PAK from a Compaq support representative in the same way that you obtain software.

C.1 Using the License Unit Requirement Table (LURT)

Many PAKs contain an alphabetic letter in the Availability or Activity fields. This letter refers to a column in the License Unit Requirement Table (LURT), which you can access online at the following URL:

http://www.compaq.com/products/software/info/refmat/swl_alpha.HTML

The second column (Operating System Units) in the LURT is also known as Column A. This column lists the number of license units required for each processor listed in the System Model column. The last column (Layered Product Units) in the LURT is also referred to as Column H. It indicates the number of OpenVMS Alpha layered products license units you need to run the system integrated products (SIPs) included with the operating system. For example, if your PAK specifies Availability = A, you would require 50 license units to load the license on a DEC 3000 Alpha Model 500 series computer, or 500 license units to load the license on a DEC 7000 Alpha Model 610 computer.

Note that some PAKs specify MOD_UNITS in the options field. The MOD_UNITS option allows the system manager to use the DCL command LICENSE MODIFY/UNITS to temporarily increase the size of the PAK. This permits a product to be used, in certain emergency situations, on a processor larger than the processor size specified in the license. Check your license terms and conditions before modifying license units. Reset the PAK size to its original size after the emergency situation is resolved.

C.2 License Management Facility (LMF) Notes

The following list addresses some common concerns and questions regarding the License Management Facility (LMF). For full explanations of these issues, see the OpenVMS License Management Utility Manual.

• If you do not have a valid OpenVMS Alpha license that is registered and activated, the system displays a warning message as part of system startup and restricts system use to the operator’s console, OPA0.

• If a checksum error is displayed when you register a license, check all the fields of data that you entered, including the checksum itself.

• After your PAKs are registered, they are activated (loaded) automatically as part of each system startup.

• If an OpenVMS Alpha license is registered with insufficient license units, the system displays the following message when the user (process) attempts to log in:

%LICENSE-F-EXCEEDED, licensed product has exceeded current license limits

Users can always log in to the operator’s console, OPA0, however.

• The default LICENSE database is located in the file SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB. You can move the database, although Compaq does not recommend doing so. If you move the database, you must either define the logical name LMF$LICENSE at the system level to point to the new database or use the /DATABASE=filespec qualifier with all LICENSE commands. To redirect LMF to another database location on a more permanent basis, add the following line to the command procedure SYS$MANAGER:SYLOGICALS.COM:

$ DEFINE/SYSTEM LMF$LICENSE device:[directory]LMF$LICENSE.LDB

If you specify a device other than SYS$SYSDEVICE, you must also mount the specified disk from the SYLOGICALS.COM command procedure.

• Each OpenVMS Alpha license is restricted to a single node for permanent PAKs. You must assign a System Communications Services (SCS) name to the license when you register with the VMSLICENSE.COM command procedure, or you must enter a LICENSE MODIFY/INCLUDE=node-name command after you register the license.

$Q:\adept8\entities\note.eps$ Note

The SCS node name is not necessarily the DECnet node name. SCSNODE is a system parameter; it can be a maximum of six alphabetic characters.

C.3 Restrictions

Availability Product Authorization Keys (PAKs) are available for the OpenVMS Alpha operating system. An OpenVMS Alpha PAK is identified by the keyword ALPHA in the PAK’s option field. Note the following restrictions:

• PAKs having the ALPHA option can be loaded and used only on Alpha computers. However, they can safely reside in a license database (LDB) shared by both VAX and Alpha systems.

• Because the LMF for Alpha systems is capable of handling all types of PAKs, including those for VAX systems, Compaq recommends that you perform your LDB tasks using the Alpha LMF.

• Availability PAKs for VAX systems (availability PAKs without the ALPHA option) will not load on Alpha systems. Only those availability PAKs containing the ALPHA option will load on Alpha systems.

• Other PAK types such as activity (also known as concurrent or n-user) and personal use (identified by the RESERVE_UNITS option) work on both VAX and Alpha systems.

• Avoid using the following LICENSE commands from a VAX system on a PAK containing the ALPHA option:

– REGISTER

– DELETE/STATUS

– DISABLE

– ENABLE

– ISSUE

– MOVE

– COPY

– LIST

• Caution: By default, all Alpha availability PAKs look disabled to a VAX system. Never use the DELETE/STATUS=DISABLED command from a VAX system on an LDB that contains Alpha PAKs. If you do, all Alpha PAKs will be deleted.

• With the exception of the DELETE/STATUS=DISABLED command, if you inadvertently use one of the previously listed LICENSE commands on an Alpha PAK while using a VAX system, the PAK and the database will not be adversely affected. Repeat the command using LMF running on an Alpha system, and the PAK should return to a valid state.

• If you do not repeat the command using LMF on an Alpha system, the system that you intended to disable will remain enabled (the system is not otherwise affected). Only the Alpha LMF can disable an Alpha PAK.

However, if you attempt to use any of the previously listed commands on a PAK located in an LDB that is shared with a VAX system, the following serious problems may result:

– Because Alpha PAKs look disabled to a VAX system, they are normally ignored at load time by VAX systems. However, if one of the previously listed commands is entered from a VAX system and the PAK information is not set to a valid state by an Alpha system, there is a chance the VAX system will attempt to load the Alpha PAK. Because the VAX system will be unable to load the PAK, the VAX LMF will report an error.

– Even if a valid VAX PAK for the affected product is in the LDB, it too may not load. In this case, system users might be denied access to the product.

If the PAK cannot be restored to a valid state because all Alpha systems are inaccessible for any reason, use your VAX system to disable the Alpha PAK. This prevents your VAX system from attempting to load the Alpha PAK.

D Preparing to Use OpenVMS Management Station

During the OpenVMS installation or upgrade procedure, the OpenVMS Management Station server software is automatically installed on your OpenVMS system disk.

If you accepted the default options, the PC client files will be located in SYS$COMMON:[TNT.CLIENT]. If these files are deleted from your system, you can download them from the following location:

http://www.openvms.compaq.com/openvms/products/argus/index.HTML#ordering

If the TNT$* server files have been deleted from SYS$SYSTEM, you can recover the server files by reinstalling the OpenVMS operating system or by downloading and installing the new kit from this website.

After you have ensured that OpenVMS Management Station software is installed on your system, follow the procedures described in this appendix.

D.1 Preparing Your OpenVMS System

You must prepare your OpenVMS system to run the server software so that your system can properly interact with the PC running the client software. The procedures include the following:

• Set up within a mixed-architecture cluster environment (if applicable).

• Start the server on other nodes.

• Update the printer and storage database.

• Edit the system files.

• Allow OpenVMS Management Station to control the printer and storage environment.

• Keep your printer environment up to date.

• Check if running third-party TCP/IP stacks.

• Determine and report problems.

D.1.1 Setting Up in a Mixed-Architecture Cluster Environment

The OpenVMS Management Station server creates several configuration files:

• TNT$UADB.DAT

• TNT$ACS.DAT

• TNT$JOURNAL.TNT$TRANSACTION_JOURNAL

• TNT$MONITOR.DAT

• TNT$MONITOR.TNT$MONITOR_JOURNAL

• TNT$EMERGENCY_MOUNT.COM

In a common-environment cluster with one common system disk, you use a common copy of each of these files located in the SYS$COMMON:[SYSEXE] directory on the common system disk, or on a disk that is mounted by all cluster nodes. No further action is required.

However, to prepare a common user environment for an OpenVMS Cluster system that includes more than one common VAX system disk or more than one common Alpha system disk, you must coordinate the files on those disks.

The following rules apply:

• Disks holding common resources must be mounted early in the system startup procedure, such as in the SYLOGICALS.COM procedure.

• You must ensure that the disks are mounted with each cluster reboot.

Follow these steps to coordinate files:

1. Decide where to locate the files. In a cluster with multiple system disks, system management is much easier if the common system files are located on a single disk that is not a system disk.

2. Copy TNT$UADB.DAT, TNT$ACS.DAT, TNT$MONITOR.DAT, TNT$MONITOR.TNT$MONITOR_JOURNAL, TNT$EMERGENCY_MOUNT.COM, and TNT$JOURNAL.TNT$TRANSACTION_JOURNAL to a location other than the system disk.

3. Edit the file SYS$COMMON:[SYSMGR]SYLOGICALS.COM on each system disk and define logical names that specify the location of the cluster common files.

Example

If the files will be located on $1$DJA16, define logical names as follows:

$ DEFINE/SYSTEM/EXEC TNT$ACS -
_$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$ACS.DAT

TNT$EMERGENCY_MOUNT.COM will be created in SYS$SYSTEM or in the directory pointed to by the TNT$ACS logical, if the logical exists.

$ DEFINE/SYSTEM/EXEC TNT$UADB -
_$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$UADB.DAT

$ DEFINE/SYSTEM/EXEC TNT$JOURNAL -
_$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$JOURNAL.TNT$TRANSACTION_JOURNAL

$ DEFINE/SYSTEM/EXEC TNT$MONITOR -
_$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$MONITOR

$ DEFINE/SYSTEM/EXEC TNT$MONITORJOURNAL -
_$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$MONITOR.TNT$MONITOR_JOURNAL

4. To ensure that the system disks are mounted correctly with each reboot, follow these steps:

1. Copy the SYS$EXAMPLES:CLU_MOUNT_DISK.COM file to the [VMS$COMMON.SYSMGR] directory, and edit it for your configuration.

2. Edit SYLOGICALS.COM and include commands to mount, with the appropriate volume label, the system disk containing the shared files.

Example

If the system disk is $1$DJA16, include the following command:

$ @SYS$SYSDEVICE:[VMS$COMMON.SYSMGR]CLU_MOUNT_DISK.COM -
_$ $1$DJA16: volume-label

D.1.2 Start the Server on Other Nodes

If you plan to run OpenVMS Management Station on more than one node in an OpenVMS Cluster without a reboot, you need to start the software on those nodes.

Use SYSMAN to start the server as follows:

$ @SYS$STARTUP:TNT$STARTUP.COM

Or, you can log into each node that shares the SYS$COMMON: directory and enter the following command:

$ @SYS$STARTUP:TNT$STARTUP.COM

If you are performing an upgrade or a reinstallation and OpenVMS Management Station is already running on the node, add the RESTART parameter to the startup command, as follows:

$ @SYS$STARTUP:TNT$STARTUP.COM RESTART

D.1.3 Error Log Information

OpenVMS Management Station writes error log information to the file TNT$SERVER_ERROR.LOG. This error log is created in the SYS$SPECIFIC:[SYSEXE] directory. If you start the OpenVMS Management Station server on multiple nodes in a cluster, which is recommended, there will be multiple server error logs.

D.1.4 Update the Printer and Storage Database

When you installed OpenVMS Management Station, the installation started the OpenVMS Management Station server on the installation node. If this installation was an upgrade, the server converts the existing OpenVMS Management Station database to the latest V3.* format. If this was a new installation, the server creates an initial version of the database file TNT$ACS.DAT and invokes the update functions automatically.

To complete the database, start the OpenVMS Management Station server on each node in your cluster. The instances of the server communicate with each other to determine device, queue, and volume information, and the server must be running on each node for this communication to take place.

D.1.5 Edit the System Files

To start the OpenVMS Management Station server from your system startup files, insert one of the following commands into your system startup procedures (probably SYS$MANAGER:SYSTARTUP_VMS.COM) after both the Queue Manager and network are started, but immediately prior to the ENABLE AUTOSTART/QUEUES.

$Q:\adept8\entities\note.eps$ Note

Remove any other invocations of TNT$STARTUP you might have added in previous releases of the OpenVMS Management Station.

OpenVMS Management Station cannot start until the network has started. If you start your network using a batch process, OpenVMS Management Station might start before the batch process completes and the network is started.

Command	Parameter 1	Parameter 2	Description
@TNT$STARTUP	blank	N.A.	Starts the server. Does not start printer queues or mount volumes.
@TNT$STARTUP	RESTART	N.A.	Shuts down a running server, then starts the server. Does not start printer queues or mount volumes.
@TNT$STARTUP	BOOT	blank	Starts the server. Starts any printer queues that are not yet started and are managed by OpenVMS Management Station. Does not mount volumes managed by OpenVMS Management Station.
@TNT$STARTUP	BOOT	ALL	Starts the server. Starts any printer queues that are not yet started and are managed by OpenVMS Management Station. Mounts any volumes that are not yet mounted and are managed by OpenVMS Management Station.
@TNT$STARTUP	BOOT	PRINTERS	Starts the server. Starts any printer queues that are not yet started and are managed by OpenVMS Management Station. Does not mount volumes managed by OpenVMS Management Station.
@TNT$STARTUP	BOOT	STORAGE	Starts the server. Mounts any volumes that are not yet mounted and are managed by OpenVMS Management Station. Does not start any printer queues.

Note that the effect of TNT$STARTUP BOOT, with no second parameter, has not changed from earlier releases. This command starts any printer queues that are not yet started and are managed by OpenVMS Management Station, but does not mount any volumes.

Add the following command line to the system shutdown file,
SYS$MANAGER:SYSHUTDWN.COM:

$ @SYS$STARTUP:TNT$SHUTDOWN.COM

D.1.6 Allow OpenVMS Management Station to Control the Printer and Storage Environment

It is not necessary to remove your existing queue startup and volume mount DCL procedures immediately. The OpenVMS Management Station server will recognize that you started a queue or mounted a volume with your command procedures and will assume that you want it that way.

As you become familiar with the server’s management ability, you can remove or comment out the DCL commands and procedures that perform these tasks and allow OpenVMS Management Station to control your printer and storage environment.

In addition, the OpenVMS Management Station server periodically (every 24 hours) generates a DCL command procedure that includes the commands to mount all of the volumes managed by OpenVMS Management Station. If you are familiar with DCL, you can look at this command procedure to see what actions OpenVMS Management Station performs for you. And, in the event of an unforeseen system problem or a corrupt server database (SYS$SYSTEM:TNT$ACS.DAT), you could use this command procedure to mount the volumes.

The name of the generated file is TNT$EMERGENCY_MOUNT.COM. TNT$EMERGENCY_MOUNT.COM is created in SYS$SYSTEM or in the directory pointed to by the TNT$ACS logical, if that logical name exists.

The OpenVMS Management Station server limits
TNT$EMERGENCY_MOUNT.COM to seven versions.

D.1.7 Keeping Your Printer Environment Up to Date

The OpenVMS Management Station server installation creates a file named SYS$STARTUP:TNT$UTILITY.COM. This command procedure scans the OpenVMS system and updates the database of known printers, queues, and related devices.

D.1.7.1 When is the Database Updated?

The database is updated:

• As part of the OpenVMS Management Station installation.

• When you specifically invoke TNT$UTILITY.COM.

• At periodic intervals as a server background thread. Two logical names control how often this server thread runs:

Logical Name	Description
TNT$PRINTER_RECON_ INTERVAL	How often the thread should run, in minutes, from when the server was last started on this node. If you do not define this logical, the default value is 1440 minutes (24 hours).
TNT$PRINTER_RECON_ INTERVAL_MIN	The minimum number of minutes that must elapse before the thread should run again, starting from when the database was last updated. If you do not define this logical, the default value is 60 minutes (1 hour).

You can think of these logicals as meaning “run the thread this often (TNT$PRINTER_RECON_INTERVAL), but make sure this much time has elapsed since the database was last updated (TNT$PRINTER_RECON_INTERVAL_MIN).”

Because you can run TNT$UTILITY.COM yourself, and because the OpenVMS Management Station server also updates the database, the TNT$PRINTER_RECON_INTERVAL_MIN logical prevents the database from being updated more frequently than is actually needed.

If you want to change the defaults for one of these logicals, define the logical on all nodes on which the OpenVMS Management Station server is running.

D.1.7.2 Do You Need to Run TNT$UTILITY.COM Manually?

If you use OpenVMS Management Station to make all of the changes to your printer configuration, the configuration files are immediately modified to reflect the changes and you probably do not need to specifically run TNT$UTILITY.COM.

However, if you or someone else uses DCL to make a change --- for example, if you use the DELETE /QUEUE command to delete a queue --- the configuration files will not be synchronized. In this case, the OpenVMS Management Station client will advise you to run TNT$UTILITY.COM to resynchronize the database.

Run the following procedure on one node in the cluster to make the database match your system:

$ @SYS$STARTUP:TNT$UTILITY.COM UPDATE PRINTERS

For example, if you or someone else used DCL to delete a queue, you need to delete that queue from the database. TNT$UTILITY.COM assumes that your system is set up and running the way that you want it to, so you should fix any problems before you run TNT$UTILITY.COM.

D.1.7.3 Are There Any Requirements for Running TNT$UTILITY.COM?

You need the SYSNAM privilege to run TNT$UTILITY.COM.

TNT$UTILITY.COM connects to the OpenVMS Management Station server on the current OpenVMS system to determine device and queue information. Therefore, the OpenVMS Management Station server must be running on the node where you run TNT$UTILITY.COM.

The OpenVMS Management Station server then connects to the other OpenVMS Management Station servers in the OpenVMS Cluster to determine device and queue information. It is generally a good idea to keep the OpenVMS Management Station server running on the other nodes in an OpenVMS Cluster to keep the database up to the minute.

However, if the OpenVMS Management Server is not able to connect to the OpenVMS Management Station server on a given node, it uses the known information about that OpenVMS node from the database. That is, in the absence of a valid connection to that OpenVMS node, the information in the database is assumed to be correct.

D.1.8 Keeping Your Storage Environment Up to Date

The TNT$UTILITY.COM utility accepts parameters (UPDATE STORAGE) to update the storage database. However, the storage database is updated dynamically every time you use the OpenVMS Management Station client to perform a storage management operation. Therefore, you do not need to run TNT$UTILITY.COM to update the storage database.

D.1.9 Enabling Disk Quotas

Before installing OpenVMS Management Station, you might have disabled disk quotas on the SYSTEM disk. If so, you should reenable the quotas and then rebuild to update quota information by entering the following commands:

$ RUN SYS$SYSTEM:DISKQUOTA
DISKQUOTA>ENABLE
DISKQUOTA>REBUILD
DISKQUOTA>EXIT

D.1.10 Caching Storage Configuration Data

OpenVMS Management Station uses two logical names to determine how often to refresh cached (in-memory) storage configuration data.

• TNT$PURGE_CYCLE_LATENCY -- Determines how often to wait (in seconds) after purging stale device reports before purging again. This value affects how frequently the clusterwide data (maintained by a “master server”) is updated in memory.

min = 180
default =  1800   (30 minutes)
max = 18000       (5 hours)

• TNT$LOCAL_SURVEY_LATENCY -- Determines the delay (in seconds) from one node-specific device survey to the next. This value is independent of clusterwide surveys requested by the “master server” when performing a purge.

min = 6
default =  60  (1 minute)
max = 600      (10 minutes)

For both logical names, smaller values result in the OpenVMS Management Station server consuming more CPU cycles in periodic purges or surveys.

If you do not accept the defaults, you might find that larger OpenVMS Cluster systems behave better with values on the high end of the allowed range.

If you do not define these logicals, the OpenVMS Management Station server uses the default values. If you do define these logical names, the values are used only if they are within the minimum to maximum range.

D.1.11 Running Third-Party TCP/IP Stacks

Compaq TCP/IP Services for OpenVMS Version 3.2 or higher is the only supported TCP/IP stack. Additional stacks have not been tested. However, TCP/IP stacks that are 100 percent compliant with the QIO interface for TCP/IP Services for OpenVMS should also work. (Contact your TCP/IP vendor for additional information and support issues.)

For the best chance of success, check the following:

• Make sure that the QIO service (for example, UCXQIO) is enabled.

• For TCPware, also make sure that TCPware’s UCX$IPC_SHR.EXE is an installed image.

• Also for TCPware, make sure you are running a version of TCPware that correctly implements a DECC-compatible socket interface, such as Version 5.3-3.

D.1.12 Determining and Reporting Problems

If you encounter a problem while using OpenVMS Management Station, please report it to Compaq. Depending on the nature of the problem and the type of support you have, you can take one of the following actions:

• If your software contract or warranty agreement entitles you to telephone support, call Compaq.

• If the problem is related to OpenVMS Management Station documentation, use the Internet address printed in front of this book to send us your comments.

D.1.13 Removing the OpenVMS Management Station Server

When you execute the OpenVMS installation or upgrade procedure, the OpenVMS Management Station server software is automatically installed on your OpenVMS system disk. If this server software is later reinstalled using another kit (for example, a kit downloaded from the web or a patch kit), you have the option to remove the OpenVMS Management Station. If you use the POLYCENTER Software Installation utility to remove the OpenVMS Management Station from the OpenVMS system, the following files are not removed:

• TNT$ACS.DAT

• TNT$JOURNAL.TNT$TRANSACTION_JOURNAL

• TNT$SERVER_ERROR.LOG

• TNT$UADB.DAT

• TNT$EMERGENCY_MOUNT.COM

Do not delete these files unless you have already removed the OpenVMS Management Station.

D.2 Preparing Your PC

During the OpenVMS installation or upgrade procedure, you selected the OpenVMS Management Station client software files to be installed on your OpenVMS system disk (or you added them later using the DCL command PRODUCT INSTALL TNT). After you have prepared your OpenVMS system to run the server software, you must next prepare your PC to run the client software.

D.2.1 Required Memory and Disk Space

Your PC requires 20 MB of free disk space to install the OpenVMS Management Station client software.

D.2.2 Distribution Files

The OpenVMS Management Station client kit, TNT032.EXE for Intel systems (Windows NT, 95, 98, 2000, and Me), is located in the SYS$COMMON:[TNT.CLIENT] directory.

D.2.3 Required Software

Microsoft Windows NT Version 4.0 (Service Pack 3 or higher) or Windows 95, 98, 2000, Me, or higher (Intel only) must be installed on each PC on which you want to install the OpenVMS Management Station client.

The version of the Microsoft Management Console (MMC) included in this baselevel requires files provided by Microsoft Internet Explorer, Version 3.02 or later, which must be present on the system.

D.2.4 Time Required for Installation

The time required to install the OpenVMS Management Station client software is approximately 5 minutes.

D.2.5 Copy the Client File to the PC

The client file TNT032.EXE is located in the SYS$COMMON:[TNT.CLIENT] directory. Copy the client file to a temporary directory on the PC using any of the following procedures:

• Create a file share to the OpenVMS system and copy the file.

• Use FTP on the PC to copy the file from the OpenVMS system.

D.2.6 Installation Directory

The installation procedure allows you to select the installation directory, and suggests \Program Files\OpenVMS Mgmt Station\ as the default.

D.2.7 Installation Procedure

Run TNT032.EXE from a temporary directory. It is a self-extracting executable file that automates the OpenVMS Management Station installation.

D.2.8 Recovering from Errors

If an error occurs during installation, you will receive an error message describing the problem. This information can help you determine the cause of the problem. An error can occur during the installation if one or more of the following conditions exist:

• The operating system version is incorrect

• Disk space and memory necessary for successful installation are inadequate

D.3 After Installing the Client Software on Your PC

When you create an OpenVMS Cluster or OpenVMS Node object in an OpenVMS Management Domain, you select the transport you want to use for all connections to that system. You can choose DECnet Phase IV for OpenVMS or TCP/IP.

OpenVMS Management Station uses this transport for all communications between the PC and this system, or between any other OpenVMS system that is running the OpenVMS Management Station server and this system.

$Q:\adept8\entities\note.eps$ Note

The OpenVMS Management Station client supports only TCP/IP connections for primary servers. That is, the connection between the PC and the OpenVMS system uses only TCP/IP. Therefore, at least one OpenVMS system must be running TCP/IP.

You do need to make sure that your PC can connect to the primary-server systems, as described in the following sections. OpenVMS Management Station connects your PC to the primary-server system and then routes management operations to the target systems.

D.4 Defining TCP/IP Nodes

Your hosts file or name server must be able to resolve the IP name or address of all primary-server systems. If you can successfully ping the primary-server systems from your PC, then this condition is met.

D.5 Uninstalling Version 2.1 of the OpenVMS Management Station Client

Version 3.2 of the OpenVMS Management Station client is not dependent on Version 2.1 and does not share any files with this prior version. After installing the Version 3.2 client, you can uninstall the Version 2.1 client software.

D.6 Uninstalling OpenVMS Management Station

If you need to uninstall the OpenVMS Management Station client software, make sure you first exit OpenVMS Management Station. The uninstallation fails if OpenVMS Management Station is currently running.

If you run the OpenVMS Management Station Help, the following files might be created:

• VMSMGMT.FTS

• VMSMGMT.GID

• VMSPRINT.FTS

• VMSPRINT.GID

• VMSSCOPE.FTS

• VMSSCOPE.GID

• VMSSTORE.FTS

• VMSSTORE.GID

• VMSACNT.FTS

• VMSACNT.GID

The OpenVMS Management Station Uninstall program does not delete these files. To complete the uninstall:

1. Delete these files.

2. Delete the OpenVMS Management Station directory.

Note that the OpenVMS Management Station Uninstall program does not uninstall the Microsoft Management Console (MMC) support files.

D.7 Getting Started with OpenVMS Management Station

All information about getting started, setting up, and using OpenVMS Management Station is contained in online help and the OpenVMS Management Station Overview and Release Notes.

Document revision date: 24 June 2002

Preface

Intended Audience

When to Use This Manual

Document Structure

Related Documents

Reader’s Comments

How to Order Additional Documentation

Conventions

1 Getting Started

1.1 Key Terms

1.2 Examining Software and Hardware Components

1.2.1 Hardware Components

1.2.2 Software Components

1.2.3 Operating System CD–ROM

1.2.4 Firmware Revision Checking

1.2.5 Device Naming Conventions

1.3 Using the Operating System CD–ROM

1.3.1 Using the Menu

1.3.2 Sample Menu Display

1.3.3 How the Install or Upgrade Option Works

1.3.3.1 Specifying the INITIALIZE Option

1.3.3.2 Specifying the PRESERVE Option

1.3.4 How the Layered Products Options Work

1.3.5 How the DCL Option Works

1.3.6 How the Shutdown Option Works

1.4 Making the Install/Upgrade/Backup Selection

2 Preparing to Install in an OpenVMS Cluster Environment

2.1 Mixed-Version Support

2.2 OpenVMS Cluster Information You Will Need

2.3 Beginning the Installation

3 Installing the OpenVMS Alpha Operating System

3.1 Preparing to Respond to Prompts During the Installation

3.2 Booting the Operating System CD–ROM

3.2.1 Booting from the Local Drive

3.2.2 Booting from the InfoServer

3.3 Creating the System Disk

3.3.1 Installing from the CD–ROM

3.3.2 Choosing INITIALIZE or PRESERVE

3.3.3 Specifying the Target Disk

3.3.4 Specifying the Volume Label

3.3.5 Specifying the On-Disk Structure Level

3.3.6 Setting the SYSTEM Account Password

3.3.7 Becoming a Cluster Member

3.3.8 Becoming an OpenVMS Galaxy Instance

3.3.9 Installing Windowing and Networking Products

3.3.10 Setting System Parameters

3.3.11 Setting Time Zone Information

3.4 Registering Licenses

3.4.1 Types of OpenVMS Alpha Licenses

3.4.2 How to Register Licenses

3.4.3 Using the Licensing Procedure

3.5 Completing the Installation

3.5.1 Choosing Descriptive Help Text

3.5.2 Selecting Components

3.5.3 List of Components

3.5.4 Completing the Procedure

3.6 Installing Layered Products

3.7 Booting the New System Disk

3.7.1 Preparing to Boot the New System Disk

3.7.2 How to Boot the New System Disk

3.8 Joining an OpenVMS Cluster

3.8.1 OpenVMS Cluster Prompts

3.9 Running AUTOGEN

3.9.1 Automatic Reboot after Autogen

3.9.2 Manual Reboot after Autogen

3.10 Logging in to the SYSTEM Account from a Character Cell Terminal

3.11 Logging in to the SYSTEM Account from a Workstation

3.12 Postinstallation Tasks

4 After Installing the OpenVMS Alpha Operating System

4.1 Registering Your Licenses

4.2 Creating Accounts

4.3 Backing Up Your System Disk

4.4 Customizing the System

4.5 Initializing CDSA

4.6 Configuring Kerberos

4.7 Configuring and Starting Networking Software

4.7.1 DECnet-Plus for OpenVMS

4.7.2 DECnet Phase IV for OpenVMS

4.7.3 Compaq TCP/IP Services for OpenVMS

4.8 Testing the System with UETP