To repeat an explanation provided by the installation procedure,
type a question mark (?) at the prompt. To change or correct a response
made to an earlier question, type the "^" character
as many times as needed. Note that entering "^" may
take you back more than one question. To return to the main menu,
enter Ctrl/Y.
During the installation, the system will prompt you for the
following information:
- Selecting Option 1 from
the Menu: When you boot the OpenVMS operating system
kit (as instructed in
Booting the OpenVMS Operating System Kit), the operating system main menu appears as in the following
example. Choose option 1 to install the operating system, as shown.
Note that after the initial copyright message, the procedure might
take a few minutes before the OpenVMS operating system menu appears.
HP OpenVMS (TM) Alpha Operating System, Version 8.2
(c) Copyright 1976-2004 Hewlett-Packard Development Company, L.P.
Installing required known files...
Configuring devices...
****************************************************************
You can install or upgrade the OpenVMS Alpha operating system
or you can install or upgrade layered products that are included
on the OpenVMS Alpha operating system CD/DVD.
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
Please choose one of the following:
1) Upgrade, install or reconfigure OpenVMS Alpha Version 8.2
2) Display products and patches that this procedure can install
3) Install or upgrade layered products and patches
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Execute DCL commands and procedures
8) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1
The OpenVMS Alpha operating system CD might contain patch
kits. If it does, information similar to the following is displayed: The following PATCH kits are present on the OpenVMS Alpha
distribution media.
----------------------------------- ----------- ----------
PRODUCT KIT TYPE KIT FORMAT
----------------------------------- ----------- ----------
DEC AXPVMS TCPIP_ECO V5.3-182 Patch Sequential
----------------------------------- ----------- ----------
1 item found
Please consult the OpenVMS Alpha Upgrade and Installation Manual,
the Release Notes, and the Cover Letter to determine if any or
all of these patches may be required for your system.If you have not already done so, check to determine whether
you need to install any patches.
The initial display from the procedure also includes information
about how to respond to prompts (as documented in detail in
Responding to Prompts During the Installation):
***********************************************************
The installation procedure will ask a series of questions.
() - encloses acceptable answers
[] - encloses default answers
Type your response and press the <Return>key. Type:
? - to repeat an explanation
^ - to change prior input (not always possible)
Ctrl/Y - to exit the installation procedure
- Creating the System Disk:
The procedure allows you to begin creating the system disk. First,
it displays the following information followed by the prompt asking
whether you want to initialize or preserve the disk, as shown:
There are two choices for Installation/Upgrade:
INITIALIZE - Removes all software and data files that were
previously on the target disk and installs OpenVMS Alpha.
PRESERVE -- Installs or upgrades OpenVMS Alpha on the target disk
and retains all other contents of the target disk.
* NOTE: You cannot use preserve to install OpenVMS Alpha on a disk on
which any other operating system is installed. This includes
implementations of OpenVMS for other architectures.
Do you want to INITIALIZE or to PRESERVE? [PRESERVE]
Respond to the INITIALIZE or PRESERVE prompt as follows:
|
IF
... |
THEN ... |
Your system disk is new
|
- Enter INITIALIZE.
- Press Return.
|
You want to remove all files from an existing
system disk
|
- Enter INITIALIZE.
- Press Return.
|
You
want to retain certain files on an existing disk
|
Press Return
to accept the default (PRESERVE).
|
 | With OpenVMS I64, during initialization of the target
system disk, the installation process creates a diagnostic partition,
visible only at the console prompt. For more information about this
partition and options you may take, see
Alternative Ways to Initialize the System Disk. With both OpenVMS Alpha and I64 systems, the installation
procedure initializes the target disk with volume expansion (INITIALIZE/LIMIT).
This renders the disk incompatible with versions of OpenVMS prior
to Version 7.2. In most cases, this does not present a problem.
However, if you intend to mount the new disk on a version of OpenVMS prior
to Version 7.2, you must perform the alternate method of initialization
described in
Alternative Ways to Initialize the System Disk. Note that by taking these steps, your new system disk might
include a relatively large minimum allocation size (as defined by
/CLUSTER_SIZE). As a result, small files will use more space than
necessary. Therefore, perform these steps ONLY for system disks
that must be mounted on versions of OpenVMS prior to Version 7.2. |
- Specifying the System Disk (Target Disk):
The procedure next asks you for the name of the target disk. If
you do not know the name of the disk, enter a question mark (?).
The system displays a list of devices on your system. Select the
appropriate disk and respond to the prompt. For example:
You must enter the device name for the target disk on which
OpenVMS Alpha will be installed.
Enter device name for target disk: (? for choices) DKB400
If this is the first installation on this system, no default
device is indicated, as in this example. A default device name is
listed if this is not the first installation (for example, [DKB400]
or, for a Fibre Channel disk device, [$1$DGA567]).
If you select a device that is not available or that cannot
be used for some other reason, the system displays information indicating
why the device cannot be used. For example, if you enter MKA500,
a tape device, a message similar to the following is displayed: MKA500 is not a disk device
- Specifying the Volume Label:
If you select a device that can be used, the system then informs
you of the volume label currently assigned to this device and asks
whether you want to keep that label. If you choose not to keep that
label, you are prompted for a new label, as shown in the following
example. The OpenVMS operating system uses the volume label to identify
and reference the disk. Make sure the label you use is unique;
problems occur if the same label is used by different disk volumes.
DKB400: is now labeled ASPVMS82.
Do you want to keep this label? (Yes/No) [Yes] NO
Enter volume label for target system disk: [ALPHASYS]
You can keep the label already assigned to the disk, accept
the default label assigned by the system (for Alpha systems, ALPHASYS;
for I64 systems, I64SYS), or specify a different volume label (with
a limit of 12 characters that can include A to Z, 0 through 9, and
optionally, the dollar sign ($), hyphen (-), and underscore (_)
characters).
| HP strongly recommends that the volume labels for all
disks on your system or OpenVMS Cluster have unique labels. If a
disk having the same label as the system disk is mounted, various
OpenVMS components will not function as intended. |
- Specifying On-Disk Structure Level:
After you enter the volume label for the target system disk, you are
asked if you want to initialize the target system disk with On-Disk
Structure Level 2 (ODS-2) or Level 5 (ODS-5). If you selected PRESERVE
instead of INITIALIZE, you are not asked about the on-disk structure
level.
The target system disk can be initialized with On-Disk Structure
Level 2 (ODS-2) or Level 5 (ODS-5). (? for more information)
Do you want to initialize with ODS-2 or ODS-5? (2/5/?) For details about ODS-2 and ODS-5 file systems, refer to the HP OpenVMS System Manager's Manual, Volume 1: Essentials.
A brief summary follows:- ODS-2
ODS-2 allows for full compatibility with all OpenVMS VAX systems
and with OpenVMS Alpha systems prior to Version 7.2.
- ODS-5
 | | ODS-5 supports file names that are
