Document revision date: 15 July 2002

Installing Availability Manager Version 2.2

on OpenVMS Alpha Systems

and

Running DECamds and the Availability Manager Concurrently

This document contains the following sections:

Section 1 explains how to prepare to install both DECamds and the Availability Manager.
Section 2 tells how to install the Availability Manager software on Compaq OpenVMS systems. Instructions for installing DECamds are in a separate document on our Availability Manager documentation web page:
http://www.openvms.compaq.com/openvms/products/availman/docs.html
Section 3 explains how to run DECamds and the Availability Manager concurrently.

1 Preparing to Install

The following sections contain instructions for preparing to install DECamds and the Availability Manager on OpenVMS systems.

Note

The Availability Manager Version 2.2 kit for OpenVMS includes the Data Analyzer and Data Collector:

The Java Data Analyzer can be installed only on OpenVMS Alpha Versions 7.1, 7.1-2, 7.2, 7.2-1 and its variants, 7.3, 7.3-1 and its variants.
The Data Collector can be installed on OpenVMS VAX and OpenVMS Alpha Versions 6.2, 7.1, 7.1-2, 7.2, 7.2-1 and its variants, 7.3, 7.3-1 and its variants. It can also be installed on OpenVMS Alpha Version 7.0.
On OpenVMS Version 7.1 and later, the Data Analyzer is installed by default. To install only the Data Collector, say NO when asked, "Do you want the defaults for all options?"

1.1 Installing Patch Kits

Before installing the Availability Manager, you might need to install patch kits. These are described in the following sections.

1.1.1 Java Remedial Kits

Check for any remedial kits that Java requires. These are currently documented at the following Java web site:

http://www.compaq.com/java/download/jdk_ovms/vmspatches.html

Install these remedial kits, even if they are listed as optional. For example, for OpenVMS Version 7.2-1, the VMS721_PTHREAD Remedial Kit is listed as optional; however, this kit is required for Availability Manager Version 2.2.

These Java patch kits allow you to run JRE 1.1.8-7, which is included in the Availability Manager Version 2.2 kit.

1.1.2 Patch Kit for OpenVMS Versions 6.2 and 7.1

Before installing Availability Manager on OpenVMS Version 6.2 or 7.1 systems, you must install the following patch kit:

V6.2 to V7.1 PCSI ECO

This patch kit is available from the Public FTP Access area at the following web site:

http://www.support.compaq.com/patches/

The patch upgrades PCSI to the functionality of PCSI in OpenVMS Version 7.2. Availability Manager kits require this functionality.

1.2 Downloading the Software

Follow these steps to download the software:

Go to the Availability Manager home page:

http://www.openvms.compaq.com/openvms/products/availman/index.html

Click Software Download.
Complete the user survey, which allows you to proceed to the Download web page.

Click one or both of the Availability Manager or DECamds executables:

Availability Manager - Alpha: vmsavailman022.pcsi-dcx_axpexe - VAX: vmsavailman022.pcsi-dcx_vaxexe DECamds - Alpha: decamds0731.pcsi-dcx_axpexe - VAX: decamds0731.pcsi-dcx_vaxexe

Save the executable to a device and directory of your choice.

Run the executable and accept the default file name. The result will be:

Availability Manager: DEC-VMS-AVAIL_MAN-V0202--1.PCSI DECamds: DEC-VMS-AMDS-V0703-1-1.PCSI

1.3 Reading the Release Notes

The Availability Manager provides online release notes. Compaq strongly recommends that you read the release notes before you proceed with the installation. On OpenVMS systems, you can obtain a text version of the Availability Manager Version 2.2 Release Notes by setting the default to the directory where the kit resides. Then enter the following command at the DCL prompt:

$ PRODUCT EXTRACT/BASE=VMS RELEASE_NOTES AVAIL_MAN

If you have not set the default to that directory, enter the following command line:

$ PRODUCT EXTRACT/BASE=VMS RELEASE_NOTES AVAIL_MAN/SOURCE=disk:[directory]

where:

