IBM CICS Transaction Gateway Version 7.2.0.2 - README for Windows

IBM CICS Transaction Gateway Version 7.2.0.2 - README for Windows

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.

SUMMARY OF TOPICS

INSTALLING AND UNINSTALLING THE FULL PRODUCT

This section applies to running the full product installer which either installs the product or replaces an existing version of the product.

Installation and uninstallation must be done by a user with Administrator authority and for Windows Vista, elevated authority is required.

Ensure that the Application Event Log is closed prior to installing 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.

INSTALLING THE FULL PRODUCT

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

Using the unattended installation can result in the machine restarting without warning.

UNINSTALLING THE FULL PRODUCT

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.

If uninstall is started from the Add/Remove programs panel it will run in GUI 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

INSTALLING AND UNINSTALLING A FIX PACK

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.

INSTALLING THE FIX PACK

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 -?

UNINSTALLING A FIX PACK

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.

DETERMINING THE PRODUCT VERSION

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 version of IBM CICS Transaction Gateway displayed by Windows in the list of currently installed programs, remains as the original installed version.

CONFIGURING THE JAVA RUNTIME ENVIRONMENT

The supplied version of Java is IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 5 Service Release 7.

After installing CICS TG to a new system, open a new command prompt and run the ctgjava command to specify which Java Runtime Environment is to be used with CICS TG. For example:

ctgjava -s="C:\Program Files\IBM\CICS Transaction Gateway\jvm15\bin\java.exe"

LIMITED SUPPORT FOR WINDOWS VISTA

The CICS TG does not run as a Windows service on Vista. For further information refer to the Information Center.

USING THE CONFIGURATION TOOL WITH TURKISH

To open a configuration file with an extension of 'ini' using the configuration tool you must set the filter to 'All Files' in the open file dialog.

CICS TS SUPPORT FOR IPIC

IPIC is supported to CICS TS version 3.2 regions with the following APARS applied :-

CICS TS APARS REQUIRED FOR IPIC SUPPORT

PK85173
Using CTG with IPIC a DPL program runs in the AOR under tranid CSMI when defined with a specific tranid (XXXX)

PK65134
Per-transaction shunting causes transaction rollback

PK57726
XA Recovery fails with security enabled. Abend AIPJ in DFHISRE when CICS Transaction Gateway v7.1 issues resync request over IPIC

PK55716
Resync XID data incorrectly sent by CICS TS 3.2 to the CICS Transaction Gateway when using IPIC connections

PK55495
Incorrect recording of partner in same sysplex

PK55494
Security exposure using IPCONN USERAUTH(IDENTIFY)

PK53783
Data conversion codepage(-1) not done when calling CICS TS over IPIC

PK51587
Message DFHIS1027 security violation from z/OS CICS using CICS Transaction Gateway

PK49490
Invalid container data returned on DPL from CTG

PK49116
Protocol IPIC requires TCP keepalive to be set

PK49021
Sending a bit container with CCSID=0 on a DPL with channel causes AITJ abend

PK49017
Multiple SYNCONRETURNS over IPIC connection from single task fails TERMERR, RESP2=17

PK49015
CIST transaction hangs during drain processing of one-way IPCONN resources

CONFIGURING AN IPIC CONNECTION

When configuring an IPCONN definition in CICS TS for communication with CICS TG, the SENDCOUNT parameter must be set to zero.

TXSERIES SUPPORT FOR IPIC

IPIC is supported to TXSeries version 7.1 regions with Fix Pack 1 applied.

USING THE J2EE CICS RESOURCE ADAPTERS WITH NONMANAGED APPLICATIONS

Outside a J2EE environment, you must ensure that the following Java extensions are available:

* JAAS (required for EPI resource adapter). 
* JCA 1.5 Connector class file (required for ECI resource adapter)
* Java Transaction API (required for XA transactions)

Note: JAAS is included with IBM JREs and JDKs by default. The JCA 1.5 Connector class file and the Java Transaction API (JTA) libraries are available for download from the Sun Java Web site.

ACCESSIBILITY FEATURES

STARTING THE GATEWAY DAEMON FROM A COMMAND PROMPT USING A SCREEN READER

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'.

KNOWN ISSUES DURING INSTALLATION OR UNINSTALLATION

CANCELLING AN INSTALL OR UNINSTALL ON WINDOWS VISTA

When the installer or uninstaller program is cancelled on Windows Vista the 'Program Compatibility Assistant' starts. Select 'The program installed correctly' to cancel the assistant.

PROGRESS BAR

The progress bar does not accurately reflect the installation progress.

TURKISH

When installing or uninstalling you need to use uppercase parameters to control the mode. For example:

installer -i SILENT -DLICENSE_ACCEPTED=true

RUNNING AS A WINDOWS SERVICE

Read this if you are running CICS TG as a Windows service and need to change the default port for local administration (adminport).

The CICS TG default adminport is 2810. You might need to change this if this port is used by another application. However, running CICS TG as a service on Windows with a non-default adminport, can cause the service to become unresponsive during shutdown. To avoid this problem, before starting the service issue the command:

