Software Requirements for Micro Focus Enterprise Developer Unix Components

Software required by the setup file

• The "awk", "ed", "ps", "sed", tar", "sed" and "which" "tar" utilities must be installed and added to the PATH.
• The pax archiving utility is required by the setup file. Pax is distributed with most UNIX/Linux systems but, if it is missing, you must install it separately. To verify pax is installed, run pax --help or pax --version at the command line.

• Xterm, the terminal emulator for the X Window System, is part of your UNIX/Linux distribution but is not installed by default. Use your UNIX/Linux installation media to install it.

• GNOME menus and buttons have been standardized across all applications so that icons are not displayed by default. To keep the icons and the look and feel of previous versions, enable the menus_have_icons property with the command:

  gconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true

Libraries required by the setup file

The following table lists the required libraries for Red Hat and SUSE Linux platforms. The setup file checks that both the 32-bit and 64-bit libraries listed below are installed on both 32-bit and on 64-bit Operating Systems for this product to install and work correctly.

If installing on a 64-bit OS, the 32-bit libraries are not installed by default and must be installed before you start the installation.

• Libraries marked with an 'X' are not included in the platform and need to be installed separately.
• ¹On SUSE 12 and 15, you can only install the 64-bit version of Enterprise Developer. The glibc-locale-32bit library is still required by the SafeNet Sentinel licensed components.
• ²On Red Hat, these libraries are required to enable COBOL and PL/I to compile.
• * Additional libraries required to use the core_on_error run-time system variable. The gdb packages (for the GNU Project Debugger) can be installed from the install media for your OS.
• ** Operating system libraries required for PL/I support on both SUSE and Red Hat.

Visit the Red Hat Web site for more information.

Required environment variables

• To execute JVM COBOL code, you need to set the environment as follows:
  • Set the JAVA_HOME environment variable. When installing the product, set this variable to a 64-bit Java installation or the installation terminates. For example, execute the following:

    export JAVA_HOME=java_install_dir

    where java_install_dir is the path to the JAVA installation directory such as /usr/java/javan.n

  • Add $JAVA_HOME/bin to your system PATH variable. To do this, execute:

    export PATH=$JAVA_HOME/bin:$PATH

  • You need to set the LANG environment variable to pick up localized messages. If you do not set it as specified here, the installation will run but you might experience unexpected behavior from the installer.

    The LANG settings are English and Japanese only so set it to one of the following locales:

    C, default, en_GB, en_GB.UTF-8, en_US, en_US.UTF-8

    ja_JP, ja_JP.SJIS, ja_JP.UTF-8, ja_JP.eucJP, ja_JP.eucjp, ja_JP.sjis, ja_JP.ujis, ja_JP.utf8, japanese

    You can set LANG before running the setup file as follows:

    export LANG=C

    Alternatively, add it to the start of the setup command line:

    LANG=C ./setupfilename

    See Using the LANG Environment Variable for details.

License Manager requirements