[Digital logo]
[HR]

OpenVMS VAX Version 7.1 Upgrade and Installation Manual


Previous | Contents

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 the Return key, and go to Section 7.4.4 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.4.4 Step 4: 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 - 22-NOV-1996 15:29:41.92 

7.4.5 Step 5: Select 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                              -  53400 blocks 
o OpenVMS optional                             -  21200 blocks 
o OpenVMS Help Message                         -  10200 blocks 
o OpenVMS Management Station                   -  21200 blocks 
o DECwindows base support                      -   3800 blocks 
o DECwindows workstation support               -  23500 blocks 
      -  75 dots per inch video fonts          -   (included) 
      - 100 dots per inch video fonts          -   6000 blocks 
o DECnet-Plus networking                        -  85000 blocks 
 
Space remaining on system disk: 682440 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 and the three reference manuals can be tailored on to the system disk only. If you do not choose the Help Message files or the three manuals 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 on an alternate disk after the installation procedure completes, you can use the BACKUP command, as follows:

BACKUP/VERIFY source-device:[000000]VMS071.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.4.5.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 (VMS071.C) save set are listed in Appendix D. If you want to install the VMS071.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 VMS071.C files, type No and press Return.

7.4.5.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 (VMS071.D) save set are listed in Appendix D. If you want to install the VMS071.D files, type Yes and press Return. If you do not want to install the VMS071.D files, type No and press Return.

7.4.5.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 10200 blocks and will be placed by default 
    on your system disk in SYS$COMMON:[SYSHLP] unless you specify an 
    alternate device when prompted. 
 
    Users with limited disk space can access the MSGHLP database 
    on a read-only basis at DAD1:[HELP_MESSAGE]. 
 
* 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]] DUA1
 
The Help Message database is installed in the area you specified, and the system displays information similar to the following:
%MOUNT-I-MOUNTED, VMS071       mounted on DUA1 
 
    Space remaining on alternate device DUA1:: 124532 blocks 

7.4.5.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 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. 
 
   Note: To use the OpenVMS Management Station on your PC, you must be 
   running Digital's PATHWORKS V5.0A for DOS and Windows (or V5.1) software. 
 
   The OpenVMS Management Station optional files consume approximately 21200 
   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:     623240 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.4.6 Step 6: Choose DECwindows Support Options

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

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 support 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 provide DECwindows options now and tailor off unwanted files later. 
 
     NOTE: This kit does NOT contain full DECwindows. 
           To obtain full DECwindows support, 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 Version 7.1. 
 
     The DECwindows components provided in this kit require approximately 
     29350 blocks, broken down as follows: 
 
         o DECwindows base support                    -   3800 blocks 
         o DECwindows workstation support             -  23500 blocks 
           -  75 dots per inch video fonts                 (included) 
           - 100 dots per inch video fonts (optional) -   6000 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) 
 
     Space remaining: 619640 
 
     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 base 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) 
 
     Space remaining:  598890 
 
     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 template command procedure 
     SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE. 
 
*Do you want 100 dots per inch video fonts installed? (Y/N) 
 
   Space remaining:  593890 

7.4.7 Step 7: Select Networking Software

Next, the procedure displays messages describing the DECnet options. For more information, refer to Section 1.2.1.

    Beginning with OpenVMS V7.1 DECnet-Plus is provided with the OpenVMS 
    operating system.  Digital strongly recommends that DECnet users 
    install DECnet-Plus.  DECnet Phase IV applications are supported 
    by DECnet-Plus. 
 
     If you plan to install DECnet Phase IV do NOT select DECnet-Plus. 
 
* Do you want to install DECnet-Plus. (Y/N) Y 
 
Space remaining on system disk:  508890 blocks 

7.4.8 Step 8: Verify Your Choices

The procedure displays a list of OpenVMS VAX and DECwindows support options that you have chosen and gives you the opportunity to change your mind before proceeding by displaying the following message:

* Is this correct? (Y/N) 

If you answer Yes to this prompt, the procedure restores the OpenVMS required save set (VMS071.B) and purges the page, swap, dump, and authorization files.

If you answer No to this prompt, you can respecify the OpenVMS VAX and DECwindows options that you want to install. The procedure restores the DECwindows components you have chosen during Phase 2.