ctgservice -R -A-adminport=<new port number>

This updates the CICS TG service registry entry with the new port number. Starting and stopping the service will then use the new port number.

SERVICE AND UPDATES

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/

APARS INCLUDED IN 7.2.0.2

PM06643
Message CCL4406E is written to the client error log when a CICS server becomes unavailable

PM03933
Message CCL3102E written to the client error log file when running a heavy workload

PM03931
CICS TG writes messages CCL3315E and CCL3227E to the client error log after transactions have timed out or abended

PM03923
CICS TG returns excess data when using an IPIC connection to CICS

PM02683
NoClassDefFoundError when using nonmanaged application with CICS TG resource adapters

PM01321
Reinstallation of version 7.2.0.1 of the CICS Transaction Gateway leaves the installed JVM in an inconsistent state

PM00653
CICS TG attempts to process incorrect TCP/IP data as a normal request

PK99781
CTIN fails to reconnect to a CICS server after a CICS restart

PK98202
CICS TG causes exception in TXSeries when using multiple containers

PK97502
Using the getStats() API causes an access violation if a large number of CICS servers have been defined

PK96066
When using IPIC, an ECI request routed to a remote CICS server runs under the default mirror transaction ID

PK95506
ECI State requests fail with ECI_ERR_INVALID_EXTEND_MODE

PK94211
CICS Client daemon terminates unexpectedly with message CCL2010 Error code -5010

PK91072
CICS TG fails to start when TCP/IP localhost is not defined.

PK89359
Multiple instances of message CCL1048E written to the Client error log, reporting error code -4 from FaarqGetMsg.

PK89000
Servername can not contain ':','/' OR '#' characters. Results in error CTG6670E Invalid chars in APPLID for ISC connection

PK88875
CICS TG trace cannot be filtered and trace overhead might be unacceptable in some environments

PK88549
Improve serviceability of IPIC protocol handler

PK86470
A server definition containing the workload manager parameter "REGION" prevents the Gateway daemon from starting.

APARS INCLUDED IN 7.2.0.1

PK68975
CICS TG log file not written to specified destination

PK71172
Moving a container between channels in CICS causes the CICS TG to ignore the modified container

PK76390
Client daemon issues CCL2012E after CICS abends a transaction

PK76458
Terminal definitions are not released in CICS if an emulator terminates when the Client daemon is at MAXREQUESTS

PK78014
ECI requests do not complete if a connection to a CICS server fails to be properly established

PK78293
Modified data tag reset on some EPI screens

PK78747
Documentation for IPIC parameters is unclear for local mode

PK81606
IPIC connections fail when the CICS server does not support some capabilities

PK82305
Improve diagnostic information available when a signal occurs in the Client daemon

PK82618
Multiple CCL0200I opened log file messages are written to the Client daemon error log

PK82680
CICS TG installation issues

PK82695
Some CICS TG statistics are incorrectly reported

PK82697
Invalid chars in APPLID for ISC connection reported when backslash characters are used in the IPIC URL

PK82698
Errors in messages when CICS Transaction Gateway starts.

PK82700
Requests with invalid extend mode values return ECI_NO_ERR instead of ECI_ERR_INVALID_EXTEND_MODE

PK82702
The Gateway daemon fails to start and returns message CTG6765E on 64 bit Linux distributions

PK82703
Channel problems when using CICS TG with IPIC connections to CICS servers

PK82711
IPIC container data corruption at 122750 bytes

PK82715
Incorrect errors reported by CICS TG when starting an SNA connection to CICS

PK82718
CICS TG reports errors on TCP/IP connections to CICS servers

PK83549
Short mirror transaction names fail over IPIC

PK84008
Improvements to IPIC support

PK84010
Some CICS TG Gateway daemon statistics are not correct

PK84012
Cannot enable trace for ECI V2 API without changing the client application

PK84013
STATSPORT override is ignored when APPLID override is also specified

PK84014
Improvements to CICS TG ECI V2

PK84028
Request Monitoring Exits do not contain timestamp data for XARollback flows

PK85494
CICS TG does not reconnect to a CICS server when the link between a SNA client and Communications Server is lost

PK85498
Access violation in cclclnt.exe when running an EPI workload and the CICS server becomes unavailable

PK85534
ECI Version 2 version parameter is not verified

PK85535
Statistics C API OpenGatewayConnection call fails on Solaris 9

APARS INCLUDED IN 7.2.0.0

PK72228
The Client daemon terminates unexpectedly with CCL2010E Internal transport error (Function = 'FaarqPutMsg', Error Code = '-5010')

PK70913
CICS Client trace function not able to track when CICS_EPITERMINATE call exits

PK69017
ECIConnection.close() Javadoc incorrectly states when a ResourceException will be thrown

PK69840
Client daemon appears to become unresponsive during startup

PK66744
CICSPRNT inserts an extra space between single byte and double byte characters causing printing errors

Contact your IBM Support organization for service and updates to the product.

THIRD PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

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 2010. All rights reserved.
For legal information, see http://www.ibm.com/legal/copytrade.shtml