General Notes About Installation

Before initiating the installation process, you should be aware of the points outlined in the following subsections.

Setting Up Tasklimits

When configuring software, the Configuration WFL job might terminate because the number of spooled tasks exceeds the Tasklimit for the queue. You can avoid this happening by submitting the Configuration WFL to a queue that does not have the Tasklimit attribute set. The maximum value of the Tasklimit is 31.

Required Supplementary Files

The following files are copied to DISK (or the alternate family pack), provided that the version being installed is higher than the version currently in place. (If it is not, the files are not copied from the Dictionary specified during installation, and a message is displayed.)

*NGEN28/1/LIBRARY
*NGEN28/1/LTEACH
*NGEN28/MLSLIBRARY
*NGEN28/1/HUBROUTER (copied to same pack as COMS)
*NGEN28/UTILITY/LINCFORM
*NGEN28/GLI
*NGEN28/OFF
*NGEN28/LVU
*NGEN28/RIP
*NGEN28SYS/CODES
*EXAMINER/LIBRARY
*SYSTEM/LINCXSUPPORT

Using a Privileged Usercode for Installation

The usercode from which the RUNTIME job is started must be privileged. If the RUNTIME job is started from a non-privileged usercode, any SLs for libraries released with this cut must be done manually from MARC under a privileged usercode.

If your machine has Security Administrator status enforced (by enabling the SECADMIN option), the usercode from which the RUNTIME job is started must have SECADMIN privileges. If the usercode does not have SECADMIN privileges, any SLs for libraries released with this cut must be done manually. Therefore, you must decide which usercode to use before you begin the installation.

Runtime Transfer Considerations

If you are installing AB Suite on environments used in Runtime Transfers, you must install the release from the same installation package in both the source and the target runtime environments.

Installing multiple Runtimes on the same MCP host

If you are installing multiple Runtimes on the same MCP host, each installation must be installed under separate usercodes with different APPL_BLD identities and unique port numbers. Each installation of Application Builder (APPL_BLD_) requires its own runtime environment. More information on installing APPL_BLD can be found in the installation instructions.

Unwrapping the GCA container for a First-Time Installation

If this is the first time that the runtime is being installed in the designated runtime usercode and you have not installed the GCA release already, you must make the GCA files available for installation now.

The GCA release media contains two packages.

  1. EPSILON package with LEVEL5 code files.

  2. ETA package with LEVEL6 code files.

See Required System Software Requirements to view the MCP Runtime Compatibility Matrix. The MCP Runtime Compatibility matrix helps you to choose the package that is compatible with your MCP host architecture and MCP release. When you choose a package from the IC release, ensure that it is compatible too.

Follow these steps to unwrap the files from the GCA release:

  1. Copy the GCA release to Windows and mount the ISO image file.

  2. Map a network drive to your privileged usercode on the MCP host.

  3. Copy the GCA container file from the ISO image to the MCP host. Select the container with the package you want to install.

    • EPSILON: GCA-70-1000-02.CON

    • ETA: ETA-GCA-70-1000-02.CON

  4. Disconnect the network drive.

  5. From CANDE, unwrap the files to the transfer pack:

    EPSILON

    WFL UNWRAP *= OUTOF "GCA-70-1000-02.CON" 
To <Transfer Pack>(RESTRICTED = FALSE)

    ETA

    WFL UNWRAP *= OUTOF "ETA-GCA-70-1000-02.CON" 
To <Transfer Pack>(RESTRICTED = FALSE)