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 must be run in a command prompt window by a user with administrator 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
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 a user with Administrator authority and for Windows Vista, elevated authority is required.
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 IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 5 Service Release 4.
To install the Java Runtime Environment, run the command:
ibm-java2-jre-50-win-i386.exe
During Java Runtime Environment installation, you can select to install this Java as the system default. If you choose not to install this Java as the system default, you must run the ctgjava.exe command to specify where the Java executable is located.
The use of CICS TG is only supported running in a user session.
Fast User Switching is not supported while the CICS TG product is running.
TCP62 Communications and Named Pipe Communications are not supported on Windows Vista.
The C++ API is not supported on Windows Vista.
When a machine is being upgraded from a previous version of Windows to Windows Vista, the CICS TG product must be uninstalled prior to the Windows upgrade.
The minimum level of Java required for running CICS TG on Windows Vista is Service Release 4 of IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 5.
To configure java for CICS TG the ctgjava utility must be invoked from an elevated command prompt.
On Windows Vista systems the CICSCLI environment variable must be used to name the configuration file. Create the directory specified in the CICSCLI environment variable if it does not exist. The CICSCLI environment variable must be defined for any user who starts or configures the CICS TG product. When setting the CICSCLI environment variable at a Windows command line, Windows auto-completion adds double quotes around the path value. The double quotes must be removed, for example:
CICSCLI=C:\ProgramData\IBM\CICS Transaction Gateway\ctg.ini
Log and trace files for the Gateway and Client daemon processes must be defined with a fully qualified file name, for example:
C:\ProgramData\IBM\CICS Transaction Gateway\cicscli.log
The user who starts the CICS TG product must have write access to the log files.
The ports required by the CICS TG network protocol drivers must be available to the user who starts the CICS TG product. Configuring the system Firewall requires elevated access.
If the startup type for the Client daemon service is not automatic, the first request made by an application will attempt to start the service. Starting a service requires administrator authority, so the attempt will fail if ctgstart is run by a user ID that does not have administrator authority.
A utility to change the permissions for the Client daemon service is included with CICS TG. The utility and accompanying documentation are installed as:
<install_path>\bin\resource\cs70.exe <install_path>\bin\resource\cs70readme.txt
Pop-up message windows are now disabled by default.
To enable pop-up message windows, open the Windows Services control panel and check the 'Allow service to interact with desktop' box on the 'Log on' tab of the properties box for the "IBM CICS Universal Client" service. Also run the Configuration Tool to edit ctg.ini and select the 'Enable pop-up windows' field on the Client daemon resources panel.
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.
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 upgrading from earlier versions of the CICS TG the installer program does not display progress correctly; ignore the progress display. The installation is unaffected by the incorrect progress display.
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
When using a response file to uninstall silently, the response file must be given a fully qualified file name.
When the installer or uninstaller program is cancelled on Windows Vista the 'Program Compatibility Assistant' will start. Select 'The program installed correctly' to cancel the assistant.
Below is a list of APARs included in this version of the CICS Transaction Gateway. All APARs listed are applicable to this platform. 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.
© Copyright IBM Corporation 2009. All rights reserved.
For legal information, see http://www.ibm.com/legal/copytrade.shtml