Document revision date: 19 July 1999

Enter a function ID value: 3[Return] OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 2[Return] Enter a Known Service Name: ALPHA072[Return]

The following sections describe how to create the system disk from the operating system CD-ROM.

3.3.1 Installing from the CD-ROM

After you boot the operating system CD-ROM, choose the install option (1) from the menu displayed on the screen. For example:

OpenVMS (TM) Alpha Operating System, Version V7.2 Copyright (c) 1998 Compaq Computer Corporation. All rights reserved. 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-ROM. 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 V7.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-ROM may 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 UCXECO_42_1 V1.0 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 if you need to install any patches.

3.3.2 Choosing INITIALIZE or PRESERVE

After you choose the install option, the system displays the following information and prompts:

*********************************************************** 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 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 OpenVMS VAX or any other operating system is installed. 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,	do the following: Enter INITIALIZE. Press the Return key.
you want to remove all files from an existing system disk,	do the following: Enter INITIALIZE. Press the Return key.
you want to retain certain files on an existing disk,	press the Return key to accept the default (PRESERVE).

3.3.3 Specifying the Target Disk

The procedure next asks you for the name of the target disk. If you 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 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

3.3.4 Specifying the Volume Label

The system then prompts you for the volume label and asks if the information is correct. You can keep the label already assigned to the disk, accept the default label assigned by the system (ALPHASYS), or specify a different volume label (with a limit of 12 characters that can be letters A--Z, numbers 0--9, dollar signs ($), hyphens (-), or underscores (_)).

After you select the volume label and choose to continue by answering Yes to the next prompt, the target disk is initialized and mounted, and page and swap files are created. For example:

DKB400: is now labeled ALPHASYS. The existing label causes problems for OpenVMS. You must enter a new label. Enter volume label for target system disk: [ALPHASYS] alphainsv You have chosen to install OpenVMS Alpha on a new disk. The target system disk, DKB400:, will be initialized. It will be labeled ALPHAINSV. Any data currently on the target system disk will be lost. Is this OK? (yes/No) y Initializing and mounting target.... Creating page and swap files....

3.3.5 Setting the SYSTEM Account Password

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; they do not appear on the display.
• Press the Return key after you enter the password.
• 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.

3.3.6 Becoming a Cluster Member

The procedure now asks if your system will be part of a cluster. The display is similar to the following:

Will this system be a member of an OpenVMS Cluster? (Yes/No) Yes

Answering Yes to this question causes SYS$MANGER: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. 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 cluster when your newly installed system is first booted. You can do this by executing a command similar to the following:

$ @SYS$MANGER:CLUSTER_CONFIG

3.3.7 Becoming an OpenVMS Galaxy Instance

The procedure next asks if your system will be an instance in an OpenVMS Galaxy. The display is similar to the following:

Will this system be an instance in an OpenVMS Galaxy? (Yes/No) Yes

If you answer Yes to this question, and you also answered Yes to the OpenVMS Cluster question, information about required remedial kits is displayed.

For compatibility with OpenVMS Galaxy, any systems in the OpenVMS Cluster that are running versions of OpenVMS prior to Version 7.1-2 must have a remedial kit installed. The following display indicates the correct remedial kits for various OpenVMS Alpha and VAX systems.

For compatibility with OpenVMS Galaxy, any systems in the OpenVMS Cluster that are running versions of OpenVMS prior to Version 7.1-2 must have a remedial kit installed. The appropriate kit from the following list must be installed on all system disks used by these systems. (Later versions of these remedial kits may be used if available.) Alpha V7.1 and V7.1-1xx ALPSYSB02_071 Alpha V6.2 and V6.2-1xx ALPSYSB02_062 VAX V7.1 VAXSYSB01_071 VAX V6.2 VAXSYSB01_062

3.3.8 MEMORY CHANNEL Information

This section contains information specific to becoming a cluster member in a MEMORY CHANNEL environment.

The MEMORY CHANNEL remedial kit (ALPMC01_071 and later) changed the data structures used with MEMORY CHANNEL. This change is not backwardly compatible and requires special considerations for MEMORY CHANNEL when upgrading OpenVMS from a version earlier than Version 7.1-2 to Version 7.1-2 (or later), under the following conditions:

• Your upgraded system disk will be part of an OpenVMS Cluster, and
• One or more of the systems in the OpenVMS Cluster has a MEMORY CHANNEL adapter, and
• Either:
  • Your OpenVMS Cluster uses multiple system disks, or
  • You will be performing a rolling upgrade

If your target system is already at OpenVMS Version 7.2 or later, you have already resolved this configuration issue. In this case, or if you indicated that the target system will not be a member of an OpenVMS Cluster, the procedure jumps to Section 3.3.9. Otherwise, it proceeds as follows:

An OpenVMS Cluster may use more than one system disk, either on a continuing basis, or only during a rolling upgrade. Will the OpenVMS Cluster use more than one system disk? (Yes/No) Yes

If you answer Yes to this question, the procedure provides information about MEMORY CHANNEL adapters, as follows:

A MEMORY CHANNEL adapter is a device that allows systems in an OpenVMS Cluster to be connected (usually through a MEMORY CHANNEL hub) to provide high speed communications among nodes in the OpenVMS Cluster.

