Document revision date: 19 July 1999 | |
Previous | Contents | Index |
If you chose to install DECnet-Plus, the procedure will now install it. The procedure displays messages similar to the following and prompts you for information it needs to install DECnet-Plus.
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 is contained in the OpenVMS kit. If you do not have a DECnet-Plus kit available, or if you have decided NOT to install/upgrade DECnet-Plus, you can bypass the DECnet-Plus installation by entering "EXIT" for the "name of drive holding the DECnet-Plus 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 © 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] yes DEC 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 |
To complete the installation procedure, continue to the next section,
Section 3.12.
3.12 Running AUTOGEN
The remaining portion of the installation procedure runs AUTOGEN to evaluate your hardware configuration and estimate typical work loads. AUTOGEN then sets system parameters, the sizes of page, swap, and dump files, and the contents of VMSIMAGES.DAT. When AUTOGEN finishes and you reboot your system, the installation procedure is complete.
The installation procedure displays messages similar to the following:
Running AUTOGEN to compute the new SYSTEM parameters ... %AUTOGEN-I-BEGIN, GETDATA phase is beginning. %AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created. You may wish to purge this file. %AUTOGEN-I-END, GETDATA phase has successfully completed. . . . %AUTOGEN-I-BEGIN, REBOOT phase is beginning. |
If you need to create or modify the size of the pagefile or swapfile,
use the SYSMAN utility. For more information, refer to the OpenVMS System Manager's Manual: Essentials.
3.13 Rebooting the System
After AUTOGEN finishes, the system shuts down, displaying messages similar to the following:
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 |
If the system does not reboot automatically, reboot the system manually.
For example, if you have a VAX--11/780 computer and the system disk is on an RA60 disk drive with a unit number of 1, enter the following command and press Return:
>>> B DUA1 |
After the system reboots, a message similar to the following is displayed:
***************************************************************** 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. ***************************************************************** |
For more information about booting, refer to the upgrade and installation supplement for your VAX computer, then return to this manual.
If you did not register your OpenVMS VAX license as described in Section 3.9, the procedure displays warning messages that the OpenVMS license must be registered. Be sure to register this license when the installation procedure finishes. For more information, see Appendix B and refer to the OpenVMS License Management Utility Manual. |
The system next displays informational messages and accounting information indicating that your OpenVMS VAX operating system is running. For example:
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at 13-NOV-1998 13:58:16.1 Accounting information: Buffered I/O count: 859 Peak working set size: 565 Direct I/O count: 478 Peak virtual size: 2570 Page faults: 5003 Mounted volumes: 0 Charged CPU time: 0 00:00:19.33 Elapsed time: 0 00:00:41.24 |
At this time, you can log in to the SYSTEM account (so you can perform
postinstallation tasks), as described in the following sections.
3.14 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.)
3.15 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 installed the OpenVMS VAX operating system and logged in to the SYSTEM account, you must perform certain postinstallation tasks before you can use the system. For complete information, go to Chapter 4.
After you have installed the OpenVMS VAX operating system, you need to perform several important tasks to prepare the system for operation. This chapter describes the following postinstallation tasks in the order you perform them:
If you are an experienced system manager, you can use the checklist at the end of the chapter to complete the necessary postinstallation tasks.
If you are a system manager with less OpenVMS VAX experience, you
should read the entire chapter and then use the checklist to make sure
you have completed all the postinstallation tasks.
4.1 Verifying System Time
During the installation, the procedure prompted you to enter the date and time. Now that you have installed 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 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:18:35:30 |
4.2 Registering Your Licenses
The installation procedure gave you the opportunity to register any
software product licenses. If you did not register your OpenVMS VAX
license at that time, you must do so before you can use the OpenVMS VAX
operating system. You must register the licenses for any of the
following System Integrated Products you have purchased:
You must also register the licenses for any of the following DECnet products you have purchased:
For step-by-step instructions about registering licenses, refer to the
OpenVMS License Management Utility Manual and see Appendix B in this manual.
4.3 Backing Up Your System Disk
After you install the operating system, protect your work by making a backup copy of the system disk in case you have any problems during customization.
Compaq recommends that you perform the following operations:
In addition to backing up the system disk now before you customize it, you should back up your system disk again after you successfully complete your customization tasks.
For complete information about backup operations, refer to the upgrade
and installation supplement for your VAX computer.
4.4 Customizing the System
You can customize the system to meet your site-specific needs. In addition, if your VAX computer is part of a VAXcluster environment, you must prepare the cluster environment and configure the cluster.
For instructions on customizing the system, read the following documentation:
In local area and mixed-interconnect VAXcluster systems, DECnet software provides both system management functions and cluster communications, such as remote booting operations. DECnet software ensures that system managers can access all VAXcluster computers from a single terminal.
You can use the DECnet-Plus or DECnet Phase IV software included on the
OpenVMS VAX Version 7.2 kit. Both of these products require that you
run a configuration procedure to configure the network. If you choose
to run the DECnet Phase IV product, you must also edit your system
startup file as described in Section 4.5.2.
4.5.1 Configuring Your System
After you have registered your DECnet license, execute one of the following interactive configuration procedures:
If you plan to run DECnet-Plus, you do not need to edit this file because DECnet will start automatically.
If you plan to run DECnet Phase IV, after you start the queue manager, edit the commands in SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM that pertain to networking, so that DECnet starts automatically when you boot the system. Choose one of the following commands to start the network and remove the comment delimiter (!) from that command:
$! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET $! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN SUBMIT SYS$MANAGER:STARTNET.COM |
Both of the previous commands perform the same task. However, the first command executes STARTNET.COM and delays further processing until the procedure is completed; the second submits STARTNET.COM to a batch queue and continues executing SYSTARTUP_VMS.COM. If you plan to run both DECnet Phase IV and DECwindows Motif for OpenVMS VAX, you must also edit SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM to add a comment delimiter (!) immediately following the dollar-sign ($) in the DEFINE DECW$IGNORE_DECNET command as follows:
$! DEFINE DECW$IGNORE_DECNET TRUE |
If you are not going to start DECnet Phase IV or have not yet started
it, this command tells DECwindows not to wait for DECnet.
4.6 Testing the System with UETP
The User Environment Test Package (UETP) is a software package designed to test whether the OpenVMS VAX operating system is installed correctly. As part of the postinstallation procedure, Compaq recommends that you run UETP to verify the installation.
Note that UETP needs at least 1200 free blocks on the system disk and is available only if you installed the optional save set VMS072.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 using UETP, refer to the OpenVMS System Manager's Manual.
4.7 Decompressing the System Libraries
Decompressing the system libraries gives the system faster access to
them. You can decompress all the system libraries or just some of them.
You use the LIBDECOMP.COM procedure to decompress the libraries.
4.7.1 Determining Disk Space
To find out how much disk space you have, enter the following command and press Return:
$ SHOW DEVICE SYS$SYSDEVICE |
The additional amount of disk space required to decompress all the system libraries is about 13,500 blocks.
Table 4-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 |
You can use the LIBDECOMP.COM procedure to decompress libraries in three ways:
The following sections describe each method.
Before you use the LIBDECOMP.COM procedure, be sure you are logged in to the SYSTEM account. |
If you want to decompress libraries by responding to prompts from the LIBDECOMP.COM procedure, do the following:
$ @SYS$UPDATE:LIBDECOMP.COM |
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): |
Previous | Next | Contents | Index |
privacy and legal statement | ||
6521PRO_005.HTML |