This document covers the following topics:
During the installation, the Sudo panel may appear. This happens because Natural Business Services depends on the installation of Natural where the Sudo panel may be used. For the installation of Natural Business Services, however, you do not need sudoers privileges.
Natural Business Services depends on Natural. Therefore, the user ID under which you run the Software AG Installer must not be longer than eight characters. If you use a longer user ID, an error message is shown. You can then exit the installer and use a different user ID or - in case you also want to install other products - return to the product selection tree and deselect Natural.
During the installation, you are asked to specify an installation directory. The installation of Natural Business Services requires the installation of Natural. If Natural is already installed, choose the directory of your Natural installation. Otherwise, see Installation in the Natural for UNIX documentation for detailed information regarding the installation directory. The user that you are using to install must have full read and write permissions to this directory.
The user who starts the installation owns all files that are installed.
The user file-creation mode mask (umask command) determines
the file permissions for newly created files. Make sure that the
umask command you are using for the installation will not prevent
users from accessing and executing the installed files. On UNIX systems, for
example, the command umask 022 allows full access rights for the
file owner and read-only access rights for group members and others.
Natural Business Services is a Natural application. Therefore, the rules for Natural also apply for Natural Business Services. For detailed information regarding side-by-side installations, see Installation in the Natural for UNIX documentation.
By default, a new FNAT system file is created in the
installation directory during the installation of Natural
(<install-dir>/Natural/fnat).
This FNAT must always exist, and the global configuration file
must have an entry which defines this FNAT.
Natural Business Services can only be installed into
this FNAT.
Note:
If you want to check or edit the settings in the global configuration
file, use the Natural Configuration Utility.
The Software AG Installer maintains an internal list of installed
products, which must coincide with the add-ons that are currently installed in
the FNAT. This is important for updates and uninstallations to
work correctly.
For this reason:
Do not install products into the FNAT without the use of
the Software AG Installer.
Do not replace the default FNAT
(<install-dir>/Natural/fnat)
with another FNAT.
Make sure to complete the installation of Natural Business Services by using the SYSPCI utility (this is explained later in this documentation).
If an error occurs due to the above-mentioned scenarios, the only way to solve the problem is a new installation. In some situations, one of the following workarounds may help:
Workaround 1: Complete the previous installation by using the SYSPCI utility.
Workaround 2: Uninstall the product and then start the installation once more.
During the installation of Natural Business Services, product-specific
information is written to the FUSER system file
(<install-dir>/Natural/fuser).
Do not use a different FUSER after the installation of
Natural Business Services. Otherwise, messages in libraries starting with
CST* and in the SYSTEM library will be missing, and
screens such as the Construct menu will show numbers instead of text.
When one of the first two digits of the version number changes, we consider an installation as an upgrade installation.
Natural Business Services is a Natural application. Therefore, it is not possible to upgrade an existing Natural Business Services installation under Natural Version 6.3 with a Natural Business Services Version 8.2 installation.
When the first two digits of the version number remain the same and the third or fourth digit changes, we consider an installation as an update installation.
An update installation does not prompt again for license files. The existing license files will be used.
A new Natural Construct version delivers the file <install-dir>/NaturalBusinessServices/INSTALL/data/CST.SYSR containing code frames. The original code frame names (for example, COPA9) have the suffix "9". If there is a Natural Construct fix for code frames, the name will have the suffix "8" (for example, COPA8) , the next fix the suffix "7", and so on. Natural Construct itself will use the code frame with the lowest prefix. Therefore, if you are installing Natural Construct over an existing version, you must delete all code frames supplied as fixes to previous versions of Natural Construct before upgrading.
Important:
If you used "8" as the suffix in the
name of a customized code frame, change the "8" to a
"7" or less before deleting the code
frames.
To determine which code frames to delete, list the existing code frames
in the SYSCST library (MENU F L) and scan for suffixes of
"8".
If you have an existing parameter file called NBSPARM, the
installation will reuse the current settings in NBSPARM. However,
the following parameters will be set or reset:
BPSFI=OFF
CMPRINT=$CMPRINT
MADIO=0
MAXCL=0
STACK will be reset
WORK=32
The definitions for the work files 1 through 5 will be set to
$WRKF1 through $WRKF5. Make sure that
$WRKF1 through $WRKF5 are defined in your environment
when needed.
To preserve your NBSPARM parameter file, either make a
backup copy or rename the parameter file before installing Natural Business
Services.