If the procedure can detect that a MEMORY CHANNEL adapter (MCA) is present, it displays the following message:

This system has a MEMORY CHANNEL adapter.

Otherwise, it displays a question similar to the following:

Is a MEMORY CHANNEL adapter installed on this system or on any other system in the OpenVMS Cluster? (Yes/No) Yes

If you answer yes to this question, or your system has a MEMORY CHANNEL adapter, the following information is displayed:

You will be using multiple system disks and MEMORY CHANNEL adapters. This requires special consideration in order to avoid data corruption. Either the ALPMC01_071 TIMA kit must be installed on all system disks, or you must not use the MEMORY CHANNEL until after all system disks in the OpenVMS Cluster have been upgraded to the new OpenVMS release and all systems have re-booted from the upgraded system disks. You can prevent using MEMORY CHANNEL in one of two ways: o Power off the MEMORY CHANNEL hub, if one is used, or o Disconnect the MEMORY CHANNEL cable, if using a virtual hub. You must NOT POWER UP OR RECONNECT until after all system disks in the OpenVMS Cluster have been upgraded to the new OpenVMS release and all systems have re-booted from the upgraded system disks. You can search [VMS$COMMON.SYSUPD]VMSINSTAL.HISTORY for ALPMC on any system disk to determine if the TIMA kit is installed on that disk. Answer the next question with a "?" if you wish to search VMSINSTAL.HISTORY for the ALPMC01_071 TIMA kit. Do you have the ALPMC01_071 TIMA kit installed on all systems disks that are part of the OpenVMS Cluster and that are prior to OpenVMS V7.2? (Yes/No) No

If you answer with a question mark (?), the OpenVMS SEARCH command is used to look in VMSINSTAL.HISTORY for the ALPMC01_071 remedial kit. If the kit is found, the line in VMSINSTAL.HISTORY that contains it is displayed. If it is not found, the message "No strings matched" is displayed. In either case, the question is repeated.

Answer Yes if the ALPMC01_071 remedial kit is installed as required on all system disks. Otherwise, answer No. If you answer No, the procedure continues as follows:

Have you powered off the MEMORY CHANNEL hub? (Or disconnected the MEMORY CHANNEL cable?) (Yes/No) No

Answer Yes if you have powered off the MEMORY CHANNEL hub or disconnected the MEMORY CHANNEL cable. Otherwise, answer No. If you answer No, the procedure continues as follows:

Before proceeding with the OpenVMS upgrade, you must either o Install the ALPMC01_071 TIMA kit on all system disks that are part of the OpenVMS Cluster, or o Take action to prevent using MEMORY CHANNEL. Termination is strongly recommended. Do you want to terminate? (Yes/No) [YES]

The installation will not recommend terminating if

• The system will not be a member of an OpenVMS Cluster, or
• The OpenVMS Cluster does not use more than one system disk, or
• There is no MEMORY CHANNEL adapter in the OpenVMS Cluster, or
• The ALPMC01_071 remedial kit is installed on all system disks in the OpenVMS Cluster, or
• You have powered down the MEMORY CHANNEL hub or disconnected the MEMORY CHANNEL cables

The procedure next asks if you want to install the following Compaq windowing and networking software:

• DECwindows Motif for OpenVMS Alpha
• DECnet-Plus for OpenVMS Alpha or DECnet Phase IV for OpenVMS Alpha
• DIGITAL TCP/IP Services for OpenVMS

This software is included with the OpenVMS Alpha operating system. You can change the default values for these products later in the installation procedure.

The display is similar to the following:

You can install the following products along with the OpenVMS operating system: o DECwindows Motif for OpenVMS Alpha o DECnet-Plus for OpenVMS Alpha o DECnet Phase IV for OpenVMS Alpha o DIGITAL 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 product options?" Do you want to install DECwindows Motif for OpenVMS Alpha V1.2-5? (Yes/No) [YES] y Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with the OpenVMS operating system kit. Compaq 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 available through Compaq's MCS Services. 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 V7.2? (Yes/No) [YES] y Do you want to install Digital TCP/IP Services for OpenVMS V5.0-9? (Yes/No) [YES] n

Note that if you answer No to the prompt to install DECnet-Plus, you will be prompted to install DECnet Phase IV.

3.3.10 Setting System Parameters

The procedure now asks you to set values for the parameters SCSNODE and 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, then SCSNODE must be unique within the cluster. If you are using DECnet Phase IV or DECnet-Plus with DECnet Phase IV addresses, then SCSNODE must be the same as your DECnet node name.

SCSSYSTEMID must also be unique within an OpenVMS Cluster. In addition, if you are using DECnet Phase IV or DECnet-Plus with DECnet Phase IV addresses, then SCSSYSTEMID depends on the DECnet Phase IV address that your system is using.

The following is an example of the display and valid responses:

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 (Phase V) node synonym. If you have multiple OpenVMS systems, the SCSNODE on each system must be unique. Enter SCSNODE: alpcsi If you plan to use DECnet, SCSSYSTEMID must be set based on the DECnet Phase IV address. 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 WITHOUT Phase IV compatible addresses, enter 0.0. Enter DECnet (Phase IV) Address [1.1]: 63.180 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:

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

	privacy and legal statement
6522PRO_002.HTML