HP OpenVMS Systems Documentation

If upgrading from an InfoServer device, perform the following steps:

1. Start the InfoServer Client software by entering the following command:

   $ @SYS$STARTUP:ESS$STARTUP CLIENT

   
   The CLIENT parameter loads the client driver, ESS$DADDRIVER.EXE, and the InfoServer transport driver, ESS$LASTDRIVER.EXE.
2. As the startup procedure executes, it displays the following messages:

   %LASTCP-I-VERSION, LASTDRIVER X1.5 is stopped %LASTCP-I-ADAINIT, Initializing adapter xxx for LASTDRIVER %LASTCP-I-STARTED, LASTDRIVER X1.5 started on node yyy

3. After you start the InfoServer Client software, you must make the compact disc drive accessible to your system by completing the following steps:
   1. Insert the distribution compact disc in the compact disc drive connected to the InfoServer.
   2. Enter the following commands:

      $ RUN SYS$SYSTEM:ESS$LADCP LADCP> BIND/CONNECT/SYSTEM VAXVMS073 %LADCP-I-BIND, service bound to logical unit DAD$VMS073 (_DADn:) LADCP> EXIT

   
   Make note of the device name _DADn: in the previous display. You will have to specify this device name during the upgrade.

To start VMSINSTAL, use the following procedure:

1. Log in to the SYSTEM account.
2. Enter the following command:

   $ @SYS$UPDATE:VMSINSTAL

VMSINSTAL displays a message similar to the following, depending on which version of the operating system is currently running on your system:

        OpenVMS VAX Software Product Installation Procedure V7.3

It is 13-NOV-2000 at 10:08.

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

VMSINSTAL checks your system's account quotas. If it finds account quotas that are less than it expects, VMSINSTAL displays a message similar to the following:

%VMSINSTAL-W-LOWQUOTA, The following account quotas may be too low.
-VMSINSTAL-W-LOWQUOTA, If you want to modify these account quotas, type NO to
-VMSINSTAL-W-LOWQUOTA, the next question, modify the appropriate quotas, log out
-VMSINSTAL-W-LOWQUOTA, then log back in and restart this procedure.

         BYTLM: currently 32512; minimum expected 32768

* Do you want to continue anyway [NO]?

You should have verified that your SYSTEM account quotas were sufficient before beginning the upgrade. (See Section 5.5.8 for the minimum required values and for instructions for modifying quotas and limits.)

To modify the account quotas now, do the following:

1. Type No and press Return.
2. Modify the account quotas you want to change.
3. Log out of the SYSTEM account; then log back in so that the new quotas will be in effect.
4. Restart VMSINSTAL.

To continue the upgrade without modifying the account quotas, type Yes and press Return.

7.2.4 Backing Up the System Disk

The procedure displays the following message:

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

If you have made a standalone BACKUP of the system disk, press Return and go to Section 7.2.5.

If you have not made a standalone image backup of the system disk, do the following:

1. Type N (for No) and press Return. VMSINSTAL ends and the dollar-sign prompt ($) is displayed.
2. Back up the system disk as described in the upgrade and installation supplement for your VAX computer.
3. After you have made a backup of the system disk, start the upgrade procedure again.

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 VMS073 and press Return. Make sure that you use the number zero (not the letter "O") when you type VMS073. For example:

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

When the procedure displays the following message, press Return:

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

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, VAXVMS073 mounted on _VXPCSI$DKB200:

The following products will be processed:

  VMS V7.3

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

        Beginning installation of VMS V7.3 at 10:08

%VMSINSTAL-I-RESTORE, Restoring product saveset A ...

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

• What VMSINSTAL is doing.
• Notes, suggestions, and restrictions about various parts of the upgrade.
• Status of the upgrade.

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.

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-2000 10:19

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 (VMS073.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-2000 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 7.1. Follow the instructions in Section 6.5.

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):

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:

• Checks the account quotas in the DEFAULT, SYSTEM, and various other accounts and modifies them if necessary
• Turns off quotas on the system disk
• Stops OPCOM
• Stops the error formatter (ERRFMT)

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

VAX 8200, 8250, 8300, 8350
VAX 8600, 8650
VAX 9000

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 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:

• You want to boot from the console media.
• You are using a CI750.

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:

• Checks for the location of the SYS$TIMEZONE.DAT file, which must now be in the SYS$COMMON:[SYSEXE] directory. If the procedure finds this file in some other directory, it deletes it from that directory. Later, during the final phase of the upgrade, the procedure prompts you for the information it needs to create a SYS$TIMEZONE.DAT file in the SYS$COMMON:[SYSEXE] directory.
• Renames files found in SYS$SPECIFIC:[SYSMGR] and in SYS$COMMON:[SYSMGR] by adding _OLD_SPECIFIC to the file extensions. For example, [SYSMGR]LOGIN.COM becomes [SYSMGR]LOGIN.COM_OLD_SPECIFIC. (The file extensions are restored during Phase 6 of the upgrade procedure.)
• Cleans up the system disk by purging all accounting data files, operator logs, and the directory SYSERR. The procedure also deletes all JNL files in the root directory and its subdirectories.
• Builds the directory tree [SYSF] and deletes the OpenVMS VAX and DECwindows files that are not needed to reboot during Phase 2 of the upgrade.

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-2000 10:34:16.34

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]VMS073.E/SAVE_SET -
_$ target-device:[directory-name]

where:

• source-device is the device name for the drive on which the distribution media is mounted.
• target-device is the name of the device on which the alternate disk is mounted.
• directory-name is 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 (VMS073.C) save set are listed in Appendix D. If you want to install the VMS073.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 VMS073.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 (VMS073.D) save set are listed in Appendix D. If you want to install the VMS073.D files, type Yes and press Return. If you do not want to install the VMS073.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 database 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.