disk:[directory] refers to the disk and directory where the kit resides.

The default file name is DEFAULT.PCSI$RELEASE_NOTES.

1.4 Installing Additional Software

You must install the following additional software on your system before installing the Availability Manager:

DECwindows Motif for OpenVMS
DECwindows Version 1.2-4 is a requirement for Availability Manager Version 2.2. You must install DECwindows if it is not already installed on your system.

1.5 Upgrading from Versions Prior to OpenVMS Version 7.2

Upgrading from versions of the Availability Manager and DECamds released prior to OpenVMS Version 7.2 might cause problems when you start the Data Collector (AMDS$STARTUP.COM). The location of the startup files and some of the logical name definitions in the startup files were changed beginning with OpenVMS Version 7.2. Releases of the Availability Manager and DECamds since that time use the new locations and definitions.

For a description of these startup files, please see Section 3.1.1.

2 Installing the Availability Manager Software

Use the following procedure to start the installation:

Enter the DCL command PRODUCT INSTALL, followed by the name of one or more products. For example, to install the Availability Manager Version 2-1, enter the following command:

$ PRODUCT INSTALL/BASE=VMS AVAIL_MAN/SOURCE=device directory/HELP

where device and directory refer to the device and the directory, respectively, where the kit is located.

Note

You currently must install Availability Manager files in the PCSI default directory root.

For a description of the features you can request with the PRODUCT INSTALL command when starting an installation such as running the IVP, purging files, and configuring the installation, see the POLYCENTER Software Installation Utility User's Guide.

As the installation procedure progresses, the system displays a percentage message to indicate how much of the installation is done. For example:

Percent Done: 0%...40%...60%...70%...80%...90%...100%

If you started the installation using the /LOG qualifier to the INSTALL command, the system displays details of the installation.

PCSI Installation Messages

If you install DECamds Version 7.3-1 after installing Availability Manager Version 2.2, you might see any of the following PCSI messages:

%PCSI-I-RETAIN, file [SYS$LDR]SYS$RMDRIVER.EXE was not replaced because file from kit does not have higher generation number %PCSI-I-RETAIN, file [SYS$LDR]SYS$RMDRIVER.STB was not replaced because file from kit does not have higher generation number %PCSI-I-RETAIN, file [SYS$STARTUP]AMDS$STARTUP.COM was not replaced because file from kit does not have higher generation number %PCSI-I-RETAIN, file [SYS$STARTUP]AMDS$STARTUP.TEMPLATE was not replaced because file from kit does not have higher generation number %PCSI-I-RETAIN, file [SYSEXE]AMDS$RMCP.EXE was not replaced because file from kit does not have higher generation number %PCSI-I-RETAIN, module AVAIL was not replaced because module from kit does not have higher generation number %PCSI-I-RETAIN, file [SYSMGR]AMDS$DRIVER_ACCESS.DAT was not replaced because file from kit does not have higher generation number %PCSI-I-RETAIN, file [SYSMGR]AMDS$DRIVER_ACCESS.TEMPLATE was not replaced because file from kit does not have higher generation number %PCSI-I-RETAIN, file [SYSMGR]AMDS$LOGICALS.COM was not replaced because file from kit does not have higher generation number %PCSI-I-RETAIN, file [SYSMGR]AMDS$LOGICALS.TEMPLATE was not replaced because file from kit does not have higher generation number

These messages are to be expected because DECamds and the Availability Manager share all the files cited.

2.1 Stopping and Restarting the Installation

Use the following procedure to stop and restart the installation:

To stop the procedure at any time, press Ctrl/Y.
Enter the DCL command PRODUCT REMOVE to reverse any changes to the system that occurred during the partial installation. This deletes all files created up to that point and causes the installation procedure to exit.
Reenter the PRODUCT INSTALL command to begin the installation again.

2.2 Recovering from Errors

If the installation procedure fails for any reason, the following message is displayed:

%POLYCENTER Software Installation utility %INSTAL-E-INSFAIL, The installation of AVAIL_MAN has failed.

An error during the installation can occur if one or more of the following conditions exist:

