VMS Authentication Module Administration & User's GUide

Previous PageTOCIndexNext Page



Chapter 1

Before You Begin

Introduction

This chapter introduces you to and prepares you for the VMS Authentication Module (VAM) product installation, configuration, startup, and testing. It is for the OpenVMS system manager or technician responsible for product installation and configuration.

Steps to Get VAM Up and Running

To get VAM up and working, you must perform the following steps:

Table 1-1 Getting VAM Up and Running (Continued)

1

Load the license pack.

 

2

Install the software.

See Chapter 2, Installing and Configuring VAM

3

Configure the VAM environment.

See Chapter2, Installing and Configuring VAM

Prepare for Installation

VAM installation involves using the VMSINSTAL procedure. Preparing for installation involves:

Understanding the hardware and software requirements

Determining if you have sufficient disk space and global pages for the installation

Determining where to install the software

Hardware Requirements

VAM has no special hardware requirements beyond those stated in the Software Product Description for TCPware, MultiNet or HP’s TCP/IP Services.

Software Requirements

VAM supports OpenVMS/VAX version 7.3; OpenVMS Alpha version 6.2, 7.0, 7.1, 7.2-1, 7.2-2, 7.3, 7.3-1, 7.3-2, 8.2, 8.3; OpenVMS I64 version 8.2, 8.2-1, 8.3; MultiNet version 4.4 or later, TCPware version 5.6-2 or later, UCX version 4.0 ECO 5 and later, and TCP/IP Services version 5.0 and later.

Disk Space and Global Pages

The destination device for your VAM software must have enough disk space so that you can install and run the software. Your system will require approximately 20,000 free blocks to install VAM, and will require approximately 1,800 blocks net after installation.

General Requirements

Check at this point that you:

Have OPER, SYSPRV, or BYPASS privileges

Can log in to the system manager's account

Are the only user logged in (recommended)

Backed up your system disk on a known, good, current, full backup (recommended)

Need to reinstall VAM after performing a major VMS upgrade

Ensure MultiNet, TCPware or TCP/IP Services (or UCX) is currently running.

Where to Install VAM

Install VAM in a location depending on the following:

Generally, on your system disk, but you can install VAM anywhere, just answer the question when it appears. This is also where you would keep your "common" files. Node-specific files should always be on your system disk.

If the machine is in a single platform cluster, on a common disk.

If the machine is in a mixed platform cluster, once on the Alpha system disk (or disks), once on the I64 system disk (or disks), and once on the VAX common system disk.

Release Notes and Online Documentation

The VAM Release Notes provide important information on the current release.

The Release Notes is a text file which can be obtained in one of three ways:

– By performing a partial installation

– During the full installation

– After the installation

To perform a partial installation (see Example 1-1):

1 Invoke VMSINSTAL at the system prompt:

$ @SYS$UPDATE:VMSINSTAL VAM010 device OPTIONS N

The device is the mount location of the distribution volumes.

2 Press Return at the prompt

Are you satisfied with the backup of your system disk [YES]?.

3 Select the option by number as to whether you want to display or print the Release Notes, or both.

4 If you requested a printout, enter the queue name for the printer. The default is SYS$PRINT.

5 Press Return at the prompt

Do you want to continue the installation [NO]?:.
This will print the VAM V1.0 Release Notes. (Note that if you enter YES at the prompt, you proceed with the full installation.)

6 You see the message

Product's release notes have been moved to SYS$HELP.

7 If you want to read or print the Release Notes after you exit the installation, you can access the VAM010.RELEASE_NOTES files in the SYS$HELP directory, as in:

$ TYPE SYS$HELP:VAM010.RELEASE_NOTES

Note! For this command to work as desired, do not redefine the SYS$HELP directory logical.

Example 1-1 Performing a Partial Installation to Obtain the Release Notes

$ @SYS$UPDATE:VMSINSTAL VAM010 DKA300: OPTIONS N [1]

        OpenVMS AXP Software Product Installation Procedure V7.1
It is 3-MARCH-2006 at 11:01.
Enter a question mark (?) at any time for help.
* Are you satisfied with the backup of your system disk [YES]? Return [2]
The following products will be processed:
  VAM V1.0

         Beginning installation of VAM V1.0 at 11:01
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
    Release notes included with this kit are always copied to SYS$HELP.
Additional Release Notes Options:
1. Display release notes
2. Print release notes
3. Both 1 and 2
4. None of the above

* Select option [2]: Return [3]

* Queue name [SYS$PRINT]: Return [4]
Job VAM010 (queue SYS$PRINT, entry 1) started on SYS$PRINT

* Do you want to continue the installation [NO]? Return [5]
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.[6]
        VMSINSTAL procedure done at 11:02

.
$TYPE SYS$HELP:VAM010.RELEASE_NOTES [7]

Previous PagePage TopTOCIndexNext Page