[OpenVMS documentation]
[Site home] [Send comments] [Help with this site] [How to order documentation] [OpenVMS site] [Compaq site]
Updated: 11 December 1998

OpenVMS VAX
Version 7.2 Upgrade and
Installation Manual


Previous Contents Index

7.2.5 Specifying the Source Drive

VMSINSTAL asks for the name of the drive that holds the distribution media:


* Where will the distribution volumes be mounted: 

Enter the device name of the source drive. For example, if you have a VAX 6000 series computer that has a TK70 with a device name of MUC6, type MUC6 and press Return.

If the drive is connected to an HSC, enter the HSC name and the device name of the drive separated by a dollar sign ($). (If you do not enter the device name in this manner, it will cause a failure in Phase 2.) For example, if the HSC name is MUTT and the device name is MUA0, enter the following and press Return:


* Where will the distribution volumes be mounted: MUTT$MUA0

If you are not using an InfoServer device, proceed to Section 7.2.6.

If you are upgrading from a compact disc drive connected to an InfoServer, the device name is DADn. The n part of the device name was displayed when you bound to the distribution compact disc as previously described in Section 7.2.2.

If VMSINSTAL displays an error message, make sure the drive is connected and set up properly. Enter the name again. If VMSINSTAL displays another error message, use the following procedure to verify the device name:

  1. Press Ctrl/Y to exit from VMSINSTAL.
  2. Enter the SHOW DEVICE command to make sure you have the correct device name.
  3. Restart the upgrade procedure from Section 7.2.3.

If VMSINSTAL does not display an error message, proceed to Section 7.2.6.

7.2.6 Entering the Product Name

When VMSINSTAL displays the following message, type VMS072 and press Return. Make sure that you use the number zero (not the letter "O") when you type VMS072. For example:


Enter the products to be processed from the first distribution volume set. 
* Products: VMS072 

When the procedure displays the following message, press Return:


* Enter installation options you wish to use (none): 

7.2.7 Mounting the First Volume

VMSINSTAL displays a message similar to the following:


Please mount the first volume of the set on DKB200:. 

When the procedure displays the following message, type Y (for Yes) and press Return:


* Are you ready? Y 

The procedure displays messages similar to the following:


%MOUNT-I-MOUNTED, VAXVMS072 mounted on _VXPCSI$DKB200: 
 
The following products will be processed: 
 
  VMS V7.2 

After a slight pause, the procedure displays a message similar to the following:


        Beginning installation of VMS V7.2 at 10:08 
 
%VMSINSTAL-I-RESTORE, Restoring product saveset A ... 
 

7.2.8 Monitoring Messages from VMSINSTAL

The upgrade procedure displays several important messages that provide you with the following information:

Read these messages carefully to decide whether or not you need to interrupt the upgrade procedure. An interruption is allowed before Phase 1. The procedure displays the following message:


* Do you want to continue? (Y/N): 

To continue the upgrade, type Yes and press Return.

To interrupt the upgrade, do the following:

  1. Type No and press Return.
  2. If prompted for another product, type EXIT to exit from VMSINSTAL.

7.2.9 Verifying the Date and Time

The procedure displays the current date and time. If the date and time are correct, type Yes. If they are incorrect, type No. Enter the correct date and time using the 24-hour clock format and press Return. For example:


PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 13-NOV-1998 10:19 

7.3 Upgrade Phase 1

This section describes Phase 1 of the upgrade. During this phase, you provide passwords for system accounts and select OpenVMS options, and the procedure restores the files in the OpenVMS required save set (VMS072.B).

At the end of this phase, the procedure shuts down your VAX computer. If your computer uses console media when booting and the boot file was modified as described in Section 7.1, the system should reboot automatically. Otherwise, you must reboot manually from the SYSF directory.

7.3.1 Specifying the Type of Upgrade

At the beginning of Phase 1, the procedure displays a message similar to the following:


    Upgrade Phase 1  13-NOV-1998 10:19:30.85 
 
* Are you performing a rolling upgrade? (Y/N): 

If you are performing a concurrent upgrade or an upgrade on a standalone system, type No and press Return.

If you are performing a rolling upgrade, type Yes and press Return. The procedure asks you several questions to determine if all system disks in the cluster (other than the one you are upgrading) are running at least OpenVMS VAX Version 6.2. Follow the instructions in Section 6.4.

7.3.2 SYSTEST and FIELD Account Creation

If your system does not have SYSTEST or FIELD accounts, you will be given the opportunity to create them at this time. These accounts are not required for normal operation of OpenVMS. The User Environment Test Program (UETP) uses SYSTEST to perform its functions. If this account does not exist you will have to create it in order to run UETP. FIELD is traditionally used for field service access. If this account does not exist, you may have to create it later or provide an alternate account for field service.


