Document revision date: 28 June 1999

Availability Manager Version 1.2

Installation Instructions for OpenVMS Alpha Systems

and

Running DECamds and the Availability Manager Concurrently

This document describes the installation procedure for the Availability Manager Version 1.2 software on OpenVMS Alpha systems. It also explains some things you need to know if you run DECamds and the Availability Manager concurrently.

1 Installation Instructions for OpenVMS Alpha Systems

The Availability Manager Version 1.2 kit for OpenVMS can currently be installed only on OpenVMS Alpha Versions 7.1, 7.1-2, 7.2, and 7.2-1. The installation includes the Data Analyzer and Data Collectors for these versions. To install the most recent Data Collectors for both Availability Manager and DECamds products on OpenVMS VAX Version 6.2 and later or on OpenVMS Alpha Version 6.2, you must install the DECamds Version 7.2-1 kit. This limitation will be corrected in a future release of the Availability Manager product.

The following sections contain instructions for installing the Availability Manager Version 1.2 on OpenVMS Alpha systems.

1.1 Preparing to Install

Preparations for installation include the following tasks:

Install Java®; If Necessary, Edit the AM_LOGICALS.COM File

A software requirement for installing Availability Manager Version 1.2 on OpenVMS systems is Java Version 1.1.6-2 or later, which is available at the following website:

http://www.digital.com/java/download

Availability Manager Version 1.2 on OpenVMS is set up to use Java 1.1.6 as the default. If you install a later version of Java, you must edit AMDS$AM_SYSTEM:AMDS$AM_LOGICALS.COM to correct a logical name assignment for the new version of Java.

You need to edit the following assignment:

$ AMDS$AM_DEF AMDS$AM_JAVA_CLASSPATH - "/SYS$COMMON/JAVA/LIB/JDK116_CLASSES.ZIP", - SYS$COMMON:[JAVA.LIB]JDK116_CLASSES.ZIP

Using Java 1.1.8 as an example, make the following changes:

$ AMDS$AM_DEF AMDS$AM_JAVA_CLASSPATH - "/SYS$COMMON/JAVA/LIB/JDK118_CLASSES.ZIP", - SYS$COMMON:[JAVA.LIB]JDK118_CLASSES.ZIP

Download the Software

Follow these steps to download the software:

From the Availability Manager home page, click Software Download.
Complete the user survey, which allows you to proceed to the Download web page.

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

Availability Manager: vmsavailman012.pcsi-dcx_axpexe DECamds - Alpha: decamds0721axp.pcsi-dcx_axpexe DECamds - VAX: decamds0721vax.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-AXPVMS-AVAIL_MAN-V12--1.PCSI DECamds - Alpha: DEC-AXPVMS-AMDS-V72-1-1.PCSI DECamds - VAX: DEC-VAXVMS-AMDS-V72-1-1.PCSI

For DECamds installation instructions, refer to the DECamds User's Guide, which is available at the following web site:

http://www.openvms.digital.com:8000/72final/5929/5929pro.html

Check Quotas

Before installing the software, check that the following accounts are set to the quotas shown:

Account Quota

PGFLQUO 150,000 pagelets or greater (180,000 pagelets or greater to collect on many nodes)

BYTLM 36,000 bytes or greater

Account	Quota
PGFLQUO	150,000 pagelets or greater (180,000 pagelets or greater to collect on many nodes)
BYTLM	36,000 bytes or greater

If necessary, use the OpenVMS Authorize utility to increase these quotas.

Read the Release Notes

The Availability Manager Version 1.2 provides online release notes. Compaq strongly recommends that you read the release notes before proceeding with the installation. On OpenVMS systems, you can obtain a text version of the Availability Manager Version 1.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 RELEASE_NOTES AVAIL_MAN

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

$ PRODUCT EXTRACT 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.2 Starting the Installation

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 1.2, enter the following command:

$ PRODUCT INSTALL AVAIL_MAN/SOURCE=device directory/HELP

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

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.

Note

When the installation is complete, you must reboot your system.

1.3 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.
Go back to the beginning of the installation procedure to restart the installation.

1.4 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 a Compaq support representative.

1.5 Performing Postinstallation Tasks

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

Original File Name Renamed to...

AMDS$AM_LAUNCH_BROWSER.COM AMDS$AM_LAUNCH_BROWSER.COM_OLD

AMDS$AM_LOGICALS.COM AMDS$AM_LOGICALS.COM_OLD

AMDS$DRIVER_ACCESS.DAT AMDS$DRIVER_ACCESS.DAT_OLD

Original File Name	Renamed to...
AMDS$AM_LAUNCH_BROWSER.COM	AMDS$AM_LAUNCH_BROWSER.COM_OLD
AMDS$AM_LOGICALS.COM	AMDS$AM_LOGICALS.COM_OLD
AMDS$DRIVER_ACCESS.DAT	AMDS$DRIVER_ACCESS.DAT_OLD

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

2 Running DECamds and the Availability Manager Concurrently

The following sections explain some things you need to know if you run DECamds and the Availability Manager concurrently.

2.1 DCL Commands for Running DECamds and the Availability Manager

After you install the Availability Manager, you need to use the following commands to start the Availability Manager and DECamds:

Starting the Availability Manager

To start the Availability Manager, enter the following DCL command:

$ AVAIL

Starting DECamds

To start DECamds, enter the following DCL command:

$ AVAIL/MOTIF

You can also use any of the following qualifiers:

Qualifier Description

/CONFIGURE Specifies the directories from which input files are read. This can be a search list of directories or a logical defining a search list of directories.

/LOG_DIRECTORY Specifies the directory to which log files are written. Output files can be directed to the null device, NLA0:

/GROUP A comma-separated list of the groups of Data Provider nodes that you want the Data Analyzer to access.

Qualifier	Description
/CONFIGURE	Specifies the directories from which input files are read. This can be a search list of directories or a logical defining a search list of directories.
/LOG_DIRECTORY	Specifies the directory to which log files are written. Output files can be directed to the null device, NLA0:
/GROUP	A comma-separated list of the groups of Data Provider nodes that you want the Data Analyzer to access.

Note

If you install DECamds at a later time, you need to reinstall the Availability Manager to reactivate the AVAIL command.

2.2 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 logicals 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$AM_LOGICALS.COM

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

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$AM_STARTUP SYS$STARTUP:
AMDS$STARTUP

Logicals command file AMDS$AM_SYSTEM:
AMDS$AM_LOGICALS.COM AMDS$AM_SYSTEM:
AMDS$LOGICALS.COM

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

File	Availability Manager	DECamds
Installation directory	SYS$COMMON:[AMDS$AM]	SYS$COMMON:[AMDS]
Startup command procedure	SYS$STARTUP: AMDS$AM_STARTUP	SYS$STARTUP: AMDS$STARTUP
Logicals command file	AMDS$AM_SYSTEM: AMDS$AM_LOGICALS.COM	AMDS$AM_SYSTEM: AMDS$LOGICALS.COM
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

In the table, notice the following:

The STARTUP command procedure for each product executes the LOGICALS command file in the installation directory of the product. The group name for a node is defined in the LOGICALS file; therefore, make sure that you customize the LOGICALS file for each product appropriately.
The passwords that the Data Collector (SYS$RMDRIVER) will accept 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.
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.

privacy and legal statement

VMS_INSTALL.HTML