Document revision date: 19 July 1999

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

Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with the OpenVMS operating system kit. DIGITAL strongly 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 Digital's MCS 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. If you plan to install DECnet Phase IV, do NOT select DECnet-Plus. * Do you want to install DECnet-Plus. (Y/N) y

If you are upgrading from OpenVMS VAX Version 7.1 and are changing DECnet products, the procedure prompts you to remove the version of DECnet installed on your system. You must remove this DECnet product because both DECnet-Plus and DECnet Phase IV products cannot run concurrently on your system.

The following message shows an upgrade from DECnet Phase IV to DECnet-Plus:

* Do you want to install DECnet-Plus? (Y/N) y DECnet Phase IV is intalled on your system. Before installing DECnet-Plus, you must remove DECnet Phase IV. *Do you want to remove DECnet Phase IV? (Y/N) y The following product has been selected: DEC VAXVMS DECNET_PHASE_IV V7.1 Layered Product Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...100% The following product has been removed: DEC VAXVMS DECNET_PHASE_IV V7.1 Layered Product Space remaining on system disk: 1458710 blocks

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

The following options will be provided: OpenVMS library OpenVMS optional OpenVMS Help Message OpenVMS Management Station Software -- PC files DECwindows base support DECwindows workstation support with: - 75 dots per inch video fonts - 100 dots per inch video fonts DECnet-Plus Space remaining on system disk: 1458710 blocks * Is this correct? (Y/N) y

If you answer Yes to this prompt, the procedure restores the OpenVMS required save set (VMS072.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. For example:

During Phase 2 you will be required to provide input if: o Your OpenVMS kit is multivolume o You chose an alternate device o You chose DECwindows options Now copying over the OpenVMS and DECwindows V7.2 REQUIRED save set %BACKUP-I-STARTVERIFY, starting verification pass Purging pagefile, swapfile, dump file, and authorization files back to one version. Entering old page, swap, dump, errlog, and authorization files in new directory tree. Setting the startup command file for the next phase of the upgrade. Renaming SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT to SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT_OLD Renaming SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT_NEW to SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT Renaming SYS$SYSDEVICE:[SYS0.SYSEXE]VAXVMSSYS.PAR_NEW to SYS$SYSDEVICE:[SYS0.SYSEXE]VAXVMSSYS.PAR

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

System shutting down to boot the new kernel system. (Please ignore any error messages during the SHUTDOWN procedure.) The distribution kit must remain on DKB200: and the system disk must remain on VXPCSI$DKB100: in order to proceed to the next phase of the upgrade. The sysgen parameters are set to boot any system. Do not change them during the reboot or the upgrade may fail to execute properly! Once the shutdown is complete, stop the system using the HALT button on the computer control panel, or the BREAK key on the console terminal if your system has no HALT button. Reboot the system with the following command, replacing "ddcu" with the name of the disk drive that contains the system disk. B/F0000000 ddcu The upgrade is set up to continue once the system reboots. If, for some reason, the kernel V7.2 system should fail to boot, you can boot into SYSBOOT by entering: B/F0000001 ddcu * Press RETURN to shut down system:

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

7.3.11 Rebooting 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, refer to the upgrade and installation supplement for your VAX computer.

7.3.12 Verifying System Time

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

OpenVMS (TM) VAX Version V7.2 Major version id = 1 Minor version id = 0 System time is: 13-NOV-1998 10:46:26.34 Enter Yes to the next question to leave the system time unchanged (the system clock continues to run unaffected) Enter No to set a new system time Enter ? to redisplay the time * Is this correct? (Y/N/?)

Enter your response and press Return.

7.4 Upgrade Phase 2

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

Continuing with OpenVMS VAX V7.2 Upgrade Procedure. Upgrade Phase 2 13-NOV-1998 10:46:31.86 ********************************************************* %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. . . . 13-NOV-1998 10:53:26.27

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

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.4.1 Mounting Additional Magnetic Tape and Tape Cartridge Volumes

If your distribution kit is contained on open reel magnetic tapes or TK50 CompacTape cartidges, you may be asked to mount the second volume of the kit. If you need to mount the second volume, your system will display a message similar to the following:

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

where: <device> is the magnetic tape or tape cartridge drive.

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

• For a 9-track open reel magnetic tape, the message is similar to the following:

  * Is the volume labeled OVMS VAX V7.2 BIN MT9 2/2 ready to be mounted?

• For a TK50 CompacTape cartridge, the message is similar to the following:

  * Is the volume labeled OVMS VAX V7.2 BIN TK50 2/2 ready to be mounted?

To respond to either message, do the following:

1. Unload the volume currently in the drive.
2. Select the volume 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, refer to Section 1.3.2.

7.5 Upgrade Phase 3

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

Continuing with OpenVMS VAX V7.2 Upgrade Procedure. Upgrade Phase 3 13-NOV-1998 11:05:47.14

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].

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

Continuing with OpenVMS VAX V7.2 Upgrade Procedure. Upgrade Phase 4 13-NOV-1998 11:21:40.65

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.

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 Return 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, refer to the upgrade and installation supplement for your VAX computer.

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