The operating system version is incorrect.
The prerequisite software version is incorrect.
Quotas necessary for successful installation are inadequate.
Process quotas required by the POLYCENTER Software Installation utility are inadequate.
The OpenVMS Help library is currently in use.

If you receive an error message beginning with %PCSI-E-INSTAL, refer to the DCL HELP/MESSAGE utility for POLYCENTER Software Installation information and a possible solution to the problem.

If the installation fails, you must restart the installation procedure. If the installation fails due to an IVP failure, contact your Compaq support representative.

Note

If the installation successfully replaced the Data Collector driver (over a previous installation), you must reboot the system to use the new driver.

2.3 Performing Postinstallation Tasks

After you install the Availability Manager, you need to perform several postinstallation steps, which are explained in the following sections.

2.3.1 Merging Customizations of Files

If the Availability Manager installation finds these files, it renames them as follows:

Original File Name Renamed to...

AMDS$DRIVER_ACCESS.DAT AMDS$DRIVER_ACCESS.DAT_OLD

AMDS$AM_LOGICALS.COM AMDS$AM_LOGICALS.COM_OLD

AMDS$LOGICALS.COM AMDS$LOGICALS.COM_OLD

AMDS$AM_STARTUP.COM AMDS$AM_STARTUP.COM_OLD

AMDS$STARTUP.COM AMDS$STARTUP.COM_OLD

Original File Name	Renamed to...
AMDS$DRIVER_ACCESS.DAT	AMDS$DRIVER_ACCESS.DAT_OLD
AMDS$AM_LOGICALS.COM	AMDS$AM_LOGICALS.COM_OLD
AMDS$LOGICALS.COM	AMDS$LOGICALS.COM_OLD
AMDS$AM_STARTUP.COM	AMDS$AM_STARTUP.COM_OLD
AMDS$STARTUP.COM	AMDS$STARTUP.COM_OLD

The installation then creates new versions of these files using the original file name. You must merge any customizations you have made to the files into the files provided by the installation.

You might find it helpful to use the DIFFERENCES utility to compare the new and old files.

2.3.2 Editing Additional Files

Following installation of the Availability Manager software, you need to edit one file, and you can optionally edit two additional files on each Data Collector node.

The following list indicates the steps to take on OpenVMS Alpha or VAX Data Collector nodes. The files in steps 1 and 2, which are optional steps, contain default values that are used if you do not supply values. Step 3 is mandatory.

Optionally edit the following file to change passwords, which allow the node to be monitored by another node:
SYS$MANAGER:AMDS$DRIVER_ACCESS.DAT
Optionally edit the following file to change the name of the group you want this node to belong to:
AMDS$SYSTEM:AMDS$LOGICALS.COM
To start the Data Collector when the system boots, you must add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file:
$ @SYS$STARTUP:AMDS$STARTUP START

2.3.3 Defining Logical Names

OpenVMS kits for DECamds Version 7.3-1 and Availability Manager Version 2.2 provide a template file that system managers can modify to define the logical names used by the Data Collector. The file, SYS$MANAGER:AMDS$SYSTARTUP.TEMPLATE, can be copied to SYS$MANAGER:AMDS$SYSTARTUP.COM and edited to change the default logicals that are used to start the Data Collector and to locate its configuration files

The two most common logicals, especially in a mixed-environment cluster configuration, are the following:

Logical Description

AMDS$GROUP_NAME Specifies the group that this node will be associated with when it is monitored.

AMDS$CONFIG Specifies the location of the security file used by the Data Collector.

Logical	Description
AMDS$GROUP_NAME	Specifies the group that this node will be associated with when it is monitored.
AMDS$CONFIG	Specifies the location of the security file used by the Data Collector.

2.3.4 Turning on Managed Objects on OpenVMS Version 7.3 or Later Data Collector Nodes

Managed objects are available only on OpenVMS Version 7.3 and later. They are discussed in the introduction to the Cluster chapter in the Availability Manager User's Guide. Before a Data Collector node can make managed object data available to Data Analyzers, the system manager must take steps so that the Data Collector driver, RMDRIVER, is loaded early in the boot process.

