The product documentation is provided as an Eclipse Information Center available at: http://publib.boulder.ibm.com/infocenter/cicstg/v7r0m0/index.jsp
This file contains important information about the IBM CICS Transaction Gateway (CICS TG) that might not be available in the Eclipse Information Center.
This readme file is available in plain text and HTML. Both files contain the same information. After installation the files are included in the <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 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.
Installation and uninstallation must be done by the root user.
Before you install, 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.
This section is an aid for installation, the following details list the commonly used options. More information on how to use the installer can be found in the section "Known issues during installation or uninstallation" and the Eclipse Information Center.
To install the CICS TG launch the InstallShield wizard:
installer
To install the CICS TG in console mode launch the InstallShield wizard with the -console option:
installer -console
To install the CICS TG with no user interaction launch the InstallShield wizard with the -silent and -V licenseAccepted options:
installer -silent -V licenseAccepted=true
The supplied version of Java is HP 32-bit Runtime Environment for J2SE HP-UX 11i platform, adapted by IBM for IBM software, Version 5 Service Release 4.
Create a directory for the Java Runtime Environment files to be extracted to. Expand and extract the Java Runtime Environment from the package file into this new directory. The following example uses the Java default location:
mkdir /opt/java1.5 cd /opt/java1.5 gzip -cd <package_path>/hpia32devhybrid-20070125-jre.tar.Z | tar -xvf -
After installing the Java Runtime Environment read the Java documentation for guidance on how to define the PATH and other environment variables.
Reference documentation for the statistics API is included in the information center. The documentation is also included as part of the CICS TG installation, in <install_path>/docs/ctgstatsdoc.zip. To view the documentation, expand the contents of the ZIP file into a suitable directory and view file 'index.html' with a Web browser.
Cipher suites define the key exchange, data encryption, and hash algorithms used for a SSL session between a client and server. During the SSL handshake both sides present the cipher suites they are able to support and the strongest one common to both sides is selected. This new feature allows you to restrict the cipher suites that a Java Client application presents.
To restrict the cipher suites used by a JavaGateway object, use the setProtocolProperties() method to add the property (JavaGateway.SSL_PROP_CIPHER_SUITES) to the properties object passed to the it. The property's value must contain a comma-separated list of the cipher suites that the application is restricted to using. For example:
Properties sslProps = new Properties();
sslProps.setProperty(JavaGateway.SSL_PROP_KEYRING_CLASS, strSSLKeyring);
sslProps.setProperty(JavaGateway.SSL_PROP_KEYRING_PW, strSSLPassword);
sslProps.setProperty(JavaGateway.SSL_PROP_CIPHER_SUITES,
"SSL_RSA_WITH_NULL_SHA");
javaGatewayObject = new JavaGateway(strUrl, iPort, sslProps);
In the WebSphere Administration console, change the "CipherSuites" custom property for the connection factory to a comma-separated list of the cipher suites that this connection factory is restricted to use.
All C++ applications must be compiled with the -AP flag in order to run successfully with the CICS TG. Example:
aCC -AP -DCICS_HPUX file.cpp
TCP62 is not supported by the CICS Transaction Gateway on HP-UX on Itanium.
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, this message is output:
'CTG6513E CICS Transaction Gateway failed to initialize'.
When installing with the graphical user interface the installer program may stop responding. If this problem occurs, issue "Ctrl C" to end the installer program and retry the installation using the "-console" option.
If you create a response file using the installer "-options-record" option with the "Custom" installation selected, you must modify the file before you use it. Find the line:
-W setupTypes.selectedSetupTypeId=custom
and replace it with:
-W setupTypes.active=false
If you do not modify the response file before use, all features will be installed.
When installing silently the license must be accepted, this is done with the -V option. The following command is for silent installation with a recorded response file.
installer.exe -options "response_file_name" -silent -V licenseAccepted=true
If the uninstallation is not performed by a user ID with root privileges, the uninstallation fails, and the following error might be output to the console.
"engine is missing (/InstallShield/Universal/common/Gen1):"
The CICS TG must be uninstalled by a user with root privileges.
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.
© Copyright IBM Corporation 2009. All rights reserved.
For legal information, see http://www.ibm.com/legal/copytrade.shtml