This readme file contains important information about the IBM CICS Transaction Gateway (CICS TG) that might not be available in the Eclipse Information Center.
The product documentation is provided as an Eclipse Information Center available at:
http://publib.boulder.ibm.com/infocenter/cicstgmp/v7r2/index.jsp
This readme file is available in plain text and HTML. Both files contain the same information. After installation the files are included in the <CICS TG install path> directory.
The text version of this file is suitable for use with a screen reader or braille device.
This section applies to running the full product installer which either installs the product or replaces an existing version of the product.
Before running the CICS TG installer the Korn shell must be installed on your system.
Before running the CICS TG installer on RHEL 5 some prerequisite shared libraries must be installed. The RPMs that contain these libraries are: libXp-1.0.0-8 compat-libstdc++-33-3.2.3 libXft-2.1.10-1.1 (The 32 bit version of this library should be installed on 64 bit RHEL 5) libXtst-1.0.1-3.1 (This 32 bit library should be installed on 64 bit RHEL 5)
Installation and uninstallation must be done by the user with root authority.
Before you install the product, check the root user's umask to ensure that files created during the installation are readable by the user IDs that will run the CICS TG. A umask of 077 restricts access to the root user that installed the CICS TG; a umask of 022 allows all users to run the CICS TG.
It is recommended that 240 MB of temporary storage is available to successfully complete installation.
Before running the CICS TG installer it is strongly recommended that you shut down all programs running on your system.
Install can be run in GUI, console or unattended mode The default mode is GUI.
GUI mode installation can be launched using the following command:
installer
Console mode installation can be launched using the following command:
installer -i console
Unattended installations can be launched using the following command:
installer -i silent -DLICENSE_ACCEPTED=true
Use the command:
ctguninst
By default the CICS TG uninstall command matches the mode used at installation. You can override the default mode to run in GUI, console or unattended mode.
GUI mode uninstall can be launched using the following command:
ctguninst -i swing
Console mode uninstall can be launched using the following command:
ctguninst -i console
Unattended uninstall can be launched using the following command:
ctguninst -i silent
This section applies to running the Fix Pack utility which updates an existing installation of the product.
The Fix Pack utility runs in console mode and must be run by a user with root privileges. Before installing or uninstalling the Fix Pack shut down any local CICS TG applications, the Gateway daemon and then the Client daemon.
It is strongly recommended that you shut down all programs running on your system before running the Fix Pack utility.
Change to the directory where the Fix Pack has been unpacked and issue the following command:
ctgfix
The installer will prompt for confirmation before installing. Enter 'y' to proceed. If you do not wish to be prompted for confirmation, issue the command:
ctgfix -y
During installation, the Fix Pack utility creates a log file named <CICS TG install path>/ctgfix/ctgfix.log. The log file contains details of each file that is updated by the Fix Pack, and details of any errors. Further information about the error messages is available in text file ctgfix.hlp located where the Fix Pack has been unpacked.
If the CICS TG is using messages that are not in English, issue the ctgmsgs command to switch to your language of choice:
ctgmsgs XX code_set
For help on the ctgmsgs command, issue the command:
ctgmsgs -?
Change to the <CICS TG install path>/ctgfix directory and issue the following command:
ctgfix -u
The Fix Pack utility will prompt for confirmation before uninstalling. Enter 'y' to proceed. If you do not wish to be prompted for confirmation, issue the command:
ctgfix -u -y
During uninstall, the Fix Pack utility appends to the ctgfix.log file. The log file contains details of each file that is restored by the Fix Pack, and details of any errors. Further information about the error messages is available in text file <CICS TG install path>/ctgfix/ctgfix.hlp.
After installing the Fix Pack, determine the product version by issuing the command:
cicscli -v
Components that have not been updated by this Fix Pack will display the original version.
The supplied version of Java is IBM 31-bit Runtime Environment for Linux on zSeries architecture, Java 2 Technology Edition, Version 5 Service Release 7.
The Java Runtime Environment used with CICS TG is found on the PATH or an alternative Java launcher program can be specified by defining the CTG_JAVA environment variable. For example:
export CTG_JAVA=/opt/ibm/cicstg/jvm15/bin/java
IPIC is supported to CICS TS version 3.2 regions with the following APARS applied :-
When configuring an IPCONN definition in CICS TS for communication with CICS TG, the SENDCOUNT parameter must be set to zero.
In some Telnet sessions, the screen reader might re-read CICS TG log output or the command prompt, after the CICS TG has started. This is expected behavior, and does not mean that the CICS TG has failed to start. To determine if the CICS TG started correctly, listen for the message:
'CTG6512I CICS Transaction Gateway initialization complete'.
If the CICS TG did not start successfully, one of the following messages is output:
'CTG8821E The CICS Transaction Gateway was unable to start the Client daemon'. or 'CTG6513E CICS Transaction Gateway failed to initialize'.
CICS TG does not support Security-Enhanced Linux.
To install and run on RHEL 5 the CICS TG product depends on shared libraries that are not installed by default. The RPMs that contain these libraries are:
libXp-1.0.0-8 compat-libstdc++-296-2.95.3
To use CICS TG on RHEL 5 export the LD_LIBRARY_PATH environment variable to include /opt/ibm/cicstg/lib/stdc++6
The progress bar does not accurately reflect the installation progress.
When installing or uninstalling you need to use uppercase parameters to control the mode. For example:
installer -i SILENT -DLICENSE_ACCEPTED=true
When installing you must ensure gzip is available on the PATH. If gzip is not available you will see messages similar to:
$ ./installer -i console Preparing to install... Extracting the JRE from the installer archive... Unpacking the JRE... gzip not found /tmp/install.dir.467026/AIX/resource/vm.tar.Z: not in compressed format ./installer[581]: gzip: not found The included VM could not be uncompressed (GZIP/UNCOMPRESS). Please try to download the installer again and make sure that you download using 'binary' mode. Please do not attempt to install this currently downloaded copy.
Below is a list of APARs included in this version of the CICS Transaction Gateway. Full details can be found on the support pages: http://www-306.ibm.com/software/htp/cics/ctg/support/
Contact your IBM Support organization for service and updates to the product.
The Program includes "UnZipSFX stub" software from the Info-Zip group which is Copyright (c) 1999-2002, Info-ZIP. All rights reserved. IBM did not modify the UnZipSFX software. There are no extra charges or costs due to the use of this code, and the original compression sources are freely available from http://www.info-zip.org/pub/infozip/ or ftp://ftp.info-zip.org/pub/infozip/ on the Internet.
This product uses the following libraries from the glibc package:
ld.so, libc.so, libm.so, libdl.so, libnsl.so, librt.so and libpthread.so.
Refer to the glibc package on your machine for the various copyright statements and licensing terms for these libraries.
This product also uses libncurses.so from the ncurses package. Again, refer to this package on your machine for the copyright statement and licensing terms applicable to this library.
IMPORTANT NOTE:
Your use of the libgcc or libstdc++ packages will be subject to the GNU GPL licence terms which could require you to provide source code in certain circumstances. In this connection, please bear in mind that IBM will not supply source code, e.g. for the CICS TG C++ libraries.
© Copyright IBM Corporation 2009. All rights reserved.
For legal information, see http://www.ibm.com/legal/copytrade.shtml