Important Information

This section covers the following topics:

Administrator Status

During the installation, the Sudo panel may appear. This happens because Entire Output Management depends on the installation of Natural where the Sudo panel may be used. For the installation of Entire Output Management, however, you do not need sudoers privileges.

User ID for Installation

Entire Output Management 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.

Installation Directory

During the installation, you are asked to specify an installation directory. The installation of Entire Output Management 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.

File Permissions

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.

The Entire Output Management installation sets execution permissions (chmod ug+x) for the scripts located in the directory install-dir/EntireOutputManagement/INSTALL.

Side-by-Side Installations

Entire Output Management is a Natural application. Therefore, the rules for Natural also apply for Entire Output Management. For detailed information regarding side-by-side installations, see Installation in the Natural for UNIX documentation.

FNAT Usage

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.

Entire Output Management can only be installed into this FNAT.

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 Entire Output Management 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 Entire Output Management, product-specific information is written to the FUSER system file (install-dir/Natural/fuser). The FUSER path must not contain a symbolic link.

Upgrading Your Entire Output Management Environment

When one of the first two digits of the version number changes, we consider an installation an upgrade installation.

Updating Your Entire Output Management Environment

When the first two digits of the version number remain the same and the third or fourth digit changes, we consider an installation an update installation.

An update installation does not prompt again for license files. The existing license files will be used.