![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
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:
For more information about TDF and local time zone support, see the OpenVMS System Manager's Manual.
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 (formerly DECnet/OSI) 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.1, 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. In this example, the kit is being installed from an InfoServer device, DAD1.
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 cartidge 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: DAD1:
* Enter the InfoServer service name: OTHER_PRODS
* Enter the InfoServer work group number [0]:
The following product has been selected:
DEC VAXVMS DECNET_PLUS V7.1
*** DEC VAXVMS DECNET_PLUS V7.1: DECnet-Plus V7.1 N3_H for OpenVMS VAX
Copyright ) Digital Equipment Corporation 1996. All rights reserved.
Digital Equipment Corporation
This product requires one of two PAKs: DVNETEND or DVNETRTG.
Do you want all the default values for this product? [YES]
Do you want to view the values? [NO]
Execution phase starting ...
The following product will be installed:
DEC VAXVMS DECNET_PLUS V7.1
Portion done: 0%...10%...20%...30%...40%...80%...90%...100?
The following product has been installed:
DEC VAXVMS DECNET_PLUS V7.1
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.
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
.
.
.
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 on booting your system, see the upgrade
and installation supplement for your VAX computer.
If you are upgrading a standalone system, go to the next step.
If you are upgrading a VAXcluster system, the system might hang when you try to reboot the upgraded system disk. This is because the total cluster value is less than the cluster quorum value. To remedy this situation, boot voting members that run from the system disk you just upgraded. (For more information about quorum values and voting members, see OpenVMS Cluster Systems.) All nodes that are booted at this time will run AUTOGEN and reboot.
After the system reboots, the procedure displays the following message:
*********************************************************** OpenVMS VAX V7.1 You have SUCCESSFULLY installed the OpenVMS operating system. The system is now executing the STARTUP procedure. Please wait for the completion of STARTUP before logging in to the system. ***********************************************************
Finally, the procedure displays informational messages as well as accounting information. For example:
%STDRV-I-STARTUP, OpenVMS startup begun at 22-NOV-1996 18:27:30 . . . %SET-I-INTSET, login interactive limit=64, current interactive value = 0 SYSTEM job terminated at 22-NOV-1996 18:30:00.00 Accounting information: Buffered I/O count: 133 Peak working set size: 401 Direct I/O count: 12 Peak virtual size: 2379 Page faults: 325 Mounted volumes: 0 Charged CPU time 0 00:00:55.23 Elapsed time 0 00:01:31.24
At this point the OpenVMS VAX operating system is running.
Press the Return key. The system asks for the user name and password. Log in to the SYSTEM account so that you can perform the postupgrade procedures described in Chapter 8.
Welcome to OpenVMS VAX V7.1 Username: SYSTEM Password: . . .
If you forget the password, follow the instructions for performing an emergency startup in the OpenVMS System Manager's Manual: Essentials.
Proceed to Chapter 8 to perform the required postupgrade tasks.
After you upgrade the OpenVMS VAX operating system, you need to perform several important tasks before you can use the system. This chapter describes the following tasks in the order you perform them:
If you are an experienced system manager, you can use the checklist at the end of this chapter to complete the necessary postupgrade tasks.
If you are a less-experienced system manager, you should read the entire chapter and then use the checklist to make sure you have completed all the postupgrade tasks.
During the upgrade, the procedure displayed the system time and gave you the opportunity to enter the correct time if the displayed time was incorrect.
Now that you have upgraded your system, verify that the system time is correct by entering the following command:
$ SHOW TIMEThe system displays the date and time.
If the time displayed by your system is not correct, reset it by entering the command SET TIME using the following format:
SET TIME=dd-mmm-yyyy:hh:mm:ss
For example:
$ SET TIME=22-NOV-1996:18:35:30
After the upgrade completes, the queuing system on the upgraded nodes is enabled, and you must restore the preferred node list for the queue manager.
To restore the preferred node list, enter the following command from any node:
START/QUEUE/MANAGER/ON=(node1, node2 . . . noden)For node1, node2, and so forth, supply the names of the nodes---separated by commas---that you want to restore to the preferred node list.
If you permanently store the SYSUAF.DAT and VMS$AUDIT_SERVER.DAT files on the system disk, go to Section 8.4.
If you do not permanently store SYSUAF.DAT and VMS$AUDIT_SERVER.DAT on the system disk, you copied them to the system disk before you did the upgrade. During upgrade procedure, these files were updated.
Note
If you did a rolling upgrade, the shared version of SYSUAF.DAT was not updated.
To replace the updated files, copy the updated versions of SYSUAF.DAT and VMS$AUDIT_SERVER.DAT from the system disk to the directory where you usually keep them.
When AUTOGEN runs, it writes informational and, if necessary, warning messages to the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You can view the contents of this report file to examine these messages.
To display AGEN$PARAMS.REPORT on your screen, enter the following command and press the Return key:
$ TYPE SYS$SYSTEM:AGEN$PARAMS.REPORT
If the report includes a message similar to the following, you can modify the size of the PAGE, SWAP, or DUMP file:
******************
%AUTOGEN-W-DSKSPC, The disk on which DISK$OpenVMS071:[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 Section 8.5.
AUTOGEN sets the following files at sizes appropriate for your system:
For special workloads or configurations, you can specify different sizes for these files. Check the sizes of these files to be sure they meet your needs. Log in to the SYSTEM account and enter the following command:
$ @SYS$UPDATE:SWAPFILES
For more information, see the OpenVMS System Manager's Manual: Essentials.
The upgrade procedure places a new version of WELCOME.TXT on your system disk. If your system uses a site-specific version of this file, you must modify the new version of the file with your changes.
The upgrade procedure restores your site-specific version of the following files with *.COM_OLD_SPECIFIC extensions:
The upgrade procedure provides new templates for some of these files with the .TEMPLATE extension. The new templates can include features that are not in your site-specific files. Check the templates against your site-specific files and edit your files as necessary.
Remember, you do not need a START/QUEUE/MANAGER command in your startup file because the queue manager automatically starts up when you boot the system.
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. Modify the new file, if necessary, for your system.
If you are upgrading a VAXcluster, you must update the MODPARAMS.DAT file for each VAX computer that boots from the system disk. Make sure the EXPECTED_VOTES value is correct. The value is the sum of all VOTES in the cluster. For example, if there are five VAX computers in the cluster, and each has one VOTE, the value is five. As you reboot each VAX computer, AUTOGEN runs automatically. The cluster forms when you have booted enough computers to attain cluster quorum.
For more information, refer to the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems.
If your computer does not use console media, skip this section and go to Section 8.10.
If your computer uses console media, you must copy the Version 7.1 VMB.EXE onto your system's console media. The procedure for accomplishing this differs depending on the VAX series computer you have. Follow the instructions in the section that applies to your VAX computer.
If you upgraded a VAX 8530, 8550, 8810 (8700), or 8820-N (8800) computer, do the following:
$ SHOW DEVICE CSA Device Device Error Volume Name Status Count Label CSA0: (SYSTEM) Online 0 CSA1: (SYSTEM) Online 0 CSA2: (SYSTEM) Online 0
%SYSTEM-W-NOSUCHDEV, no such device available
$ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT
$ INITIALIZE/STRUCTURE=1 device-name: volume-label
$ INITIALIZE/STRUCTURE=1 CSA1: V61CONSOLE
$ MOUNT/OVERRIDE=ID device-name: $ CREATE/DIRECTORY device-name:[TRANSFER] $ COPY SYS$SYSTEM:VMB.EXE device-name:[TRANSFER]
$ DISMOUNT device-name:
>>> EXIT
$ COPY DZu:[TRANSFER]VMB.EXE LB0:[CONSOLE]
$ RUN CONTROL
>>> SET TERMINAL PROGRAM
If you upgraded a VAX--11/730, 750, 780, 785 and VAX 8200, 8250, 8300, 8350, 8600, or 8650 computer, follow the instructions in this section.
The procedure does the following:
To update the console media, use the following procedure:
$ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT $ EXCHANGE DIRECTORY device-name:VMB.EXE Directory of RT-11 volume TINES$CSA1: 22-NOV-1996 18:40 VMB.EXE 80 22-NOV-1996 Total of 1 file, 80 blocks. Free space 43 blocks, largest 23.
$ @SYS$UPDATE:UPDATE_CONSOLE.COM
VAX 9000 computers use a special version of VMB.EXE named VMB9AQ.EXE. The upgrade procedure automatically copies a new version of this file to the console hard disk. However, if for some reason you need to update the console hard disk, use the UPDATE_CONSOLE.COM command procedure described for the VAX--11/730, 750, 780, 785 and VAX 8200, 8250, 8300, 8350, 8600, 8650 computers. The device name for the VAX 9000 console hard disk is CSA1.
Decompressing the system libraries gives the system faster access to the libraries. You can decompress all the system libraries or just some of them. Table 8-1 gives the approximate number of blocks consumed by each library after decompression.
| Library | Blocks | Library | Blocks |
|---|---|---|---|
| HELPLIB.HLB | 9108 | EDFHLP.HLB | 102 |
| STARLET.OLB | 8442 | TPUHELP.HLB | 1038 |
| VAXCCURSE.OLB | 102 | ACLEDT.HLB | 102 |
| VAXCRTL.OLB | 477 | INSTALHLP.HLB | 102 |
| VAXCRTLG.OLB | 102 | LATCP$HELP.HLB | 240 |
| DECCCURSE.OLB | 102 | MNRHELP.HLB | 102 |
| DECCRTL.OLB | 183 | PATCHHELP.HLB | 102 |
| DECCRTLG.OLB | 102 | PHONEHELP.HLB | 102 |
| ERFLIB.TLB | 105 | SDA.HLB | 111 |
| STARLETSD.TLB | 4800 | SHWCLHELP.HLB | 150 |
| MAILHELP.HLB | 273 | SYSGEN.HLB | 393 |
| EDTHELP.HLB | 231 | TECO.HLB | 102 |
| DBG$UIHELP.HLB | 408 | UAFHELP.HLB | 372 |
| DBG$HELP.HLB | 1986 | EVE$HELP.HLB | 1197 |
| EXCHNGHLP.HLB | 117 | EVE$KEYHELP.HLB | 147 |
| NCPHELP.HLB | 537 | STARLET.MLB | 2502 |
| ANLRMSHLP.HLB | 102 | LIB.MLB | 2229 |
| DISKQUOTA.HLB | 102 |
The additional amount of disk space required to decompress all system libraries is about 13,500 blocks. To find out how much disk space you have, enter the following command and press the Return key:
$ SHOW DEVICE SYS$SYSDEVICE
You execute the LIBDECOMP.COM command procedure to decompress the system libraries. To run LIBDECOMP, log in to the SYSTEM account, enter the following command, and press Return:
$ @SYS$UPDATE:LIBDECOMP.COMThe following information is displayed:
OpenVMS Library Decompression Utility
1 HELPLIB.HLB 14 NCPHELP.HLB 27 PATCHHELP.HLB
2 STARLET.OLB 15 SDA.HLB 28 PHONEHELP.HLB
3 ACLEDT.HLB 16 SHWCLHELP.HLB 29 LIB.MLB
4 ANLRMSHLP.HLB 17 SYSGEN.HLB 30 STARLET.MLB
5 DBG$HELP.HLB 18 ANALAUDIT$HELP.HLB 31 STARLETSD.TLB
6 DBG$UIHELP.HLB 19 SYSMANHELP.HLB 32 ERFLIB.TLB
7 DISKQUOTA.HLB 20 TFF$TFUHELP.HLB 33 VAXCCURSE.OLB
8 EDFHLP.HLB 21 EXCHNGHLP.HLB 34 VAXCRTL.OLB
9 INSTALHLP.HLB 22 TPUHELP.HLB 35 VAXCRTLG.OLB
10 LATCP$HELP.HLB 23 EVE$HELP.HLB 36 IMAGELIB.OLB
11 MAILHELP.HLB 24 EVE$KEYHELP.HLB 37 DECCCURSE.OLB
12 MNRHELP.HLB 25 UAFHELP.HLB 38 DECCRTL.OLB
13 EDTHELP.HLB 26 TECO.HLB 39 DECCRTLG.OLB
A ALL libraries to be decompressed
E EXIT this procedure
* Enter letter or number(s) of libraries to be decompressed
(Separate multiple entries with a comma):
Enter the appropriate letter or the numbers of the libraries you want
to decompress. To decompress all libraries, the process takes
approximately one half hour.
If you prefer, you can execute LIBDECOMP interactively or as a batch job. If you use either of these methods, you can decompress up to 8 libraries each time you execute LIBDECOMP by listing the names of the libraries you want to decompress as parameters on the command line. (You can decompress all the libraries by omitting the /PARAMETERS qualifier.) Be sure to separate the library names with commas and do not include the file extension. For example, to decompress the VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB libraries as a batch job, enter the following command:
$ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)- _$ SYS$UPDATE:LIBDECOMP
To decompress these same libraries interactively, enter the following command:
$ @SYS$UPDATE:LIBDECOMP VAXCRTL DISKQUOTA LIB
Note that, when you type the command for a batch job, you separate the library names with commas and enclose the list within parentheses. You do not use commas or parentheses on the interactive command line.
UETP, the user environment test package, is a software package that tests whether the OpenVMS VAX operating system is installed correctly. As part of the postupgrade procedure, you should run UETP to verify your upgrade.
Note that UETP needs at least 1200 free blocks on the system disk and is available only if you installed the optional save set VMS071.D. If you did not install the optional save set, you can add the UETP files to your system using VMSTAILOR. For information about using VMSTAILOR, see Chapter 10.
For complete information about UETP, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems.
This section describes how to increase the amount of free space on your system disk. You can gain free space by removing optional OpenVMS VAX files that you do not need from the system disk or by purging old versions of some system files.
To remove files you do not need from the system disk, use VMSTAILOR. For example, if you are not running DECnet for OpenVMS, you do not need the network support files. For complete information about using VMSTAILOR to remove files, see Chapter 10.
6487P008.HTM OSSG Documentation 9-DEC-1996 10:54:05.02
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.