This document describes how to install Natural Security on an OpenVMS platform.
It is recommended that you install Natural Security after having installed all other subproducts of Natural, as this makes defining the subproducts' system libraries to Natural Security easier.
Important:
Once Natural Security is installed, Natural on the assigned
system file (FNAT) can only be accessed under the control of
Natural Security. Natural Security cannot be removed once it has been
installed. It is therefore recommended that you make a backup copy of your
FNAT system file before you install Natural Security.
The following topics are covered:
See also Natural Security On Different Platforms in the Natural Security documentation.
The following topics are covered below:
The space required on disk will be checked by the PCSI utility during the installation. See Disk Space in the section Installing and Setting Up Natural on OpenVMS.
Make sure that the following software has been installed on your computer:
Natural (same version and update package or patch level as that of Natural Security). Natural and Natural Security will be installed with the Natural suite installation.
Adabas.
Entire Net-Work (only required if the FSEC system file
is located in a remote database).
Natural Security uses the same versions of Adabas and Entire Net-Work as Natural. For the supported versions, see Related Software AG Products.
Also, make sure that LOGIN.COM and STARTUP_<name><v>.COM for the above products have been executed with the required product versions.
You need a license key file to install and activate Natural Security.
Before you start the installation, ensure that the license key file is available locally on SYS$LOGIN of the installing user on the machine where you intend to install Natural Security.
In general, Software AG recommends you to place the license key file on the file system before starting the installation.
The Natural Security system file FSEC in the Adabas
database which has been installed once for a Natural Security Version 6 can be
used for all later Natural Security versions.
If you install Natural Security in a cluster environment, you have to install it on each node in the cluster environment.
Note:
Sagbase must be installed on each node on which Natural Security is
to be installed.
Depending on how Sagbase has been installed, the initial Natural Security installation within a cluster will choose either the common or the specific root directory. The installation procedure checks if there is already an existing Natural Security installation in the cluster.
During an update installation the values of the system parameters are automatically checked.
The Natural Security installation procedure performs the following steps:
Checks whether the prerequisite version of the operating system is running.
Temporarily sets the privileges (BYPASS,
CMKRNL, SYSNAM).
Checks whether Sagbase (GBA) is installed.
Sets the owner of the SAG$ROOT directory to all installed product directories and files.
Checks whether system parameters have correct values.
Registers the product Sagbase to PCSI, if required.
Calculates and verifies the disk space needed for installation on both the work-directory device and the installation device.
Checks whether Natural is installed.
Creates the directories SAG$ROOT:[NATSEC] and SAG$ROOT:[NATSEC.V<version>].
Moves all files and images to the appropriate directories.
Sets protections for files and directories.
Creates the patch level file in the version subdirectory of the Natural Security directory.
Note:
Patch level files are for internal use and should not be modified or
deleted. They are used for other installations.
Before you start installing Natural Security using the PCSI procedure, perform the necessary steps as described in Installing and Setting Up Software AG Products on OpenVMS.
You started the installation using the command procedure SETUP.COM located on the installation medium to install Natural Security in the OpenVMS environment.
SETUP.COM copies the Natural Security PSC file from the installation medium to the SAG$ROOT:[SAGKITS] directory and starts the Natural suite installation of the Polycenter Software Installation utility (PCSI). The suite installation automatically invokes the single product PCSI installations such as Natural and Natural Security. During the installation procedure, a number of general information messages are displayed. Read all messages carefully and follow any advice they may provide.
During the Natural suite installation (see Continue the Suite Installation in the section Installing and Setting Up Natural on OpenVMS), you will be asked whether you want to install Natural Security:
Do you want to install NSC<version>? [YES]
Enter "YES" to continue with the Natural Security PCSI installation.
A message appears during the installation process, informing you that the product "SAG I64VMS NSC_<version> V<v.r> Layered Product" has been selected.
The installation procedure checks whether the product Sagbase (product code GBA) has already been installed and registered with the PCSI utility.
Information on the product license key is shown. Check whether the license key file is available on SYS$LOGIN of the installing user. Without a proper license key file, the installation will abort.
After the successful installation of the suite, you are informed about the installed products.
Depending on the type of installation, initial or update, you will have to perform some post-installation steps (see below).
To verify the product entry in the PCSI database, enter the following:
PRODUCT SHOW PRODUCT NSC_<version>
The information in this section is only relevant if this is a first-time installation of Natural Security.
Make sure that Natural Version <version> (where <version> must be the same version as the Natural Security version you are installing) is installed on your OpenVMS system.
Make sure that the Adabas database is running.
Enter the following commands to start the installation procedure:
SET DEF SAG$ROOT:[NATSEC.V<version>.INSTALL]
@SAGINST_NSC.COM
Important:
Several functions of the SAGINST_NSC.COM
command procedure require Natural administrator rights. Before you start the
command procedure, you should therefore make sure that you are defined as a
Natural administrator in the local configuration file (see
Administrator Assignments in the
Configuration Utility documentation).
A menu is displayed providing several functions.
Perform each of the following functions:
1 - Specify Adabas DBID for FSEC file 2 - Create database file for FSEC 3 - Select Natural parameter file for INPL 4 - Specify FSEC profile parameter in parameter file (same DBID as in Step 1, same FNR as in Step 2) 5 - Add FSEC definition to NATCONF.CFG 6 - Start FSEC INPL procedure (this step takes some time) 7 - Check log file of INPL procedure 8 - Copy NATSEC.EXE to Natural default directory
In the functions 1 and 2, you have to specify the DBID and FNR of the
FSEC file to be loaded into the Adabas database.
When you choose function 4, the Natural Parameter
Setting screen for the current parameter file appears. Using the
Edit option, enter the same DBID and FNR for
FSEC that you specified in functions 1 and 2 respectively. For
further information, see the
Overview
of Profile Parameters in the Configuration
Utility documentation.
In function 5, you have to specify the section
[NAT-DB-TABLE] in Natural's global configuration file
NATCONF.CFG which must contain the following subsection:
###Natural FSEC Definition [DBID_nnn] GEN = ADA EXE = ADA [DBID_nnn-END]
where nnn is the number of the database
which contains FSEC. If this subsection is missing (because
NATCONF.CFG was modified using the Configuration Utility),
add it, and if it is present, edit it accordingly.
After you have performed functions 1 to 8, Natural Security is installed and operational.
Proceed as described below in the section After the Natural Security Installation.
The information in this section is only relevant if this is not a first-time installation of Natural Security.
Make sure that Natural Version <version> (where <version> must be the same version as the Natural Security version you are installing) is installed on your OpenVMS system.
Make sure that the Adabas database is running.
Enter the following command to start the installation procedure:
@SAGINST_NSC.COM
A menu is displayed providing several functions.
In the case of an upgrade installation, you have the choice to use
your FSEC file from the previous installation or to create a new
one.
If you want to use an already existing FSEC file from a
previous installation, skip function 2 and then use functions 3 and 4 to enter
the DBID and FNR of your existing FSEC file.
If you want to use a new FSEC file, perform function 2
and then use functions 3 and 4 to enter the DBID and FNR of the new
FSEC file.
Natural Security is now installed and operational.
If necessary, perform the functions 6, 7 and 8 of the SAGINST_NSC.COM procedure.
If you have installed Natural Security for the very first time (that is,
if the version you have installed is your first version of Natural Security on
this FSEC system file), proceed as described in the
Natural Security documentation under the heading
First Steps
After the Installation. Do this immediately after a
successful installation of Natural Security and after the post-installation
steps performed with the command procedure
SAGINST_NSC.COM.