7.4.9 Step 9: Shut Down Your System

After several minutes, the upgrade procedure indicates that the system will shut down to reboot the partially upgraded OpenVMS VAX system and displays information about how to reboot the system.

On certain VAX computers, the procedure displays the following message:

* Press RETURN to shutdown system: 

Once you have read the information displayed on the screen, press Return to begin the shutdown.

7.4.10 Step 10: Reboot the System

If your system uses console media, it should automatically reboot from the SYSF directory when the shutdown is complete. If you have a MicroVAX or if your system does not reboot from SYSF, halt the system and boot from the [SYSF] directory. For most MicroVAX and VAXstation computers, use the BOOT command in the following format and substitute the device name of the system disk for ddcu:

>>> B/F0000000 ddcu

If the system fails to boot, you can boot into SYSBOOT by entering the following:

>>> B/F0000001 ddcu

For more information on booting your computer from the SYSF directory, see the upgrade and installation supplement for your VAX computer.

7.4.11 Step 11: Verify System Time

When the system reboots, it displays a message similar to the following:

  OpenVMS VAX Version V7.1 Major version id = 1 Minor version id = 0 
 
System time is: 22-NOV-1996 15:54:08.30 
 
   .
   .
   .
 
* Is that correct? (Y/N/?) 
If ... Then ...
You want to redisplay the time Type a question mark (?) and press Return.
The system time displayed by the procedure is correct Type Yes and press Return.
The system time displayed by the procedure is incorrect Type No and press Return.

The procedure prompts you to enter the correct date and time.

7.5 Upgrade Phase 2

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

Continuing with OpenVMS VAX V7.1 Upgrade Procedure. 
 
         Upgrade Phase 2         22-NOV-1996 15:55:42.57 
 
********************************************************* 
%SYSTEM-W-TZGMT, your local timezone has defaulted to GMT 
%SYSTEM-I-SETTZ, to set your local timezone use: 
 
     $ @SYS$MANAGER:UTC$TIME_SETUP.COM 
 
********************************************************* 
On MIN or UPGRADE system startup - CLUE is not run. 
       . 
       . 
       . 
 
      22-NOV-1996 15:57:00.59 
 

You can ignore the time zone message. The UTC$TIME_SETUP.COM procedure runs during the final phase of the upgrade procedure.

7.5.1 What the Procedure Does

During Phase 2, the upgrade procedure restores the rest of the library (C), optional (D), Help Message (E), and OpenVMS Management Station software (F) save sets and DECwindows support files if you elected to install them.

7.5.1.1 Mounting Additional Tape Cartridge and 9-Track Open Reel Magnetic Tape Volumes

If your distribution kit is on TK50 tape cartidges or 9-track open reel magnetic tapes, you may be asked to mount additional volumes of the kit. In such a case, your system will display a message similar to the following:

Please mount volume  <x> of the OpenVMS kit on  <device> 

where: <x> is the volume number and <device> is the cartridge tape drive or open reel tape drive.

After you respond to the prompt, the system displays one of the following messages:

To respond to either message, do the following:

  1. Unload the volume currently in the drive.
  2. Examine the remaining volumes and select the one with the label that matches the label specified in the prompt.
  3. Load the volume and make the drive ready.
  4. Answer YES to the question.

For information on which save sets are located on which tape volumes, Section 1.4.1 and Section 1.4.2.

7.6 Upgrade Phase 3

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

Continuing with OpenVMS VAX V7.1 Upgrade Procedure 
 
     Upgrade Phase 3                   22-NOV-1996 16:45:18.35 

7.6.1 What the Procedure Does

During Phase 3, the upgrade procedure does the following:

  1. Merges the OpenVMS VAX distributed files that are commonly edited by system managers with new OpenVMS VAX files.
  2. Merges all the miscellaneous user files in the old system directories into a new set of system directories, temporarily called SYSF.SYSEXE, SYSF.SYSMGR, SYSF.SYSLIB, and so on.
  3. Removes the directory entries for page, swap, dump, and authorization files from the old directory tree.
  4. Deletes all the remaining accounting data files, operator logs, and all files in the SYSERR directory.
  5. Merges the old and new versions of the following files: HELP, DCLTABLES, IMAGELIB.OLB, and STARLET.OLB.
  6. Moves all remaining files from the old directory tree [VMS$COMMON] to the new directory tree.
  7. Deletes the old directory tree [VMS$COMMON].