SYSTEST account does not exist ... 
* Do you want to create this account? (Y/N): 
    
FIELD account does not exist ... 
* Do you want to create this account? (Y/N): 

7.3.3 Entering Passwords

To ensure system security, the upgrade procedure requires you to enter passwords for the SYSTEM, SYSTEST, and FIELD accounts before continuing. Passwords must contain at least 8 characters; they are not displayed by the system. Press Return after you enter each password and it will be verified. You will not be prompted for SYSTEST and FIELD passwords if those accounts do not exist. For example:


To help provide a more secure system, you are asked to enter passwords 
for key system accounts. Passwords must be a minimum of 8 characters 
in length. You can enter new or existing passwords. 
 
Enter passwords for the following accounts: 
 
             SYSTEM, SYSTEST, FIELD 
 
* Enter password for SYSTEM: 
* Reenter for verification: 
%UAF-I-MDFYMSG, user record(s) updated 
%VMS-I-PWD_OKAY, account password for SYSTEM verified 
 
* Enter password for SYSTEST: 
* Re-enter for verification: 
%UAF-I-MDFYMSG, user record(s) updated 
%VMS-I-PWD_OKAY, account password for SYSTEST verified 
 
     The SYSTEST_CLIG account will be disabled.  You must reenable 
     it before running UETP but do not assign a password. 
 
* Enter password for FIELD: 
* Reenter for verification: 
%UAF-I-MDFYMSG, user record(s) updated 
%VMS-I-PWD_OKAY, account password for FIELD verified 

If you enter a password incorrectly or if the password is too easy to guess, the procedure displays error messages similar to the following:


%VMS-W-PWD-INVALID, account password for SYSTEST is invalid 
%VMS-I-PWD-WEAK, password is too easy to guess 
 
Because of the preceding error, you must take action to secure this account. 
You must either disable this account, change its password, or do both. 

When the procedure asks if you want to disable the account, type No and press Return. When the procedure asks if you want to enter a new password, type Yes and press Return. Then enter a new password. For example:


Do you want to disable the account (Y/N)? N
Do you want to change the account password (Y/N)? Y
You must now select a new primary password for the SYSTEST account. The 
password you select must be at least 8 characters in length and cannot be 
the same as the name of the account. 
 
New password: 
Verification: 
%UAF-I-MDFMSG, user record(s) updated 
%VMS-I-PWD-SET, primary password for account SYSTEST set

After you have correctly entered the passwords, the procedure does the following:

7.3.4 Choosing the Boot Method

If your VAX computer is not one of the following, go to Section 7.3.5.

If your VAX computer is included in the preceding list, the procedure can temporarily modify the DEFBOO.CMD (or DEFBOO.COM if you have a VAX 8600 computer) to boot from the [SYSF] directory. During Phase 4 of the upgrade, the procedure restores the DEFBOO.CMD (or DEFBOO.COM) file that is set up to boot from the current system disk and system root.

The procedure displays a message similar to the following (except for VAX--11/730, 11/780, and 8600 computers):


* Do you want to boot from the [console media]? 

If you prefer to boot your system manually from the [SYSF] directory or if you are booting directly from a local system disk, type No, press Return, and go to Section 7.3.5 to continue the upgrade.

Type Yes and press Return if one of the following is true:

The procedure prompts you to insert the console media in the drive. Insert the backup copy of the console media into the drive and do not remove it from the drive until the upgrade has been completed. Make sure the console media is write enabled.

7.3.5 File Cleanup

The procedure does the following:

As the procedure performs each of these tasks, it displays messages describing what is being done. When this step is completed, the procedure displays a message similar to the following:


File cleanup complete - 13-NOV-1998 10:34:16.34 

7.3.6 Selecting Optional OpenVMS Components

The procedure displays information about optional OpenVMS VAX files and the remaining amount of disk space. The information is similar to the following (block sizes might vary slightly):


Select optional software you want to install. You can install one 
or more of the following OpenVMS or DECwindows components: 
 
o OpenVMS library                              -  52200 blocks 
o OpenVMS optional                             -  19000 blocks 
o OpenVMS Help Message                         -  10400 blocks 
o OpenVMS Management Station                   -  20000 blocks 
o DECwindows base support                      -   4400 blocks 
o DECwindows workstation support               -  23800 blocks 
      -  75 dots per inch video fonts          -   (included) 
      - 100 dots per inch video fonts          -   6200 blocks 
