The minimum hardware configuration to perform the installation as described in the VSI OMNI API Software Product Description (SPD) is as follows:

Refer to the VSI OMNI API 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 OMNI API 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")

You must use the License Management Facility (LMF) to register the VSI OMNI software license 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. Register the license under LMF using either of the following methods:

$ SYS$UPDATE:VMSLICENSE.COM

$ LICENSE REGISTER VSI OMNI/qualifier,...

If you plan to use the VSI OMNI 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:

Enter the following command to verify the available disk space:

$ SHOW DEVICE SYS$SYSDEVICE

The VSI OMNI API 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 OMNI API installation requires specific system parameter settings.

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

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.

%VMSINSTAL_E_INSFAIL, The installation of OMNI V4.1 has failed.

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

* Are you satisfied with the backup of your system disk [YES]? YES
The following products will be processed:
       OMNIV4.1

       Beginning installation of OMNI V4.1 at 11:43
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product’s release notes have been moved to SYS$HELP.
Copyright 2017 VMS Software, Inc and Hewlett Packard Enterprise Development, LP
Installation procedure for: VSI OMNI for VSI OpenVMS Alpha (TM) V8.4-1H1

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:OMNI_IVP

The VSI OMNI IVP verifies that the VSI OMNI 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 OMNI IVP has executed successfully, the VSI OMNI API software is ready for use.

The VSI OMNI 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 OMNI API (before running any application program):

$ @SYS$STARTUP:OMNI_STARTUP FULL

Otherwise, you can execute the following command to start up VSI OMNI API:

$ @SYS$STARTUP:OMNI_STARTUP [AST]

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

You require the following privileges to invoke the VSI OMNI API stop procedure:

• DETACH
• PRMMBX
• SYSNAM
• CMKRNL
• SYSGBL
• PRMGBL
• WORLD
• GROUP

Enter the following command to manually shut down the VSI OMNI process:

$ @SYS$MANAGER:OMNI_STOP

If you want the VSI OMNI 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.OMNI] directory contains some examples of VSI OMNI API usage.

You can consult the VSI OMNI API 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 OMNIAPII041.RELEASE_NOTES for VSI OpenVMS Integrity and OMNIAPIA041.RELEASE_NOTES for VSI OpenVMS Alpha.