Preparing to install CICS Transaction Gateway

These tasks must be completed before attempting to install CICS® Transaction Gateway.

  1. Check that your operating system is supported; for more information see Operating systems.
  2. Only one of the products CICS TG for Multiplatforms or CICS Transaction Gateway Desktop Edition can be installed on an operating system at a time. Any version of any of these products, including a beta release, must be removed before you install another version of one of these products.
  3. Product upgrade support is as follows:
    • CICS Transaction Gateway for Multiplatforms can be upgraded from V7.0 or later. Earlier and beta versions must be removed first.
    • CICS Transaction Gateway Desktop Edition can be upgraded from V8.0 or later.
  4. When a CICS Transaction Gateway installer is named with a version string that includes a fix pack number then that installer includes all the product updates supplied by that fix pack. For more information about version strings see Product versions.

Disk space requirements

The following table shows the disk space requirements for CICS Transaction Gateway. Additional space is required for log and trace data. During installation, extra space is required but this is freed when installation is complete:
Table 1. . Disk space requirements for CICS TG
Disk space requirement Windows Solaris AIX Linux HP
Product 380 MB 370 MB 360 MB 330 MB 410 MB
Additional temporary space needed for new installation 650 MB 600 MB 600 MB 600 MB 600 MB
Additional temporary space needed for upgrade 750 MB 700 MB 700 MB 700 MB 700 MB

Windows platforms

To prepare to install CICS Transaction Gateway:

  1. Log on with administrator privileges. Administrator authority is required for installing and uninstalling. Administrator privileges are available if you are a member of the local Administrators group or if you are a domain Administrator.
  2. Check that there is sufficient free disk space.
  3. If you are upgrading, stop any CICS Transaction Gateway application processes, product processes or services that are running, for example the IBM CICS Transaction Gateway service and the Configuration Tool.
  4. When using Windows Server Remote Desktop Services, ensure that your session is correctly configured to install new software. Take one of the following steps:
    • Install from Add or Remove Programs on the Control Panel.
    • At a command prompt, type change user /install to place the system into install mode. When the installation has finished, type change user /execute at the command prompt to return the system to execute mode.

UNIX and Linux platforms

Check the table for the disk space requirements for the installation after the install process finishes. Additional space is required for log and trace data. To successfully complete an installation ensure that additional temporary disk space is available; 460 MB is required for a new installation and 690 MB is required for an upgrade installation.

To prepare to install CICS Transaction Gateway:

  1. Log on as root.
  2. The following libraries must be installed before you run the UNIX/Linux CICS TG installer in the default Graphical mode:
    • libXtst - X11 Resource extension library
    • libXft - Font drawing library for X
    • libXp - X11 X Print library
    If any one of the libraries is not present, the installer might revert to the console/text-based installer.
    Prerequisites for Red Hat Enterprise Linux (RHEL) version 8

    Prerequisite shared libraries must be installed prior to running the CICS TG installer on Red Hat Enterprise Linux (RHEL). Prerequisite shared libraries might not be installed by default.

    The minimum level RPMs that contain these libraries are:
    • libstdc++.i686
    • ksh.x86_64
    • ncurses-compat-libs.i686
    • libnsl.i686

    Select packages that contain 64-bit (i686) runtime support. You can install a later release of any of these packages.

  3. Check that there is sufficient free disk space.
  4. If you are upgrading, stop any CICS Transaction Gateway application processes, product processes or services that are running, for example the Gateway daemon, the Client daemon and the Configuration Tool.
  5. Check the root user's umask to ensure that files created during the installation are readable by the user IDs that run CICS Transaction Gateway. A umask of 077 restricts access to the root user that installed CICS Transaction Gateway; a umask of 022 allows all users to run CICS Transaction Gateway.
  6. By default, the installer uses the /tmp directory for temporary data, or /root if there is insufficient space in /tmp. You can override this behavior by setting the IATEMPDIR environment variable to the required temporary directory before launching the installer.