o DECnet-Plus networking                       -  80000 blocks 
o DECnet Phase IV networking                   -    800 blocks 
 
Space remaining on system disk: 1674710 blocks 

You must indicate which of the options you want to install. If you require network support, you must select the OpenVMS library component.

Note that if you do not install the optional OpenVMS components at this time, you can install them after the upgrade by using the VMSTAILOR and DECW$TAILOR utilities. However, the Help Message utility can be tailored on (added) to the system disk only. If you do not choose to install the Help Message files at this point in the procedure and want them on an alternate device, you will not be able to use VMSTAILOR to restore them later. If you want to install Help Message files on an alternate disk after the installation procedure completes, you can use the BACKUP command, as follows:

BACKUP/VERIFY source-device:[000000]VMS072.E/SAVE_SET-
target-device:[directory-name]

For source-device, enter the device name for the drive on which the distribution media is mounted. For target-device, enter the device name on which the alternate disk is mounted, and for directory, enter the name of the directory to which you are copying the files.

Also note that, for TK50 tape cartridges, it is quicker to install OpenVMS VAX software during the upgrade than to add software after the upgrade with a tailoring utility. For information about using VMSTAILOR, see Chapter 10. To select the options you want to install, follow the instructions displayed by the procedure.

7.3.6.1 OpenVMS Library Files

The procedure displays the following message:


* Do you want to install the OpenVMS library files? (Y/N) 

The file subclasses of the OpenVMS library (VMS072.C) save set are listed in Appendix D. If you want to install the VMS072.C files, type Yes and press Return. If you require network support, you must select the OpenVMS library component. If you do not want to install the VMS072.C files, type No and press Return.

7.3.6.2 OpenVMS Optional Files

The procedure displays the following message:


* Do you want to install the OpenVMS optional files? (Y/N) 

The file subclasses of the OpenVMS optional (VMS072.D) save set are listed in Appendix D. If you want to install the VMS072.D files, type Yes and press Return. If you do not want to install the VMS072.D files, type No and press Return.

7.3.6.3 Help Message Files

The procedure displays the following message:


    The Help Message utility (MSGHLP) provides online explanations 
    and user actions for OpenVMS messages in place of the hardcopy 
    OpenVMS System Messages and Recovery Procedures Reference Manual, 
    which is now separately orderable. 
 
    The MSGHLP database, MSGHLP$LIBRARY.MSGHLP$DATA, consumes 
    approximately 10400 blocks and will be placed by default 
    on your system disk in SYS$COMMON:[SYSHLP] unless you specify an 
    alternate device when prompted. 
 
* Do you want to install the MSGHLP database? (Y/N) 

The Help Message utility is an online system for system messages documentation. You can install Help Message either on the system disk or on an alternate disk. If you want to install the Help Message files, type Yes and press Return.

The procedure displays the following message:


    You can install this database on your system disk in SYS$COMMON:[SYSHLP] 
    or on an alternate device. If you specify an alternate device, but no 
    directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. When 
    prompted, take the default of the system disk or specify an alternate 
    device using this format: 
 
                           device:[directory] 
 
* Where do you want to install the MSGHLP database? [SYS$COMMON:[SYSHLP]] 
 
    Space remaining on system disk:  1593110 blocks 

The Help Message database is installed in the area you specified.

7.3.6.4 OpenVMS Management Station Files

The procedure displays the following message:


   The OpenVMS Management Station is a client-server application 
   that provides OpenVMS system management capabilities through a 
   client application on a personal computer (PC) running Microsoft 
   Windows. The server application runs on OpenVMS systems and is 
   automatically installed as part of the OpenVMS operating system. 
 
   This option provides the files used to create the installation 
   media for the PC client software.  If you want to use the OpenVMS 
   Management Station, you must install these optional files on at 
   least one OpenVMS system to create the installation media, which 
   can then be used to install the PC client on one or more PCs. 
 
   The OpenVMS Management Station client can run on Windows 3.1 
   (including Windows for Workgroups), Windows NT, or Windows 95. 
 
   The OpenVMS Management Station optional files consume approximately 20000 
   blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT]. 
 
* Do you want to install the optional OpenVMS Management Station files? (Y/N) 
 
   Space remaining on system disk: 1573110 blocks 
 

If you want to use the OpenVMS Management Station software, you must install these files. After the upgrade procedure completes, follow the instructions in Appendix G to prepare your OpenVMS system and your PC to run the OpenVMS Management Station server and client software.

7.3.7 Choosing DECwindows Support Options

Next, the procedure displays messages about the DECwindows components shipped with OpenVMS VAX Version 7.2.