OpenVMS (TM) VAX Version V7.2 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.7 Upgrade Phase 5

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

Continuing with OpenVMS VAX V7.2 Upgrade Procedure. Upgrade Phase 5 13-NOV-1998 11:36:36.95

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. Registers the OpenVMS VAX V7.2 operating system in the POLYCENTER Software Installation product database.
4. Installs DECnet Phase IV V7.2. Earlier in the procedure you were asked whether you wanted to install the DECnet Phase IV product. If you answered YES, the procedure now installs it.
5. Converts all VAXVMSSYS.PAR parameter files found in system roots to Version 7.2 format.
6. Displays messages listing tasks that you can perform after the upgrade procedure is completed. These tasks are described in Chapter 8.

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

Continuing with OpenVMS VAX V7.2 Upgrade Procedure. Upgrade Phase 6 13-NOV-1998 11:38:46.83 Configuring all devices on the system ...

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

• SYSTARTUP_VMS.COM
• SYCONFIG.COM
• SYPAGSWPFILES.COM
• SYSECURITY.COM
• SYSHUTDWN.COM
• SYLOGIN.COM
• LOGIN.COM
• SYLOGICALS.COM
• AGEN$NEW_SATELLITE_DEFAULTS.DAT
• AGEN$NEW_NODE_DEFAULTS.DAT
• LAT$SYSTARTUP.COM
• TFF$STARTUP.COM

You might not have site-specific versions of all of these files. The procedure displays 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.8.2 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.

For local time zone support to work correctly, the upgrade 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 those menus. The first menu is the main time zone menu. Select the time zone that best describes your location. If you do not select a time zone, the default is Greenwich Mean Time (GMT).

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 your local 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 for measuring time of day. You can choose from the following options:

• Exit the time zone procedure without setting a TDF
• Set a TDF
• Display the TDF for your local time zone

For more information about TDF and local time zone support, refer to the OpenVMS System Manager's Manual.

7.8.3 Installing DECnet-Plus

Earlier in the procedure, you were asked whether you wanted to install the DECnet-Plus product. If you answered Yes, the procedure now installs it.

Note that if DECnet-Plus is already installed on your system and if the installed version is the same as or higher than the version supplied with OpenVMS VAX Version 7.2, then DECnet-Plus is not reinstalled, and the procedure displays the following message:

DECnet-Plus is already installed.

If DECnet-Plus is not already installed on your system, the procedure displays a message similar to the following and prompts you for information it needs to install the DECnet-Plus product:

DECnet-Plus will now be installed. Media containing the DECnet-Plus kit must be available. If you are installing OpenVMS from an InfoServer (DAD1) or local CD-ROM, there is a DECnet-Plus kit on the CD-ROM. If you are installing from a cartridge tape (TK50) or from an open reel tape, you should have a DECnet-Plus kit on cartridge tape or open reel tape. An appropriate DECnet-Plus kit may also be available on the Consolidated Distribution CD-ROM, or you may have a separate DECnet-Plus kit. NOTE: You may choose any available media for the DECnet-Plus kit. It is NOT NECESSARY to use the same type of media that contained the OpenVMS kit. * Enter name of drive holding the DECnet-Plus kit: dkb200 * Is DKB200: ready to be mounted? [N] y The following product has been selected: DEC VAXVMS DECNET_OSI V7.2 Layered Product 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 VAXVMS DECNET_OSI V7.2: DECnet-Plus V7.2 for OpenVMS VAX Copyright (c) Digital Equipment Corporation 1999. All rights reserved. Digital Equipment Corporation This product requires one of two PAKs: DVNETEND or DVNETRTG. Do you want the defaults for all options? [YES] Do you want to review the options? [NO] y VAXVMS DECNET_OSI V7.2: DECnet-Plus V7.2 for OpenVMS VAX DEC VAXVMS VMS V7.2 [Installed] VAX P.S.I. or P.S.I. Access software: NO VAX Wide Area Device Drivers: NO DECdns Server software: NO DECdts Server software: NO Are you satisfied with these options? [YES] Execution phase starting ... The following product will be installed: DEC VAXVMS DECNET_OSI V7.2 Layered Product Portion done: 0%...10%...20%...30%...40%...80%...90%...100% The following product has been installed: DEC VAXVMS DECNET_OSI V7.2 Layered Product

7.8.4 Running AUTOGEN

Next, the procedure displays the following message and runs AUTOGEN:

Running AUTOGEN to compute the new SYSTEM parameters ...

If AUTOGEN encounters any problems, it displays the following message:

%AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review the information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT.

If AUTOGEN displays this message, be sure to check AGEN$PARAMS.REPORT as one of your postupgrade tasks. This task is described in Section 8.4.

7.8.5 Shutting Down the System

After AUTOGEN finishes, the procedure displays a sequence of shutdown messages that begins like this:

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 upgrade will be complete. SHUTDOWN -- Perform an Orderly System Shutdown on node VXPCSI . . .

The system shuts down and will reboot automatically if your system is set up to do so. If the system does not reboot automatically, reboot it manually. For more information about booting your system, refer to the upgrade and installation supplement for your VAX computer.

	privacy and legal statement
6521PRO_010.HTML