![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
The DECwindows support files are listed in Appendix E. After you finish the installation, you can use the DECwindows tailoring utility, DECW$TAILOR, to remove the DECwindows files you do not need. For more information about removing files with DECW$TAILOR, see Chapter 10.
If your distribution media is tape cartridges or magnetic tape, the procedure displays a message similar to the following after the DECwindows options you have selected have been successfully installed:
You can now remove the DECwindows distribution kit from MUA0:.
Remove the distribution media from the drive.
If your distribution media is compact disc leave it in the drive.
The installation procedure now displays information about cluster configuration. But, because there is no network present on the system at this point in the procedure, no cluster configuration work can actually be performed at this time.
In a cluster, you can run multiple systems sharing all files except
PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP, and VAXVMSSYS.PAR.
Cluster configuration cannot be done at this time because no network
is present. In order to configure a cluster, you must FIRST do one
or both of the following:
o Install DECnet-Plus (or DECnet Phase IV), or
o Execute SYS$STARTUP:LAN$STARTUP.COM by removing the
comment delimiter ("!") from the line
$! @ SYS$STARTUP:LAN$STARTUP.COM
in SYS$MANAGER:SYSTARTUP_VMS.COM.
Then configure the cluster by executing the following command:
@SYS$MANAGER:CLUSTER_CONFIG.COM
Once the network is running on your system, you can execute the SYS$MANAGER:CLUSTER_CONFIG.COM command procedure in configure your cluster. For more information about cluster configuration, see the OpenVMS System Manager's Manual: Essentials.
Next, the installation procedure prompts you to set passwords for the SYSTEM, SYSTEST, and FIELD accounts and uses this information to create a rights database.
When setting the passwords, remember:
Now we will ask you for new passwords for the following accounts:
SYSTEM, SYSTEST, FIELD
Passwords must be a minimum of 8 characters in length. All passwords
will be checked and verified. Any passwords that can be guessed easily
will not be accepted.
* Enter password for SYSTEM:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEM verified
* Enter password for SYSTEST:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEST verified
The SYSTEST_CLIG account will be disabled. You must re-enable
it before running UETP but do not assign a password.
* Enter password for FIELD:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for FIELD verified
%VMS-I-PWD_INVALID, account password for SYSTEST is invalid %VMS-I-PWD_WEAK, password is too easy to guess Because of the preceding error, you must take action to secure this account. You must either disable this account, change its password, or do both.
Do you want to disable this account (Y/N)? N
Do you want to change the account password (Y/N)? Y
You must now select a new primary password for the SYSTEST account. The
password you select must be at least 8 characters in length and cannot
be the same as the name of the account:
New password:
Verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_SET, primary password for account SYSTEST set
Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT
Ignore any "-SYSTEM-F-DUPIDENT, duplicate identifier" errors
.
.
.
If you are installing a standalone system, the procedure displays the following prompts:
* Please enter SCSNODE name * Please enter SCSSYSTEMIDEnter the SCSNODE name and SCSSYSTEMID that you determined as part of the preinstallation tasks in Chapter 2.
If you are installing the operating system in a VAXcluster environment, you are not prompted to supply these parameters. The procedure calculates these parameters using the DECnet node name and node address you supplied earlier in the procedure.
After the procedure creates the rights database, it displays messages describing postinstallation tasks you might want to perform.
Note that you do not perform these tasks now but after the installation completes.
The tasks displayed on your screen might vary from the following example, depending on what options you chose to install earlier in the procedure.
After the installation finishes, you might want to do one or more of the
following tasks:
o DECOMPRESS THE SYSTEM LIBRARIES - To save space, many of the system
libraries are shipped in a data-compressed format. If you have
enough disk space, you can decompress the libraries for faster access.
To data expand the libraries, type:
$ @SYS$UPDATE:LIBDECOMP.COM
If you do not decompress these libraries, you will experience slower
response with the HELP and LINK commands.
o BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit
using the procedure described in the upgrade and installation supplement
supplied for your VAX computer.
o TAILOR THE SYSTEM DISK - You might want to review the files provided or
not provided during this installation. If you find there are files
you want to remove from the system disk (TAILOR OFF) or files you want
to add (TAILOR ON), use the following utilities to perform the
desired tailoring.
OpenVMS tailoring: $ RUN SYS$UPDATE:VMSTAILOR
DECwindows tailoring: $ RUN SYS$UPDATE:DECW$TAILOR
Note: The tailor procedure cannot be used to TAILOR ON or to TAILOR OFF
files located on an alternate device.
o DEFINE A LOGICAL NAME - Define the logical name MSGHLP$LIBRARY in
your site-specific startup file to be: DUA1:[HELP_MESSAGE] to
point to the new location of the MSGHLP database.
For more information about decompressing the system libraries, see Section 4.8 in Chapter 4. For information on using VMSTAILOR or DECW$TAILOR, see Chapter 10.
After the messages about postinstallation tasks are displayed, the procedure displays a message similar to the following:
Continuing with OpenVMS VAX V7.1 installation procedure. Configuring all devices on the system...
Proceed to the next section for information about registering your licenses.
Before you can use the OpenVMS VAX operating system and its components, you must first register all licenses. If you do not register your licenses at this point in the procedure, you must register them immediately after the installation, before you perform the other postinstallation tasks.
The OpenVMS VAX operating system uses one of two different categories of licenses, depending on the hardware and software configuration used and currently supported. The two categories of operating system licenses for OpenVMS VAX are:
The following table describes the types of licenses for each licensing category. Digital provides the proper license type with the purchase of the system. Not all license types are available for every system model.
| Type of License | Description |
|---|---|
| VAX VMS Licenses | |
| Traditional License | Provides unlimited use to the users on a defined system. VAX VMS traditional licenses are sized to capacity according to system type. |
| Multi-User License |
Provides use according to a specified number of concurrent users. This
is an activity-based license. The Multi-user License gives you the
right to use the operating system for up to the limit of users
specified in the license. An operating system
user is one who is logged in to the system or one who is using
the operating system software by means other than login, or both. This
license is available only on limited system models, primarily MicroVAX
and VAX 4000 systems.
Interactive use of VAX systems licensed with the Multi-user License can be increased by the addition of the OpenVMS VAX Individual User License¹ for one or more users. For more information, refer to the description of the OpenVMS VAX Individual User License later in this table. |
| VAX VMS Workstation License |
Provides use for a single user on a VAX workstation. This license type
allows one direct login for the single user and then one additional
login for system management purposes only.
Additional interactive use of VAX workstations licensed with the VAX VMS Workstation License requires the addition of an OpenVMS VAX User License¹ for one or more users. For more information, refer to the description of the OpenVMS VAX Individual User License later in this table. |
| File and Application Server License |
Provides for the noninteractive use of OpenVMS VAX. OpenVMS based
VAXservers are sold with a File and Application Server License.
The intent of an OpenVMS based VAXserver is to provide file, print, application, and compute services to clients who have remotely submitted their requests for these services. This license type also allows one direct login for system management purposes only. Additional interactive use of OpenVMS VAXservers licensed with the File and Application Server License requires the addition of an OpenVMS VAX User License¹ for one or more users. For more information, refer to the description of the OpenVMS VAX Individual User License later in this table. |
| OpenVMS VAX Licenses | |
| OpenVMS VAX O/S Base License² |
Provides the right to unrestricted, noninteractive use of the OpenVMS
VAX operating system for the execution of remotely submitted requests
for batch, print, application, and computing services, on a designated,
single processor.
No direct OpenVMS VAX operating system logins by users are permitted on the system. One direct login is allowed for system management purposes only. Interactive use of systems licensed with an OpenVMS VAX O/S Base License requires the addition of an OpenVMS VAX Individual User License¹ for one or more users. |
| OpenVMS VAX Individual User License¹ |
Provides the right to interactively use the operating system by a
specified, or unlimited, number of concurrent users on a designated,
single processor. A user is one who is logged in to a processor or one
who is interactively using the operating system software by means other
than login, or both. An OpenVMS VAX O/S Base License, or any of the
four types of VAX VMS Licenses, is a prerequisite for the OpenVMS VAX
Individual User License.
|
You must register your licenses in the following order:
For more information about registering licenses, see the following:
You can use the SYS$UPDATE:VMSLICENSE.COM procedure to register a license for any Digital product that supplies a Product Authorization Key (PAK). Or, you can register licenses with the LICENSE REGISTER command. See the OpenVMS License Management Utility Manual for detailed information.
The installation procedure displays the following message:
If you have any Product Authorization Keys (PAKS) to register, you can register them now. * Do you want to register any Product Authorization Keys? (Y/N)
| If you choose ... | Then ... |
|---|---|
| Not to register the licenses at this time |
Do the following:
|
| To register your licenses now |
Do the following:
|
By typing Y (Yes) to register your licenses now, you invoke the SYS$UPDATE:VMSLICENSE.COM procedure, which displays the following message:
OpenVMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. Exit this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to this menu.
Enter one of the above choices [1]
Select the appropriate options (beginning with 1, as shown) until you
have successfully registered all required PAKs.
After you register the OpenVMS VAX license, you must register the license for any of the following System Integrated Products (SIPs) you have purchased:
At this point in the installation, the procedure asks you for time zone information that is used for providing local time zone support.
For local time zone support to work correctly, the installation 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
If you chose to install DECnet--Plus earlier in the installation procedure, see Section 3.10.
If you chose not to install DECnet--Plus, go to Section 3.11.
Earlier in the procedure, you were asked whether you wanted to install the DECnet--Plus product. If you answered Yes, the procedure will now install the DECnet--Plus product.
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.
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: DAD1:
* Enter the InfoServer service name: OTHER_PRODS
* Enter the InfoServer work group number [0]:
The following product has been selected:
DEC VAXVMS DECNET_OSI V7.1
DEC VAXVMS DECNET_OSI V7.1: DECnet-Plus V7.1 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_OSI V7.1
Portion done: 0%...10%...20%...30%...40%...80%...90%...100?
The following product has been installed:
DEC VAXVMS DECNET_OSI V7.1
.
.
.
To complete the installation procedure, continue on to the next section, Section 3.11.
The remaining portion of the installation procedure runs AUTOGEN to evaluate your hardware configuration and estimate typical workloads. AUTOGEN then sets system parameters, the sizes of page, swap, and dump files, and the contents of VMSIMAGES.DAT. When AUTOGEN finishes and the system has rebooted, the installation procedure is complete.
The installation procedure runs AUTOGEN, as follows:
Running AUTOGEN to compute 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, see the OpenVMS System Manager's Manual: Essentials.
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
>>> B DUA1For information on booting, refer to the upgrade and installation supplement for your VAX computer. Then return to this manual.
OpenVMS VAX Version V7.1 Major version id = 1 Minor version id = 0 *************************************************************** OpenVMS VAX V7.1 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. ****************************************************************
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at 22-NOV-1996 16:54:24.71 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.24At this point the OpenVMS VAX operating system is running.
Welcome to OpenVMS VAX V7.1
Username: SYSTEM
Password:
.
.
.
Welcome to OpenVMS VAX Version V7.1
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.
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 TIMEThe 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
6487P003.HTM OSSG Documentation 9-DEC-1996 10:53:48.91
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.