The OpenVMS VAX operating system no longer ships the OpenVMS DECwindows product. The operating system now ships only the DECwindows base support and DECwindows workstation support components. To get full DECwindows support, you must also install the separate DECwindows Motif for OpenVMS VAX (previously called VMS DECwindows Motif) layered product, which supports both Motif and XUI environments.

Note that the DECwindows base support and DECwindows workstation support components are not shipped with the DECwindows Motif for OpenVMS layered product. If you want to install these options, you must select them now or use the DECW$TAILOR option after the installation procedure completes.

Before you indicate whether you want to install DECwindows support software, consider the following:
If you... Then choose...
Intend to install the DECwindows Motif layered product DECwindows base support.
Intend to install the DECwindows Motif layered product on a workstation or on a VAXcluster system that contains workstations DECwindows base support and
DECwindows workstation support.
Are not planning to install the DECwindows Motif layered product but are installing OpenVMS VAX on a workstation or on a VAXcluster that includes workstations DECwindows base support and
DECwindows workstation support.
Want to provide font files for X terminals DECwindows base support and
DECwindows workstation support.
Have a workstation monitor (for example, a VR150, VR160, or VR295) capable of displaying 100 dots/inch or a VAXstation 4000 series computer, which uses 100 dots/inch video fonts by default DECwindows base support and
DECwindows workstation support with the 100 dots/inch option.

By selecting the workstation support files, you automatically get 75 dots/inch video font files, and you will be prompted to indicate if you want to install 100 dots/inch video font files.

The procedure displays the following:


    You can select DECwindows now, or you can use the DECW$TAILOR utility 
    to provide or remove DECwindows support after upgrade. 
 
    Some media, TK50s in particular, can be very slow when tailoring on files. 
    You might want to select DECwindows now and tailor off unwanted files later. 
 
    NOTE: This kit does NOT contain full DECwindows. 
          To obtain full DECwindows, you must also install the separate 
          layered product, DECwindows Motif for OpenVMS VAX. 
          Version 1.2-3 is the minimum version of DECwindows Motif for OpenVMS VAX 
          that can be used with OpenVMS VAX V7.2. 
 
    The DECwindows components provided in this kit require approximately 
    34400 blocks, broken down as follows: 
 
         o DECwindows base support                    -   4400 blocks 
         o DECwindows workstation support             -  23800 blocks 
           -  75 dots per inch video fonts                 (included) 
           - 100 dots per inch video fonts (optional) -   6200 blocks 
 
     You must select the DECwindows base support option if 
         - you plan to run DECwindows software, or 
         - you are installing this kit on 
             * a workstation or 
             * a VAXcluster that contains workstations, or 
         - you want to provide font files for Xterminals. 
 
     If you are installing this kit on a system that includes Xterminals 
     and you do NOT select DECwindows base support, then you will have to use 
     the DECW$TAILOR utility to provide font files. 
 
* Do you want the DECwindows base support? (Y/N) y 
 
     Space remaining: 1568710 blocks 
 
 
     You must select the DECwindows workstation support option if 
         - you are installing this kit on 
             * a workstation or 
             * a VAXcluster that contains workstations, or 
         - you want to provide font files for Xterminals. 
 
     If you are installing this kit on a system that includes Xterminals 
     and you do NOT select DECwindows workstation support, then you will have 
     to use the DECW$TAILOR utility to provide font files. 
 
* Do you want to provide DECwindows workstation support? (Y/N) y 
 
     Space remaining:  1544910 blocks 
 
 
     DECwindows workstation support includes the 75 dots per inch video fonts. 
 
     All DECwindows applications run with 75 dots per inch video fonts. 
     By default, most systems start up with 75 dots per inch video fonts. 
     Certain applications can take advantage of 100 dots per inch video fonts. 
 
     For the VAXstation 4000 series machine, 100 dots per inch video fonts 
     are used by default.  If you decide not to install 100 dots per inch 
     video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM 
     to force 75 dots per inch video fonts to be the default.  Otherwise, 
     certain applications may not space text properly. 
 
     For instructions on how to configure your system with both 75 and 100 
     dots per inch video fonts, see the installation guide or look at the 
     template command procedure SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE. 
 
*Do you want 100 dots per inch video fonts installed? (Y/N) y 
 
   Space remaining:  1538710 blocks 


Previous Next Contents Index

[Site home] [Send comments] [Help with this site] [How to order documentation] [OpenVMS site] [Compaq site]
[OpenVMS documentation]

Copyright © Compaq Computer Corporation 1998. All rights reserved.

Legal
6521PRO_009.HTML