![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
For example:
$ SET TIME=22-NOV-1996:18:35:30
4.3 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 also register the licenses for any of the
following System Integrated Products you have purchased:
For step-by-step instructions about registering licenses, see the
OpenVMS License Management Utility Manual and Appendix B of this manual, which provides
supplemental information.
4.4 Backing Up Your System Disk
Now that you have spent time installing the operating system, you should protect your work by making a backup copy of the system disk in case you have any problems while customizing it. Digital recommends that you perform the following operations:
You should back up your system disk again after you have customized it.
For complete information about these operations, see the upgrade and
installation supplement for your VAX computer.
4.5 Customizing the System
You can customize the system to meet the specific needs of your site. In addition, if your VAX computer is part of a VAXcluster environment, you must prepare the cluster environment and configure the cluster.
For instructions about customizing your system, refer to the following:
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 software included on the OpenVMS VAX Version 7.1 kit, or you can install the DECnet Phase IV layered product.
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.6.2.
4.6.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 your system is booted. 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.7 Testing the System with UETP Software
UETP software is a user environment test package that tests whether the OpenVMS VAX operating system is installed correctly. As part of the postinstallation procedure, you should run UETP to verify your 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 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.
4.8 Decompressing 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. 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 |
The additional amount of disk space required to decompress all the 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
To decompress the system libraries, you run LIBDECOMP.COM by logging in to the SYSTEM account, entering the following command, and pressing 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.
4.9 Removing or Adding OpenVMS Files
To remove unwanted OpenVMS VAX files from the system disk, use VMSTAILOR or DECW$TAILOR. For example, if you are not running DECnet software, use VMSTAILOR to remove the files associated with DECnet.
Note
You cannot use VMSTAILOR to remove files installed on an alternate device from save set VMS071.E.
For complete information about using VMSTAILOR and DECW$TAILOR to
remove optional OpenVMS VAX software, see Chapter 10.
4.10 Installing Layered Products
Back up your system disk and then use either the VMSINSTAL command procedure or the POLYCENTER Software Installation utility to install layered products on your system.
For additional information about installing layered products, see the
OpenVMS System Manager's Manual.
4.10.1 TCP/IP Services for OpenVMS
If you installed the Digital TCP/IP Services for OpenVMS software during the installation or if you choose to install it now as a layered product, note that you must also install the mandatory security update kit included with this release.
The Digital TCP/IP Kit and the mandatory Security Update Kit are available in the following directory on the OpenVMS VAX CD-ROM:
[TCPIP_VAX_041]
If you choose to install the Digital TCP/IP Services for OpenVMS
software, you must install both kits.
4.11 Backing Up the Customized System Disk
Now that you have spent time installing and customizing the operating
system, protect your work by making a standalone backup copy of the
system disk. For complete information about these operations, see the
upgrade and installation supplement for your VAX computer.
4.12 Running AUTOGEN
When you installed the OpenVMS VAX operating system, the procedure executed AUTOGEN to set the values of system parameters and the sizes of the page and swap files according to the system's workload.
In many cases, AUTOGEN can improve system performance by using dynamic
feedback information from the running system. As a postinstallation
task, you should run AUTOGEN again using the feedback mechanism to make
further adjustments to system parameters.
4.12.1 How AUTOGEN Works
When AUTOGEN runs, it uses the parameter values in SYS$SYSTEM:MODPARAMS.DAT. Note that hardcoded values in MODPARAMS.DAT affect AUTOGEN's calculations of the feedback parameters. For AUTOGEN to properly calculate minimum default values, you should replace the hardcoded values in MODPARAMS.DAT with MIN_ values. If you need to modify the parameter values calculated by AUTOGEN, you can use AUTOGEN to change the hardcoded values in MODPARAMS.DAT.
For information about using AUTOGEN, see the OpenVMS System Manager's Manual: Essentials.
4.12.2 When to Run AUTOGEN
After installing the operating system, run AUTOGEN again using the following procedure:
After you run AUTOGEN following the first 24 hours of system operation
(step 1), review the checklist in Section 4.13 to confirm that you
have completed all the tasks described in this chapter.
4.13 Postinstallation Checklist
Use the following checklist to make sure you perform all the necessary postinstallation tasks.
Before you begin an upgrade, you need to perform several important tasks to prepare the system. This chapter describes what you need to know and do to prepare for an upgrade, including:
If you are an experienced system manager, you can use the checklist at the end of this chapter to complete the necessary preupgrade tasks.
If you are system manager with limited OpenVMS VAX experience, you
should read the entire chapter and then use the checklist to make sure
you have completed all the preupgrade tasks.
5.2 Cautions and Restrictions
This section provides important information that you need to be aware
of before you upgrade your system. If you attempt to upgrade your
system without following these cautions and restrictions, the upgrade
could fail or your upgraded system might not perform as expected.
5.2.1 License Requirements
To upgrade to OpenVMS Version 7.1, you must have an appropriate license. Digital's software licenses grant the right to use the current version of a product or any previous version of the product at the time of purchase. If you have an OpenVMS license prior to Version 7.1 and are not covered by a Software Product Services agreement, which includes the right to use new versions (RTNV), you must purchase an Update License before upgrading to OpenVMS Version 7.1.
If you do not have an Update License, please contact your Digital
account representative who will assist you in obtaining the correct
Product Authorization Key (PAK) needed to access the OpenVMS operating
system.
5.2.2 DECset Version 11 Debugger
If you have the DECset Version 11 layered product installed on your system, you must remove the @DEBUG$STARTUP.COM command from the system startup procedure. The debugger shipped with OpenVMS VAX Version 7.1 is a superset of the debugger that was shipped with the DECset Version 11 software. Removing the @DEBUG$STARTUP.COM command will cause the debugger shipped with OpenVMS VAX Version 7.1 to be the default system debugger.
To remove the @DEBUG$STARTUP.COM command before you upgrade the operating system software, perform the following steps:
$ @DEBUG$STARTUP
If you do not remove this command before you upgrade the operating system software, you must remove it after the upgrade, and you must deassign the logicals that were defined by DEBUG$STARTUP.COM by performing the following steps:
$ DEASSIGN/SYSTEM DEBUG $ DEASSIGN/SYSTEM DEBUGSHR $ DEASSIGN/SYSTEM DEBUGUISHR $ DEASSIGN/SYSTEM DBGTBKMSG $ DEASSIGN/SYSTEM DBG$HELP $ DEASSIGN/SYSTEM DBG$UIHELP $ DEASSIGN/SYSTEM DEBUGAPPCLASS $ DEASSIGN/SYSTEM VMSDEBUGUIL
$ @DEBUG$STARTUPDelete the command and any parameters. (The command might have an optional parameter of either VMS or DECSET.)
The Version 7.1 upgrade procedure provides new files and directories in
the directory [VMS$COMMON...]. If you had any special protections and
access control lists (ACLs) before the upgrade, you need to reapply
them to reestablish the security environment you had previously
established. For more information on creating and maintaining a secure
environment, see the OpenVMS Guide to System Security.
5.2.4 Operator and Accounting Logs
The upgrade procedure deletes all the operator and accounting logs. To
save these files, move them to a user directory before you start the
upgrade.
5.2.5 Special Testing and Debugging Files
Before you perform an upgrade, remove or rename any special testing or debugging files that you might have in any of the SYS$SPECIFIC: or SYS$SYSROOT: directories. Files in these directories are used in place of the files in SYS$COMMON: directories.
As a minimum, you should check the following directories:
SYS$SYSROOT:[SYSEXE] SYS$SYSROOT:[SYS$LDR]Because the upgrade procedure affects the SYS$COMMON: directories and does not check or alter the contents of the SYS$SPECIFIC: or SYS$SYSROOT: directories, any testing or debugging files that you have in these directories remain there unchanged until you remove or rename them. If you do not remove or rename these files, your system might behave in an unpredictable manner.
The following cautions apply when you are upgrading a cluster system:
If you move the OpenVMS VAX save sets from the distribution media to the system disk or some other disk before beginning the upgrade, the save sets must be in the [000000] directory of the disk, or the upgrade will fail.
Do not attempt to use VMSINSTAL with OPTION G to transfer OpenVMS VAX
save sets to another media type; doing so will produce an unusable
system. Instead, you can use the DCL command COPY to transfer save sets
to another media type.
5.2.8 System Disk Cautions
The following cautions apply to the system disk:
If you use your AUTOGEN feedback data, you should save this information
before rebooting the system with minimum startup to begin the upgrade.
For more information, see Section 5.4.
5.2.10 OpenVMS Version Requirements
Before you can upgrade to OpenVMS VAX Version 7.1, your system must be running at least Version 6.1 of the OpenVMS operating system. For example, you can upgrade a system disk to Version 7.1 of the OpenVMS VAX operating system from any of the following versions (or related hardware releases):
If you want to use DECwindows software with OpenVMS VAX Version 7.1, you must be running Version 1.2--3 or higher of the DECwindows Motif for OpenVMS layered product.
6487P004.HTM OSSG Documentation 9-DEC-1996 10:53:52.03
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.