OpenVMS kits for Availability Manager Version 2.2 contain a data file called SYS$AMCONFIG.DAT. This file turns "managed object" functionality on and off on Data Collector nodes. This functionality is turned off by default.

At boot time on both OpenVMS VAX and Alpha systems, the operating system looks for the SYS$AMCONFIG.DAT file in the SYS$SYSROOT:[SYSEXE] directory. If the file is found, the boot code reads the file to determine whether to load RMDRIVER so that managed objects can begin to use this driver at boot time.

In the template file on the kit, the flag in the SYS$AMCONFIG.DAT file is set to FALSE (the default) so that RMDRIVER is not loaded at boot time. Instead, AMDS$STARTUP.COM will load the file when it starts the Availability Manager.

System managers can perform the following actions to load RMDRIVER at boot time, thereby enabling users to access information about switched LANs on their systems:

Copy the SYS$AMCONFIG.DAT file from the SYS$EXAMPLES directory to the SYS$SYSROOT:[SYSEXE] directory.
Change the flag in the SYS$AMCONFIG.DAT file to TRUE.
Reboot your system.

After you complete these steps, RMDRIVER will be loaded at boot time, allowing managed objects to register with RMDRIVER and allowing users to see switched LAN data on their systems.

2.3.5 Enabling and Disabling Kernel Multithreading

On multiple-CPU OpenVMS systems, the logical name AMDS$AM_MULTITHREADING controls whether or not the Availability Manager runs on multiple CPUs (that is, whether it uses kernel multithreading). This logical name is defined in the SYS$MANAGER:AMDS$LOGICALS.COM file.

Setting AMDS$AM_MULTITHREADING to TRUE can improve application performance, but at the cost of application stability. Setting the logical name to FALSE (the default) forces the application to run on a single CPU. For the current set of patches available on OpenVMS, this approach offers the greatest stability.

Enabling and Disabling Commands

To enable kernel multithreading, set the logical to TRUE:
$ AMDS$DEF AMDS$AM_MULTITHREADING TRUE

To disable kernel multithreading, set the logical to FALSE:
$ AMDS$DEF AMDS$AM_MULTITHREADING FALSE

3 Running DECamds and the Availability Manager Concurrently

This section discusses how to configure and start Data Collectors and Data Analyzers for both DECamds and the Availability Manager.

To install and run DECamds and the Availability Manager concurrently, complete the steps outlined in Table 1.

Table 1 Installing and Running DECamds and Availability Manager Concurrently
Step Description For more information, see...

1 Install DECamds. See Section 1 for preparation instructions. For installation steps, see the DECamds installation instructions, which are available as a link from the Availability Manager Documentation web page.

2 Install the Availability Manager. Section 1 through Section 2.3.1

3 Review the Availability Manager and DECamds configuration files. Section 3.1

4 Make postinstallation edits. Section 3.2

5 Make sure the Data Collector is started on Data Analyzer nodes. Section 2

6 Use DCL commands to run DECamds and the Availability Manager. Section 3.5

**Table 1 Installing and Running DECamds and Availability Manager Concurrently**
Step	Description	For more information, see...
1	Install DECamds.	See Section 1 for preparation instructions. For installation steps, see the DECamds installation instructions, which are available as a link from the Availability Manager Documentation web page.
2	Install the Availability Manager.	Section 1 through Section 2.3.1
3	Review the Availability Manager and DECamds configuration files.	Section 3.1
4	Make postinstallation edits.	Section 3.2
5	Make sure the Data Collector is started on Data Analyzer nodes.	Section 2
6	Use DCL commands to run DECamds and the Availability Manager.	Section 3.5

3.1 Understanding Availability Manager and DECamds Configuration Files

The DECamds and Availability Manager products have several common files that the Data Collector (or Data Provider, in DECamds terms) uses. These two products also have several files that have similar functions. Files, directories, or logical names with the same or similar function have the prefix AMDS$ or AMDS$AM, representing DECamds or the Availability Manager, respectively.