7.7 Upgrade Phase 4

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

Continuing with OpenVMS VAX V7.1 Upgrade Procedure. 
 
     Upgrade Phase 4            22-NOV-1996 17:14:34.12 

7.7.1 What the Procedure Does

During Phase 4, the upgrade procedure does the following:

  1. Corrects back pointers for system directories.
  2. Shuts down the system.
  3. Reboots the system, or requires that you manually reboot the system.

7.7.2 What You Do

If the procedure requires that you manually reboot the system from the original system root (usually SYS0), do the following:

  1. If you are upgrading a VAX 8530, 8550, 8810, or 8820-N computer, do the following:
    1. Restore the original copies of DEFBOO and dddGEN to boot from the original root directory.
    2. In the preupgrade procedure (Chapter 5), you made copies of the boot command procedures, DEFBOO.SAV and dddGEN.SAV. To restore the original names to these files, enter the following commands and press the Return key after each one:
      >>> EXIT
      $ COPY DEFBOO.SAV DEFBOO.COM
      $ COPY dddGEN.SAV dddGEN.COM
      
  2. For most MicroVAX and VAXstation computers, use the BOOT command in the following format and substitute the device name of the system disk for ddcu:
    >>> B ddcu
    

    If the system fails to boot, you can boot into SYSBOOT by entering the following:
    >>> B/1 ddcu
    

For more information about booting your system, see the upgrade and installation supplement for your VAX computer.

When the system reboots, the procedure displays a message similar to the following:

OpenVMS VAX Version 7.1 Major version id = 1 Minor version id = 0 

After the system reboots, the procedure continues with upgrade Phase 5. Do not move the system disk to a different drive. The system disk must remain in the same drive for the procedure to continue with Phase 5.

7.8 Upgrade Phase 5

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

Continuing with OpenVMS VAX V7.1 Upgrade Procedure. 
 
     Upgrade Phase 5            22-NOV-1996 17:45:24.03 

During Phase 5, the upgrade procedure does the following:

  1. Deletes the temporary [SYSF] directory tree.
  2. Cleans up files used only during the upgrade procedure.
  3. Converts all VAXVMSSYS.PAR parameter files found in system roots to Version 7.1 format.
  4. Displays messages listing tasks that you can perform after the upgrade procedure is completed. These tasks are described in Chapter 8.

7.9 Upgrade Phase 6

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

   Continuing with OpenVMS VAX V7.1 Upgrade Procedure. 
 
        Upgrade Phase 6       22-NOV-1996 17:45:25.03 
 
 
   Configuring all devices on the system... 

7.9.1 Restoring System Files

The procedure restores SYS$SPECIFIC and SYS$COMMON versions of the following system files that were renamed with .COM_OLD_SPECIFIC and .DAT_OLD_SPECIFIC extensions during Phase 1:

You might not have site-specific versions of all of these files. The procedure will display a message listing each file as it is restored.

You might receive any of the following network messages, which can be ignored:

   %NCP-W-UNRCMP, Unrecognized component, Object 

Or:

   %NCP-I-SUCCESS, Success 
   Object = X$X0 
   %NML-I-RECDELET, Database entry deleted 

7.9.2 Registering Licenses

The upgrade procedure also gives you the opportunity to register any additional licenses.

The procedure 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? (Y/N): 

You do not have to reregister your OpenVMS VAX license or licenses for the following system integrated products:

If you want to register a new Product Authorization Key, type Yes and press the Return key. Otherwise, type No and press Return.

For more information on registering licenses, see the description of VMSLICENSE.COM in Appendix B and in the OpenVMS License Management Utility Manual.

7.9.3 Updating Time Zone Information

At this point in the upgrade, the procedure checks for the presence of time zone and time differential factor (TDF) files on your system. If it does not find one or the other of these files, the procedure prompts you for information to be used for providing local time zone support.


Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]

[HR]

  6487P007.HTM
  OSSG Documentation
   9-DEC-1996 10:54:01.78

Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

Legal