Updated: 11 December 1998 |
OpenVMS VAX
Version 7.2 Upgrade and
Installation Manual
Previous | Contents | Index |
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,
refer to OpenVMS Cluster Systems.) All nodes that are booted at this time will
run AUTOGEN and reboot.
7.8.7 Executing STARTUP
After the system reboots, the procedure displays the following message:
*********************************************************** OpenVMS VAX V7.2 You have SUCCESSFULLY installed the OpenVMS VAX 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 indicating that your OpenVMS VAX operating system is running. For example:
%STDRV-I-STARTUP, OpenVMS startup begun at 13-NOV-1998 13:36:40.32 . . . %SET-I-INTSET, login interactive limit=64, current interactive value = 0 SYSTEM job terminated at 13-NOV-1998 13:39:28.31 Accounting information: Buffered I/O count: 1845 Peak working set size: 970 Direct I/O count: 677 Peak virtual size: 5165 Page faults: 8906 Mounted volumes: 0 Charged CPU time 0 00:00:53.34 Elapsed time 0 00:02:58.77 |
At this time, you can log in to the SYSTEM account (so you can perform
postupgrade tasks), as described in the following sections.
7.8.8 Logging in to the SYSTEM Account by Means of a Character Cell Terminal
Log in to a character cell terminal by entering the user name SYSTEM followed by the password. The display is similar to the following:
Welcome to OpenVMS VAX V7.2 Username: SYSTEM Password: . . . Welcome to OpenVMS VAX Version V7.2 |
(If you forget your password, follow the instructions in the
OpenVMS System Manager's Manual: Essentials to perform an emergency startup.)
7.8.9 Logging in to the SYSTEM Account by Means of a Workstation
If you installed the DECwindows Motif for OpenVMS VAX software on your workstation, do the following after the login window displays on your screen:
After you have successfully upgraded the OpenVMS VAX operating system and logged in to the SYSTEM account, you must perform certain postupgrade tasks before you can use the system. For complete information, go to Chapter 8.
After you upgrade the OpenVMS VAX operating system, you need to perform several important tasks before you can use the system. These tasks, described in the order in which you perform them, are as follows:
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.
8.1 Verifying System Time
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 TIME |
The 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=13-NOV-1998:10:19:25 |
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.
8.3 Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DAT
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 the upgrade procedure, these files were updated.
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.
8.4 Examining AGEN$PARAMS.REPORT
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 Return:
$ 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$OpenVMS072:[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, or
dump files, see Section 8.5.
8.5 Checking the Size of System Files
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, refer to the OpenVMS System Manager's Manual: Essentials.
8.6 Examining Your Command Procedures
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.
8.7 Changing MODPARAMS.DAT
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 value for the EXPECTED_VOTES parameter 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.
8.8 Updating Your Console Media
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.2
VMB.EXE onto your system's console media. The procedure differs
depending on the VAX series computer you have. Follow the instructions
in the section that applies to your VAX computer.
8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers
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: 13-NOV-1998 18:40 VMB.EXE 80 13-NOV-1998 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, and 8650 computers. The device name for the VAX
9000 console hard disk is CSA1.
8.10 Decompressing the System Libraries
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 Return:
$ 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.COM |
The following information is displayed:
OpenVMS Library Decompression Utility 1 HELPLIB.HLB 14 NCPHELP.HLB 27 PHONEHELP.HLB 2 STARLET.OLB 15 SDA.HLB 28 LIB.MLB 3 ACLEDT.HLB 16 SHWCLHELP.HLB 29 STARLET.MLB 4 ANLRMSHLP.HLB 17 SYSGEN.HLB 30 STARLETSD.TLB 5 DBG$HELP.HLB 18 ANALAUDIT$HELP.HLB 31 SYS$STARLET_C.TLB 6 DBG$UIHELP.HLB 19 SYSMANHELP.HLB 32 ERFLIB.TLB 7 DISKQUOTA.HLB 20 TFF$TFUHELP.HLB 33 SYS$LIB_C.TLB 8 EDFHLP.HLB 21 EXCHNGHLP.HLB 34 VAXCCURSE.OLB 9 INSTALHLP.HLB 22 TPUHELP.HLB 35 VAXCRTL.OLB 10 LATCP$HELP.HLB 23 EVE$HELP.HLB 36 VAXCRTLD.OLB 11 MAILHELP.HLB 24 EVE$KEYHELP.HLB 37 VAXCRTLT.OLB 12 MNRHELP.HLB 25 UAFHELP.HLB 38 IMAGELIB.OLB 13 EDTHELP.HLB 26 TECO.HLB 39 VMS$VOLATILE_PRIVATE_INTERFACES.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.
Previous | Next | Contents | Index |
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
6521PRO_011.HTML
|