The installation also uses this naming scheme to place files that are specific to either product. For example, the file that defines logical names for DECamds is:

AMDS$SYSTEM:AMDS$LOGICALS.COM

For the Availability Manager, this file is:

AMDS$AM_SYSTEM:AMDS$LOGICALS.COM

The names of files that the products have in common usually start with AMDS$.

3.1.1 Using Configuration Files

The following table shows the configuration files that the startup command procedure creates for the Availability Manager and for DECamds.

File Availability Manager DECamds

Installation directory SYS$COMMON:[AMDS$AM] SYS$COMMON:[AMDS]

Startup command procedure SYS$STARTUP:AMDS$STARTUP Same as Availability Manager

Driver file (contains passwords for DECamds V7.1 and earlier) n/a AMDS$SYSTEM:
AMDS$DRIVER_ACCESS.DAT

Driver file (contains passwords for DECamds V7.2 and later) SYS$MANAGER:
AMDS$DRIVER_ACCESS.DAT Same as Availability Manager

Logical names command file (contains group names for DECamds V7.1 and earlier) n/a AMDS$SYSTEM:
AMDS$LOGICALS.COM

Logical names command file (contains group names for DECamds V7.2 and later) SYS$MANAGER:
AMDS$LOGICALS.COM Same as Availability Manager

File	Availability Manager	DECamds
Installation directory	SYS$COMMON:[AMDS$AM]	SYS$COMMON:[AMDS]
Startup command procedure	SYS$STARTUP:AMDS$STARTUP	Same as Availability Manager
Driver file (contains passwords for DECamds V7.1 and earlier)	n/a	AMDS$SYSTEM: AMDS$DRIVER_ACCESS.DAT
Driver file (contains passwords for DECamds V7.2 and later)	SYS$MANAGER: AMDS$DRIVER_ACCESS.DAT	Same as Availability Manager
Logical names command file (contains group names for DECamds V7.1 and earlier)	n/a	AMDS$SYSTEM: AMDS$LOGICALS.COM
Logical names command file (contains group names for DECamds V7.2 and later)	SYS$MANAGER: AMDS$LOGICALS.COM	Same as Availability Manager

3.1.2 Merging Files

To use Data Collector passwords as well as group names and other configuration data from DECamds Version 7.1 and earlier, you must merge versions of files:

For passwords
The passwords that the Data Collector (SYS$RMDRIVER) accepts from the Data Analyzer for DECamds Version 7.1 and earlier are stored in the AMDS$DRIVER_ACCESS.DAT file in the SYS$COMMON:[AMDS] directory. The passwords for later versions of DECamds and for the Availability Manager are stored in SYS$MANAGER:AMDS$DRIVER_ACCESS.DAT.
For both products to use this file, merge any data you want to keep from the copy of AMDS$DRIVER_ACCESS.DAT in the SYS$COMMON:[AMDS] directory into the copy in the SYS$MANAGER directory. Then remove the file from the SYS$COMMON:[AMDS] directory. If you have both products installed and want both products to use the same AMDS$DRIVER_ACCESS.DAT file, make sure this file resides only in SYS$MANAGER.
For group names and other configuration data
The group names and other configuration data that the Data Collector (SYS$RMDRIVER) accepts from the Data Analyzer for DECamds Version 7.1 and earlier are stored in the AMDS$LOGICALS.COM file in the SYS$COMMON:[AMDS] directory. The group names for later versions of DECamds and for the Availability Manager are stored in SYS$MANAGER:AMDS$LOGICALS.COM.
For both products to use this file, merge any data you want to keep from the copy of AMDS$LOGICALS.COM in the SYS$COMMON:[AMDS] directory into the copy in the SYS$MANAGER directory. Then remove the file from the SYS$COMMON:[AMDS] directory. If you have both products installed and want both products to use the same AMDS$LOGICALS.COM file, make sure this file resides only in SYS$MANAGER.

privacy and legal statement

6552INSTALL_VMS.HTML