The minimum hardware configuration to perform the installation as described in the VSI OSAP/H1 Version 4.1 for OpenVMS Software Product Description (SPD) is as follows:

Refer to the VSI OSAP/H1 SPD to determine whether there are additional hardware requirements that apply to your application.

Your system requires the following minimum software versions:

Pre-requisite software and software versions may change. Refer to the current VSI OSAP/H1 Version 4.1 for OpenVMS Software Product Description (SPD) for the latest pre-requisite information. The following command displays the OpenVMS system version you are running:

$ WRITE SYS$OUTPUT F$GETSYI("VERSION")

Use the License Management Facility (LMF) to register the VSI OSAP/H1 software license in accordance with the license agreement signed for your site before you can run either the Installation Verification Procedure (IVP) or the software. License registration information is included in the Product Authorization Key (PAK). The PAK contains licensing information that should be registered before you start the installation.

To register the license, log into the SYSTEM account and set your default to SYS$UPDATE. You can register the license under LMF using either of the following methods:

If you plan to use the VSI OSAP/H1 software on more than one node of a cluster system, you must load the license on each of the other nodes after you have completed this one.

See the VSI OpenVMS License Management Utility Guide for more information about using LMF.

You require either the SETPRV privilege or all of the following privileges:

$ CMKRNL
WORLD
SYSPRV

The following command verifies your installation privileges:

$ SHOW PROCESS /PRIVILEGES

The following free disk space is required on OpenVMS systems:

The following command verifies the available disk space:

$ SHOW DEVICE SYS$SYSDEVICE

A feature of the VSI OSAP/H1 installation process allows you to locate the Omni Directory Services (ODS) directory structure on a disk other than the system disk. If you install the ODS directory structure on a separate disk, make sure that the disk has adequate free space.

The VSI OSAP/H1 installation requires specific system parameter settings.

FREE_GBLPAGES = 1000
FREE_GBLSECTS = 15

$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")
$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")

The following minimum process quotas are required for the installation account; this is typically the SYSTEM account:

You can use the AUTHORIZE utility to display installation process quotas by entering the following commands:

$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF> SHOW SYSTEM 

If no changes are necessary, enter the EXIT command to leave the AUTHORIZE utility. To modify system account quotas (BYTLM, for example):

UAF> MODIFY SYSTEM /BYTLM=32768

The utility responds with a message confirming the change and you can enter the EXIT command to leave the utility. You must then log out and log in again to reset the system account quotas.

For further information about AUTHORIZE, refer to the VSI OpenVMS System Manager's Manual.

VSI recommends that you perform a full system disk backup before you start any installation procedures. Use the backup procedures established for your site. For information about performing a system disk backup, refer to your OpenVMS documentation.

This section provides information you may require during the installation process.

To perform the installation, you must be logged in on the system manager’s account, or an account with the appropriate privileges.

If you did not run the Installation Verification Procedure (IVP) as part of the installation, you should run it separately after you have installed and started the product.

You must enable the following privileges to invoke the IVP:

NETMBX
PRMMBX
SYSLCK
WORLD
GROUP

Enter the following command to run the IVP:

$ @SYS$TEST:OSAPH1_IVP

The VSI OSAP/H1 IVP verifies that the VSI OSAP/H1 system is correctly installed and displays informational messages as it progresses. If the IVP fails, it displays a message indicating the reason for the failure. Correct the problem and then re-execute the IVP. When the VSI OSAP/H1 IVP has executed successfully, the VSI OSAP/H1 software is ready for use.

The VSI OSAP/H1 IVP can fail for various reasons. The following table lists the possible causes for an IVP failure and ways to resolve the problem.

If you do not invoke the IVP during installation, you must use the following command to start VSI OSAP/H1 (before running any application program):

$ @SYS$STARTUP:OSH1_STARTUP

Otherwise, you can execute the following command to start up VSI OSAP/H1 :

$ @SYS$STARTUP:OSH1_STARTUP [AST] 

You must specify the AST parameter if you wish to use the AST-based version of VSI OSAP/H1 , rather than the thread-based version.

You require the following privileges to invoke the VSI OSAP/H1 stop procedure:

DETACH
PRMMBX
SYSNAM
CMKRNL
SYSGBL
PRMGBL
WORLD
GROUP 

Enter the following command to manually shut down the VSI OSAP/H1 process:

$ @SYS$MANAGER:OMNI_STOP

If you want the VSI OSAP/H1 process to shut down each time the system is brought down, include the command in the site-specific shutdown file SYS$MANAGER:SYSHUTDOWN.COM.

The SYS$COMMON:[ SYSHLP.EXAMPLES.OSH1] directory contains some examples of VSI OSAP/H1 usage.

You can consult the VSI OSAP/H1 release notes at any time after the installation from the SYS$HELP: directory. VMSINSTAL labels the release notes file with the current product name and version number, such as OSH104I.RELEASE_NOTES.