longer, have a wider range of legal characters, and allow for mixed-case
file names. This feature permits use of file names similar to those
in a Microsoft Windows® or
UNIX® environment. |
| | ODS-5 supports hard links to files, access dates,
and files whose names differ only by case. |
| | ODS-5 volumes cannot be mounted on any version of
OpenVMS prior to Version 7.2. |
| | Systems running OpenVMS VAX Version 7.2 and later
can mount ODS-5 volumes, but cannot create or access files having
extended names. (Lowercase file name characters are seen in uppercase
on OpenVMS VAX systems.) |
Select ODS-2 or ODS-5 by entering 2 or 5 at the prompt.
- Specifying Hard Links (ODS-5 Only):
If you selected ODS-5, the procedure asks whether you want to enable
hard links (if you selected ODS-2, skip to the next step). Enter
YES or NO to indicate your choice.
Hard links can be enabled on ODS-5 disks. (? for more information)
Do you want to enable hard links? (Yes/No/?) YES
Both ODS-2 and ODS-5 support aliases, which are additional
names for a file or directory. Only ODS-5 supports hard links. One
of the main differences with hard links enabled is the way the DCL
DELETE command works. With hard links enabled, if you issue the
DELETE command to delete a file that has one or more aliases associated
with it, the command only deletes the alias by which the file is
being accessed. The actual file continues to exist and is accessible
by any remaining alias. The file is deleted only when the last remaining
alias is deleted. Without hard links enabled, the DELETE command deletes
both the alias by which the file is being accessed and the file
itself. Any other aliases remain but the file is no longer accessible
because it is no longer present. Thus, the remaining aliases are
unusable. If enabling hard links has any drawbacks, they are minor
and probably of concern only in rare circumstances. For example,
if disk quotas are in effect, though owners of a file can delete
any links to a file in a directory they can access, hard links in
other users' directories might cause a file to be retained, and
the file size will continue to be charged against that owner's
disk quota.
In general, be aware that enabling hard links does change
the file system's behavior and that applications and management
practices should respond accordingly (instead of being alias-specific,
for example).
For more information about hard links, refer to the HP OpenVMS System Manager's Manual, Volume 1: Essentials.
- Confirming Target System
Disk Choices: The procedure displays your target system
disk choices, and you are asked to confirm that they are correct.
In the following example, the choices made were to initialize the
disk with ODS-5 and without hard link. The volume label will be
ALPHASYS.
You have chosen to install OpenVMS Alpha on a new disk.
The target system disk, DKB400:, will be initialized
with structure level 5 (ODS-5).
Hard links WILL be enabled.
It will be labeled ALPHASYS.
Any data currently on the target system disk will be lost.
Is this OK? (Yes/No) YES
Initializing and mounting target....
Creating page and swap files....
- Specifying System Account Information
(Initialized Disks Only): If you are initializing the
target disk, you are prompted for system account information. Before
you respond to the system prompt asking you to enter a password
for the SYSTEM account, note the following:
- Passwords must be at least eight characters
in length (but not exceeding 31 characters). Valid characters for
the password include A through Z, 0 through 9, and optionally, the
dollar sign ($) and underscore (_). Passwords must contain at least
one alphabetic character (A through Z). The system converts all
characters to uppercase, so the case of characters you enter is
insignificant.
- Press Return after you enter the password. (The
password does not display as you type it.)
- After you enter the password, the procedure checks
to make sure it meets the requirements for a valid password.
- Reenter the password for verification.
The following is a sample display: You must enter a password for the SYSTEM account.
The password must be a minimum of 8 characters in length,
and may not exceed 31 characters. It will be checked and verified.
The system will not accept passwords that can be guessed easily.
The password will not be displayed as you enter it.
Password for SYSTEM account:
Reenter SYSTEM password for verification:If you reenter the password incorrectly or if the system determines
that the password is too easy for another user to guess, the system
displays an error message and gives you the opportunity to specify
a valid password.
- Declaring OpenVMS Cluster Membership:
The procedure now asks whether your system will be part of an OpenVMS
Cluster. The display is similar to the following:
Will this system be a member of an OpenVMS Cluster? (Yes/No)
You should answer YES if the system will be an OpenVMS
Galaxy instance or a member of an OpenVMS cluster. Answering
YES to this question causes SYS$MANAGER:CLUSTER_CONFIG.COM to run
automatically when your newly installed system is first booted.
The CLUSTER_CONFIG procedure will ask a series of questions about
the cluster. Your response to this question determines how the VAXCLUSTER
system parameter will be set. (The parameter name "VAXCLUSTER" has
been retained on OpenVMS Alpha systems.) For more information, refer
to the Guidelines for OpenVMS Cluster Configurations manual.
If you answer YES to the cluster question, the display is
similar to the following: When your new system is first booted you will be required to answer
additional questions in order to configure the OpenVMS Cluster.
If you answer NO to the cluster question, the system can still
be a member of an OpenVMS Cluster. However, in this case you will
have to explicitly configure the node into the cluster after the
installation is completed. For more information, see
Joining an OpenVMS Cluster.
For detailed information about cluster configuration, refer
to the HP OpenVMS Cluster Systems manual.
- Declaring System as OpenVMS Galaxy Instance
(Alpha Only): The procedure next asks whether your system
will be an instance in an OpenVMS Galaxy. (This question is asked
in OpenVMS Alpha installations only. OpenVMS I64 does not support
OpenVMS Galaxy.) The display is similar to the following:
Will this system be an instance in an OpenVMS Galaxy? (Yes/No)
Your answer to this question determines how the GALAXY system
parameter will be set.
- Setting SCSNODE
System Parameter: The system now asks you to specify
a value for the first of two system parameters, the SCSNODE parameter
(step 12 describes the output and prompts for the second system
parameter, SCSSYSTEMID). SCSNODE is a name that can be from 1 to
6 letters or numbers; it must include at least one letter. If this
system is part of an OpenVMS Cluster, SCSNODE must be unique within
the cluster. If you are using DECnet Phase IV for OpenVMS or DECnet-Plus
for OpenVMS with DECnet Phase IV addresses, then SCSNODE must be
the same as your DECnet node name.
The following is an example of the display and a valid
response: For your system to operate properly, you must set two parameters:
SCSNODE and SCSSYSTEMID.
SCSNODE can be from 1 to 6 letters or numbers. It must contain at
least one letter.
If you plan to use DECnet, SCSNODE must be the DECnet Phase IV
node name, or the DECnet-Plus node synonym.
If you have multiple OpenVMS systems, the SCSNODE on each system
must be unique.
Enter SCSNODE: ALPCSI
- Declaring
Use of DECnet; Setting SCSSYSTEMID System Parameter:
The next prompt asks whether you plan to use DECnet. It also informs
you that the SCSYSYSTEMID system parameter will be based on the
DECnet Phase IV address. SCSSYSTEMID must also be unique within
an OpenVMS Cluster.
If you plan to use DECnet, SCSSYSTEMID must be set based on the
DECnet Phase IV address.
Do you plan to use DECnet (Y/N) [YES]:YES
If you answer YES, you will see the information about the
DECnet Phase IV addresses and a prompt for a DECnet Phase IV address.
Enter a valid DECnet Phase IV address as in the following example.
Note that
DECnet Phase IV addresses are in the format
DECnet_area_number.DECnet_node_number
DECnet_area_number is a number between 1 and 63.
DECnet_node_number is a number between 1 and 1023.
If you plan to use DECnet-Plus WITHOUT Phase IV compatible addresses,
enter 0.0.
Enter DECnet (Phase IV) Address [1.1]: 63.180
A display such as the following informs you of the value assigned
to SCSSYSTEMID: SCSSYSTEMID will be set to 64692.
This was calculated as follows:
(DECnet_area_number * 1024) + DECnet_node_number
If you are not using DECnet, or if you enter 0.0 as the DECnet
Phase IV address, you are prompted to enter a SCSSSYSTEMID in the
range of 1 to 65535. If this is a standalone system,
the default 65534 is acceptable. However, if this system is part
of an OpenVMS Cluster, you must enter a unique SCSSYSTEMID. The
following is a sample display: The system cannot calculate SCSSYSTEMID from an address that is not
compatible with DECnet Phase-IV.
You will have to choose a value for SCSSYSTEMID.
If you plan to use LAT software, you may have to add /NODECNET to any
CREATE LINK commands in SYS$MANAGER:LATSYSTARTUP.COM.
Please choose a SCSSYSTEMID between 1 and 65535. If you have multiple
OpenVMS systems, the SCSSYSTEMID on each system must be unique.
Enter SCSYSTEMID [65535]: 12345
- Setting Local Time Zone:
Now the system will ask you to configure the local time zone. 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 will ask you to set the OpenVMS time differential factor
(TDF).
The procedure displays the main time zone menu. You can select
the time zone in either of two ways: - Selecting the number in the main time zone
menu that best represents the time zone desired (if multiple time
zones exist for the selection you make, you must select the exact
time zone from another menu).
- Using a search option that
allows you to bypass the time zone menu and search by name (partial
or full).
If you select one of
the numbers in the time zone menu, the corresponding time zone is
selected. At any prompt, you can enter a question mark (?) for help
information.
| An asterisk (*) next to a number indicates
that more than one time zone exists for that selection. If you select
such a number, an additional menu displays choices that allow you to
select the appropriate time zone. For example, if you choose the
United States (US) time zone from the main time zone menu, a second
menu displays the specific time zones within the United States. |
The following example shows how you would select the Eastern
time zone for the United States by using the menu number: Configuring the Local Time Zone
TIME ZONE SPECIFICATION -- MAIN Time Zone Menu "*" indicates a menu
0* GMT
1* AFRICA 17) EST 33) IRAN 49) PORTUGAL
2* AMERICA 18) EST5EDT 34) ISRAEL 50) PRC
3* ANTARCTICA 19* ETC 35) JAMAICA 51) PST8PDT
4* ARCTIC 20* EUROPE 36) JAPAN 52) ROC
5* ASIA 21) FACTORY 37) KWAJALEIN 53) ROK
6* ATLANTIC 22) GB-EIRE 38) LIBYA 54) SINGAPORE
7* AUSTRALIA 23) GB 39) MET 55* SYSTEMV
8* BRAZIL 24) GMT-0 40* MEXICO 56) TURKEY
9* CANADA 25) GMT 41* MIDEAST 57) UCT
10) CET 26) GMT0 42) MST 58) UNIVERSAL
11* CHILE 27) GMTPLUS0 43) MST7MDT 59* US
12) CST6CDT 28) GREENWICH 44) NAVAJO 60) UTC
13) CUBA 29) HONGKONG 45) NZ-CHAT 61) W-SU
14) EET 30) HST 46) NZ 62) WET
15) EGYPT 31) ICELAND 47* PACIFIC 63) ZULU
16) EIRE 32* INDIAN 48) POLAND
Press "Return" to redisplay, enter "=" to search or "?" for help, or
Select the number above that best represents the desired time zone: 59
US Time Zone Menu "*" indicates a menu
0* RETURN TO MAIN TIME ZONE MENU
1) ALASKA 5) EAST-INDIANA 9) MICHIGAN 13) SAMOA
2) ALEUTIAN 6) EASTERN 10) MOUNTAIN
3) ARIZONA 7) HAWAII 11) PACIFIC-NEW
4) CENTRAL 8) INDIANA-STARKE 12) PACIFIC
Press "Return" to redisplay, enter "=" to search or "?" for help, or
Select the number above that best represents the desired time zone: 6
You selected US /EASTERN as your time zone.
Is this correct? (Yes/No) [YES]:
To use the search option instead of menu numbers to select
the time zone, enter an equal sign ("=") at the menu
prompt instead of a number. You can enter one or more words or partial
words immediately after the equal string, or you can enter the equal
sign alone, in which case the procedure prompts you for the words
or partial words of the time zone you want to select. After you
enter that information, the procedure displays all matching time
zones, and you can then select the appropriate one.
The following example shows how you would select the Eastern
time zone for the United States by using the search option: Configuring the Local Time Zone
TIME ZONE SPECIFICATION -- MAIN Time Zone Menu "*" indicates a menu
0* GMT
1* AFRICA 17) EST 33) IRAN 49) PORTUGAL
2* AMERICA 18) EST5EDT 34) ISRAEL 50) PRC
3* ANTARCTICA 19* ETC 35) JAMAICA 51) PST8PDT
4* ARCTIC 20* EUROPE 36) JAPAN 52) ROC
5* ASIA 21) FACTORY 37) KWAJALEIN 53) ROK
6* ATLANTIC 22) GB-EIRE 38) LIBYA 54) SINGAPORE
7* AUSTRALIA 23) GB 39) MET 55* SYSTEMV
8* BRAZIL 24) GMT-0 40* MEXICO 56) TURKEY
9* CANADA 25) GMT 41* MIDEAST 57) UCT
10) CET 26) GMT0 42) MST 58) UNIVERSAL
11* CHILE 27) GMTPLUS0 43) MST7MDT 59* US
12) CST6CDT 28) GREENWICH 44) NAVAJO 60) UTC
13) CUBA 29) HONGKONG 45) NZ-CHAT 61) W-SU
14) EET 30) HST 46) NZ 62) WET
15) EGYPT 31) ICELAND 47* PACIFIC 63) ZULU
16) EIRE 32* INDIAN 48) POLAND
Press "Return" to redisplay, enter "=" to search or "?" for help, or
Select the number above that best represents the desired time zone: =EAST
Search for Time Zone by Full or Partial Name
"*" indicates a menu
1) BRAZIL / EAST
2) CANADA / EAST-SASKATCHEWAN
3) CANADA / EASTERN
4) CHILE / EASTERISLAND
5) MIDEAST / RIYADH87
6) MIDEAST / RIYADH88
7) MIDEAST / RIYADH89
8) PACIFIC / EASTER
9) US / EAST-INDIANA
10) US / EASTERN
Press "Return" to redisplay this menu,
enter "=" to search for a new zone,
enter "0" to return to the Main Time Zone Menu,
enter "?" for help, or
Select the number above that best represents the desired time zone: 10
You selected EASTERN / US as your time zone.
Is this correct? (Yes/No) [YES]:
The procedure then prompts you for the TDF.
For more information about local time zone support, refer
to the HP OpenVMS System Manager's Manual, Volume 1: Essentials.
- Setting Time Differential Factor (TDF):
The procedure now provides information about and prompts you to
enter the Time Differential Factor (TDF). The TDF is the difference
between your system time and Coordinated Universal Time (UTC), which
is an international standard (similar to Greenwich Mean Time) for
measuring time of day. The procedure supplies a default for TDF,
which is generally the correct response.The procedure also asks
whether the system's time zone supports daylight savings
time. The following example shows TDF information and prompts displayed
by the procedure:
Configuring the Time Differential Factor (TDF)
Default Time Differential Factor for standard time is -5:00.
Default Time Differential Factor for daylight saving time is -4:00.
The Time Differential Factor (TDF) is the difference between your
system time and Coordinated Universal Time (UTC). UTC is similar
in most respects to Greenwich Mean Time (GMT).
The TDF is expressed as hours and minutes, and should be entered
in the hh:mm format. TDFs for the Americas will be negative
(-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia and Australia
will be positive (1:00, 2:00, etc.).
This time zone supports daylight saving time.
Is this time zone currently on daylight saving time? (Yes/No): Y
Enter the Time Differential Factor [-4:00]:
NEW SYSTEM TIME DIFFERENTIAL FACTOR = -4:00
Is this correct? [Y]:
For more information about TDF support, refer to the HP OpenVMS System Manager's Manual, Volume 1: Essentials.
- Registering Licenses (Optional at this
Time): After setting the TDF, the system asks whether
you want to register any Product Authorization Keys (PAKs), as in
the following display:
If you have Product Authorization Keys (PAKs) to register,
you can register them now.
Do you want to register any Product Authorization Keys? (Yes/No) [Yes]
You can register the PAKs now by responding YES to the prompt,
or later by responding NO. You register licenses later by following
the directions in
Registering Your Licenses.
To register your licenses now, be sure you have the following
before proceeding:- A
copy of the Product Authorization Key (PAK) for each license that
you will register
- The HP OpenVMS License Management Utility Manual, which contains
complete, detailed information about the licensing procedure
The OpenVMS Alpha operating system uses one or more of the
types of licenses described in
Types of OpenVMS Alpha Licenses, depending on your hardware and software configuration.
For the OpenVMS I64 operating system, a single OE license grants
the right to use all the components bundled in the purchased OE.
Each OE is offered with per-processor licenses (PPL). The License
Management utility supports these OpenVMS I64 licensing practices.
The OpenVMS Unlimited User License is included with the Foundation
Operating Environment (FOE) and, therefore, is included with the
other OEs available.
| All OpenVMS Alpha Base and SMP licenses include the
NO_SHARE attribute and remain with the initial host computer. |
Table 2 Types of OpenVMS Alpha Licenses
|
Type of License |
Description |
Operating
System Base License
|
Grants
the right to noninteractive use of the remote batch, print, application,
and computing services of the OpenVMS Alpha operating system on
a single processor and authorizes one direct login (for system management
purposes only). For dual-processor systems, the base license for
these specific systems grants the right to noninteractive use of
the remote batch, print, application, and computing services of the
OpenVMS Alpha operating system on a dual processor.
The
base license is a prerequisite for OpenVMS Alpha User Licenses and
the SMP Base Extension license.
|
Symmetric Multiprocessing (SMP)
Base Extension License
|
Extends
the rights of the Operating System Base License to the matching multiprocessing
level of your Alpha SMP system.
Because the Symmetric
Multiprocessing (SMP) Extension grants all the rights that the existing
Base provided at the uniprocessing level, you do not need to reinstall those
licenses when you upgrade to a multiprocessing system. Each time
you upgrade your system to a new multiprocessing level (for example,
from a DEC 7000 Model 620 Alpha system to a DEC 7000 Model 630 Alpha
system), you add an SMP Extension to your existing licenses.
|
Individual User License
|
Grants the right to interactive use of
the OpenVMS Alpha operating system, provided the appropriate Operating
System Base License has been previously installed on the OpenVMS
Alpha operating system. The Individual User Licenses are available
in any quantity desired or as an unlimited user license.
|
Distributed Interactive User License
|
Grants the right to interactive use of
the OpenVMS Alpha operating system, provided the appropriate Operating
System Base License has been previously installed on an OpenVMS
Alpha operating system. Distributed Interactive User Licenses are
concurrent-use licenses and are available in any quantity desired
except unlimited. You can redesignate these licenses, and they may
be installed and used on a single OpenVMS Alpha processor, or shared
in a single OpenVMS Cluster environment.
|
OpenVMS Concurrent-Use Licenses
|
Grant the
right to interactive use of the OpenVMS Alpha operating system,
provided you have previously installed the appropriate OpenVMS Alpha
Operating System Base License on an Alpha computer. These licenses
are available in any quantity desired except unlimited. The licenses
are mobile (can be redesignated), and they may be installed and
used on a single OpenVMS Alpha processor, or shared in a single OpenVMS
Cluster.
You can add interactive users to the computer
at any time by specifying the same node name on the additional Interactive
User License PAK and by following the license combination procedure
described in the HP OpenVMS License Management Utility Manual.
|
When you answer YES to the prompt to register your licenses
now, the installation procedure invokes the SYS$UPDATE:VMSLICENSE.COM
procedure, which displays the following options menu:
VMS 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 REGISTER option and enter each license key until
you have successfully registered all required PAKs. After you register
all your licenses, exit the License Management procedure by entering 99
at the prompt.
- Installing Windowing
and Networking Products: Finally, the system asks whether
you want to install the following windowing and networking products.
Some of this software is required, as noted; some is optional.
- Availability
Manager base software (required)
- CDSA (required)
- Kerberos (required)
- Performance Data Collector
(base software, TDC_RT) (required)
- DECwindows Motif for OpenVMS
- DECnet-Plus for OpenVMS or DECnet Phase IV for OpenVMS
(but not both)
- TCP/IP Services for OpenVMS
The software that you choose to install (including the required
software) will be installed along with the OpenVMS operating system.
You can change the default values for these products later in the
installation procedure.
| The OpenVMS installation menu offers the choice to install
DECnet-Plus for OpenVMS or DECnet Phase IV for OpenVMS networking
software. You cannot have both installed on your
system at the same time. You can choose to install neither DECnet
product; however, certain products that depend on DECnet might be
affected. After you have DECnet-Plus and TCP/IP installed on your system,
you can run DECnet applications over your TCP/IP network. For more
information about DECnet over TCP/IP, refer to the DECnet-Plus for OpenVMS Network Management. |
The software products display is similar to the following
and includes the prompts for DECwindows Motif and DECnet-Plus (because
the first four products listed are required, you are not prompted
to install these). Note that the Performance Data Collector in the
list of products to be installed is TDC_RT, the run-time variant
(base software). You can install the following products along with the OpenVMS operating
system:
o Availability Manager (base) for OpenVMS Alpha (required part of OpenVMS)
o CDSA for OpenVMS Alpha (required part of OpenVMS)
o KERBEROS for OpenVMS Alpha (required part of OpenVMS)
o Performance Data Collector for OpenVMS Alpha (required part of OpenVMS)
o DECwindows Motif for OpenVMS Alpha
o DECnet-Plus for OpenVMS Alpha
o DECnet Phase IV for OpenVMS Alpha
o HP TCP/IP Services for OpenVMS
If you want to change your selections, you can do so later in the
installation by answering "NO" to the following question:
"Do you want the defaults for all options?"
Do you want to install DECwindows Motif for OpenVMS Alpha V1.5?
(Yes/No) [YES] Y
Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with
the OpenVMS operating system kit. HP strongly recommends that
DECnet users install DECnet-Plus. DECnet Phase IV applications are
supported by DECnet-Plus.
DECnet Phase IV is also provided as an option. Support for DECnet
Phase IV is available through a Prior Version Support Contract.
If you install DECnet-Plus and TCP/IP you can run DECnet
applications over a TCP/IP network. Please see the OpenVMS
Management Guide for information on running DECnet over TCP/IP.
Do you want to install DECnet-Plus for OpenVMS Alpha V8.2?
(Yes/No) [YES]
If you answer NO to the DECnet-Plus prompt, you are prompted
to install DECnet Phase IV: Do you want to install DECnet Phase IV for OpenVMS Alpha V8.2?
(Yes/No) [YES]
Finally, you are asked whether you want to install HP TCP/IP
Services for OpenVMS: Do you want to install HP TCP/IP Services for OpenVMS V5.5?
(Yes/No) [YES] Y
- Choosing Descriptive Help Text:
After you respond to the prompt for TCP/IP Services for OpenVMS, the
final stages of the installation proceed. First, the system asks
whether you want detailed descriptions:
The installation can provide brief or detailed descriptions.
In either case, you can request the detailed descriptions by typing "?".
Do you always want detailed descriptions? (Yes/No) [No]
If you answer YES, the system displays additional explanatory
text with each prompt.
- Selecting Product Component
Options (Accept All Defaults or Select Individually):
The system displays a message such as the following, indicating
that it is ready to install the operating system:
The following product has been selected:
DEC AXPVMS OPENVMS V8.2 Platform (product suite)
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that need to be installed to satisfy software dependency requirements.
DEC AXPVMS OPENVMS V8.2: OPENVMS and related products Platform
COPYRIGHT 1976, 8-NOV-2004
Hewlett-Packard Development Company, L.P.
Do you want the defaults for all options? [YES]
When selecting options, note the following: - If you want all the default values,
press Return.
If you want to select options individually, answer NO. The
system will then prompt you for each option and suboption shown
in the display in
Component Options and Suboptions.
- Review the list of options and compare them with
the requirements for your system. If you are selecting components
individually, be sure that you include all components necessary
to support the needs of your users. Note also that certain components
depend on the installation of other components.
- If you are not sure whether you want certain options,
request help by entering a question mark (?) at the prompt for that
option.
- After you select all the options you want, you will
have an opportunity to view your selections and make changes (if
necessary).
- OpenVMS Management Station software is automatically
installed on your OpenVMS system disk when you accept all the default
values. If you do not accept the default values, you must select
the OpenVMS Management Station component (server and client files)
if you plan to use that product. After the installation is complete,
you can then prepare your OpenVMS system and your PC to run OpenVMS
Management Station by following the procedures described in
Preparing to Use OpenVMS Management Station.
- If you decide after the installation to change which
OpenVMS operating system options you want installed on your system,
you must reconfigure the installation as described in
PRESERVE Option and
Adding and Removing Operating System Files (Optional).
- After you boot the new system disk and log in, you
can obtain information about individual system files by entering
HELP SYSTEM_FILES at the dollar sign prompt ($).
| Unless you have specific reasons to do otherwise, HP
recommends that you accept the defaults and install all OpenVMS
options. OpenVMS and layered products have various dependencies
on many of these options. Even if you think you do not need certain
options, some OpenVMS or layered product operations might not work
correctly if other OpenVMS options are not installed. Note also that, for OpenVMS I64 installations, the availability
of certain options depends on the Operating Environment (OE) you
have purchased. For example, OpenVMS Management Station is available
with the Enterprise Operating Environment (EOE) and Mission Critical
Operating Environment (MCOE). |
If you answer YES to accept the defaults for all options,
the system displays a message similar to the following, the contents
of which depend on the products you chose to install. If you answer
NO, the system prompts you for each option and suboption.
You are installing the Performance Data Collector runtime
environment for use ONLY with Version 8.2 of OpenVMS on Alpha platforms.
Note that a full kit that provides runtime environments for all
OpenVMS configurations supported by the Performance Data Collector,
and that includes a Software Developers Kit, can be downloaded from
URL:
http://h71000.www7.hp.com/openvms/products/tdc/
%TDC-I-NOSTRT, The TDC startup and IVP procedures will not be run
Insert the following line in SYS$MANAGER:SYSTARTUP_VMS.COM:
@sys$startup:tdc$startup.com
Availability Manager (base) for OpenVMS Alpha (required part of OpenVMS)
CDSA for OpenVMS Alpha (required part of OpenVMS)
KERBEROS for OpenVMS Alpha (required part of OpenVMS)
The Performance Data Collector for OpenVMS (required part of OpenVMS)
DEC AXPVMS DWMOTIF V1.3-1: DECwindows Motif
If a Local Language Variant is installed, refer to the Installation Guide.
Do you want to continue? [YES]If you answer NO, the installation takes you back to the main
menu. If you answer YES, and you chose to install DECnet Phase IV,
the procedure displays additional text similar to the following
before continuing. If you did not install DECnet Phase IV, the installation
continues to the next step (19).
DEC AXPVMS DECNET_PHASE_IV V8.2: DECNET_PHASE_IV
Support addendum to the DECnet Phase IV service contract required
Do you want to continue? [YES]
If you answer NO, the installation takes you back to the main
menu. If you answer YES, the installation continues as described
in the next step (19).
- Completing Installation onto System Disk
- Review Options and Confirm: When you have answered
all the prompts and selected the options you want installed, the
system displays information about the products you have
selected. The system allows you to review your selections and make
changes if necessary, then installs the product, provides informational
messages, and returns you to the original menu.
First, you are asked if you want to review the options:
Do you want to review the options? [NO]
If you answer YES, the system displays all the selected options
and suboptions, similar to the example in
Component Options and Suboptions. If you answer NO, the installation continues as
described with the sample script (beginning with "Execution phase
starting ...") that follows.
Figure 1 Component Options and Suboptions
|
 |
The component options listed in
Component Options and Suboptions are included within the OpenVMS Version 8.2 operating system.
Except as noted, these options apply to both Alpha and I64 systems.
Depending on the products you chose to install with the operating
system, additional components are included as well. After the system
displays all selected options and suboptions, you are prompted as
follows:
Are you satisfied with these options? [YES]
If you answer NO to this prompt, you are allowed
to selectively configure options and suboptions, even if you did
not do so previously. When you finish, you will again be asked whether
you are satisfied with the options you selected. When you answer
YES to indicate you are satisfied with the selections, the installation
begins installing OpenVMS onto the target disk. A sample display
follows.
| Alpha Systems Only: If
you perform two installations at the same time to systems connected
by MEMORY CHANNEL, you might see a message similar to the following every
5 seconds:
%PMA0 CPU00: 27-AUG-2004 14:58:40 Remote System Conflicts with
Known System - REMOTE NODE
%PMA0 CPU00: 27-AUG-2004 14:58:45 Remote System Conflicts with
Known System - REMOTE NODEDisregard the message. The installation or upgrade will proceed
normally and the message will not be present when the system reboots
with its actual node name. |
| Names of products
installed with OpenVMS differ between OpenVMS Alpha and I64 installations.
For example, the OpenVMS I64 windowing and networking product names are
all displayed as HP I64VMS product-name, such as HP I64VMS KERBEROS, while OpenVMS Alpha
product names are displayed in any of three different ways, depending
on the product and version:- HP product-name, such as HP AXPVMS KERBEROS V2.1
- DEC product-name, such as DEC AXPVMS DWMOTIF V1.5
- CPQ product-name, such as CPQ AXPVMS CDSA V2.1
|
Execution phase starting ...
The following products will be installed to destinations:
CPQ AXPVMS CDSA V2.1 DISK$ALPHASYS:[VMS$COMMON.]
DEC AXPVMS DECNET_OSI V8.2 DISK$ALPHASYS:[VMS$COMMON.]
DEC AXPVMS DWMOTIF V1.5 DISK$ALPHASYS:[VMS$COMMON.]
DEC AXPVMS OPENVMS V8.2 DISK$ALPHASYS:[VMS$COMMON.]
DEC XPVMS TCPIP V5.5 DISK$ALPHASYS:[VMS$COMMON.]
DEC AXPVMS VMS V8.2 DISK$ALPHASYS:[VMS$COMMON.]
HP AXPVMS AVAIL_MAN_BASE V8.2 DISK$ALPHASYS:[VMS$COMMON.]
HP AXPVMS KERBEROS V2.1 DISK$ALPHASYS:[VMS$COMMON.]
HP AXPVMS TDC_RT V2.1 DISK$ALPHASYS:[VMS$COMMON.]
Portion done: 0%..10%..20%..30%..40%..50%..60%..70%..80%
**** DECwindows Motif application and run-time support files DETECTED ****
**** DECwindows device support files DETECTED ****
...90%
%PCSI-I-PRCOUTPUT, output from subprocess follows ...
% - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration of
% HP TCP/IP Services for OpenVMS.
%
Portion done: 100%
Depending on the options you selected, messages such as the
preceding DECwindows and TCP/IP messages might be displayed at this
point. You might also see an %UPGRADE-I-FIXUP message, which indicates
that obsolete files on the system were incorrectly saved by remedial
kits. The "fixup" allows them to be correctly removed.
- Final Installation Output: The
installation continues, displaying the products that have been installed and
indicating the next steps to take, as in the following example:
The following products have been installed:
CPQ AXPVMS CDSA V2.1 Layered Product
DEC AXPVMS DECNET_OSI V8.2 Layered Product
DEC AXPVMS DWMOTIF V1.5 Layered Product
DEC AXPVMS OPENVMS V8.2 Platform (product suite)
DEC AXPVMS TCPIP V5.5 Layered Product
DEC AXPVMS VMS V8.2 Operating System
HP AXPVMS AVAIL_MAN_BASE V8.2 Layered Product
HP AXPVMS KERBEROS V2.1 Layered Product
HP AXPVMS TDC_RT V2.1 Layered Product
DEC AXPVMS OPENVMS V8.2: OPENVMS and related products Platform
HP AXPVMS KERBEROS V2.1
Configure the OpenVMS Kerberos clients & servers
If Kerberos will be in use on this system
and a current Kerberos configuration will
not be used, please take the time to run
the following command after the installation
has completed (and after rebooting the system
if this is an OpenVMS Installation or Upgrade):
@SYS$STARTUP:KRB$CONFIGURE.COM After configuration, two system files need to
be modified. The following line should be
added to SYS$MANAGER:SYSTARTUP.COM
$ @SYS$STARTUP:KRB$STARTUP
The following line must be added to
SYS$MANAGER:SYLOGIN.COM:
$ @SYS$MANAGER:KRB$SYMBOLS
The Kerberos 5 V2.1 documentation has been
provided as it was received from MIT. This
documentation may differ slightly from the
OpenVMS Kerberos implementation as it describes
the Kerberos implementation in a Unix environment.
The documents are:
KRB$ROOT:[DOC]IMPLEMENT.PDF
KRB$ROOT:[DOC]LIBRARY.PDF
KRB$ROOT:[DOC]ADMIN-GUIDE.PS
KRB$ROOT:[DOC]INSTALL-GUIDE.PS
KRB$ROOT:[DOC]KRB425-GUIDE.PS
KRB$ROOT:[DOC]USER-GUIDE.PS
HP AXPVMS TDC_RT V2.1: The Performance Data Collector (base) for OpenVMS
Users of this product require the following privileges:
(CMKRNL,LOG_IO,WORLD,PHY_IO,SYSPRV,SYSLCK)
Users of this product require the following process resource limits:
WSQUO minimum 4000
A read-me file is available in SYS$COMMON:[TDC]TDC_REAME.TXT
Release notes are available in SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT
DEC AXPVMS DWMOTIF V1.5: DECwindows Motif
System reboot is required.
If using a language variant, reboot after upgrade of language variant.
Installation Verification Procedure can be run after reboot.
DEC AXPVMS TCPIP V5.5: HP TCP/IP Services for OpenVMS.
Check the release notes for current status of the product.
The installation is now complete.
When the newly installed system is first booted, a special
startup procedure will be run. This procedure will:
o Configure the system for standalone or OpenVMS Cluster operation.
o Run AUTOGEN to set system parameters.
o Reboot the system with the newly set parameters.
You may shut down now or continue with other operations.
Process AXPVMS_INSTALL logged out at 27-AUG-2004 14:45:49.54
Press Return to continue...
****************************************************************
You can install or upgrade the OpenVMS Alpha operating system
or you can install or upgrade layered products that are included
on the OpenVMS Alpha operating system CD/DVD.
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
Please choose one of the following:
1) Upgrade, install, or reconfigure OpenVMS Alpha Version 8.2
2) Display products and patches that this procedure can install
3) Install or upgrade layered products and patches
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Execute DCL commands and procedures
8) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?)
- Configuring Boot Options (OpenVMS I64
only): When you boot your new system disk, you can boot your
system disk manually, as you did to boot your Operating Environment
DVD, using the following command as explained in
Booting the New OpenVMS I64 System Disk:
fs0:\efi\vms\vms_loader.efi
However, HP recommends instead that you configure your system
to make booting your system disk much simpler. You can add your
system disk as the first boot option in the EFI Boot Manager menu.
In this way, when that menu appears, you need only press Return to
boot the system disk, or if there is no response within 10 seconds,
your system disk will boot automatically. To add a boot option for
your system disk to the EFI Boot Manager menu, use the OpenVMS I64
Boot Manager (BOOT_OPTIONS.COM) utility. This is a menu-based utility
that is simple to use, as explained in the following steps. For
more information about this utility, refer to the HP OpenVMS System Manager's Manual, Volume 1: Essentials.
| To configure booting on Fibre Channel devices, you must
use the OpenVMS I64 Boot Manager utility. (Use of the utility is
optional for other devices but mandatory for Fibre Channel devices.)
For more information about configuring and booting Fibre Channel devices,
refer to the Guidelines for OpenVMS Cluster Configurations. |
- Select option 7 ("Execute DCL
commands and procedures") from the OpenVMS main menu.
- At the DCL prompt ($$$), enter the following command
to invoke the OpenVMS I64 Boot Manager utility:
$$$ @SYS$MANAGER:BOOT_OPTIONS.COM
- When the utility is invoked, the main menu displays.
To add your system disk as a boot option, enter 1 at the prompt,
as shown in the following example:
OpenVMS I64 Boot Manager Boot Options List Management Utility
(1) ADD an entry to the Boot Options list
(2) DISPLAY the Boot Options list
(3) REMOVE an entry from the Boot Options list
(4) MOVE the position of an entry in the Boot Options list
(5) VALIDATE boot options and fix them as necessary
(6) Modify Boot Options TIMEOUT setting
(B) Set to operate on the Boot Device Options list
(D) Set to operate on the Dump Device Options list
(G) Set to operate on the Debug Device Options list
(E) EXIT from the Boot Manager utility
You can also enter Ctrl-Y at any time to abort this utility
Enter your choice: 1
| While using this utility, you can change
a response made to an earlier prompt by typing the "^" character
as many times as needed. To abort and return to the DCL prompt, enter
Ctrl/Y. |
- The utility prompts you for the device name. Enter
the system disk device you are using for this installation. In the
following example, the device is DKA0::
Enter the device name (enter "?" for a list of devices): DKA0:
- The utility prompts you for the position you want
your entry to take in the EFI boot option list. To see a list of
the current boot options, enter a question mark (?):
Enter the desired position number (1,2,3,,,) of the entry.
To display the Boot Options list, enter "?" and press Return.
Position [1]: ?
- The list in the following example includes only
one boot option. To add your boot option entry to the top of the
list (the default) so that when the EFI Boot Manager menu times
out, your system disk boots automatically, press Return or enter
1:
EFI Boot Options list: Timeout = 0 secs.
-----------------------------------------------------------------
01. VenHw(d65a6b8c-71e5-4df0-d2f009a9) "EFI Shell [Built-in]"
-----------------------------------------------------------------
1 entries found.
Enter the desired position number (1,2,3,...) of the entry.
To display the Boot Options list, enter "?" and press Return.
Position [1]: 1
- The utility prompts you for OpenVMS boot flags.
By default, no flags are set. Enter the OpenVMS flags (for example,
0,1), or press Return to set no flags:
Enter the value for VMS_FLAGS in the form n,n.
VMS_FLAGS [NONE]:
Optionally, you can use any of the standard OpenVMS boot flags.
For example:
0,1
|
Enable SYSBOOT to change system parameters;
enable conversational booting for debugging purposes.
|
0,2
|
Load XDELTA.
|
0,4
|
Take the initial EXEC_INIT breakpoint.
|
0,20000
|
Print debug messages on boot.
|
0,30000
|
Print more debug messages on boot.
|
- The utility prompts you for a description to include
with your boot option entry. By default, the device name is used
as the description. You can enter more descriptive information as
in the following example. This example shows a sample confirmation
message (for devices with multiple paths, such as Fibre Channel
devices, a separate confirmation message is displayed for each path).
EFI$BCFG is the name of the executor file for the OpenVMS I64 Boot
Manager utility.
Enter a short description (do not include quotation marks).
Description ["DKA0"]: DKA0: OpenVMS V8.2 for PLM's System
efi$bcfg: DKA0: (BOOT003) Option successfully added
- When you have successfully added your boot option,
exit the utility by entering E at the prompt, and then log out of
DCL to return to the OpenVMS main menu.
Enter your choice: E
$$$> LOGOUT
- Shutting Down the System:
Unless you want to perform any other operations prior to booting
the new system disk, choose the shutdown option (8) from the OpenVMS
main menu to shut down the operating system, as shown in the following
example. If you want to install layered products that have not been installed
yet, HP recommends doing so during the postinstallation phase, as
documented in
Installing and Configuring Layered Products (New Installations, Possibly Upgrades).
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 8
Shutting down the system
SYSTEM SHUTDOWN COMPLETE
After you complete the installation and shut down the system,
you can boot your new operating system disk, as explained in
Booting the New OpenVMS System Disk. If you are installing OpenVMS
I64, make sure you remove the DVD from the drive.
HP OpenVMS Version 8.2 Upgrade and Installation... 
Installing the OpenVMS Operating System
