CICS® Transaction
Gateway includes enhancements in the areas of high availability, monitoring,
open integration, security, and user information.
Functional enhancements
- An ECI timeout value can be set on IPIC server
definitions in the CICS Transaction
Gateway configuration file. This enables applications, that do not
specify a timeout value, to be timed out when connected to CICS over IPIC. For
more information, see ECI timeout.
- All ECI V2 and ESI V2 functions can now be used by 64-bit applications
as well as by 32-bit applications. For more information, see CICS TG ECI and ESI Version 2 for
C Overview.
- ECI V2 applications now allow multiple threads to share a single
Gateway connection when using synchronous calls.
- ECI V2 has been enhanced with the addition of asynchronous call
support, for more information, see Making
ECI V2 and ESI V2 calls from C programs.
- Local mode JEE and Java™ applications
can now set the maximum number of send sessions that are used with
IPIC connections to CICS. The
number of send sessions controls the number of simultaneous requests
that are allowed over the connection. For more
information see, Configuring
IPIC in local mode.
High availability
- Client application IP addresses are now available for use in CICS request exits. The IP address
information can be used in your CICS request
exit routing decisions, for example. For more
information about CICS request
exits, see Writing a CICS request
exit.
Monitoring
- You can use Cross Component Trace (XCT) to track individual requests
as they flow from WebSphere® Application
Server to CICS and back, making
it easier to identify the responsible component when failures occur.
XCT can be enabled for applications using the ECI resource adapter
in WebSphere Application
Server V8.5 or later. For more information,
see Transaction tracking
with Cross Component Trace (XCT).
- Request monitoring exits in the Gateway daemon have been extended
to include an exit that reports the actual target CICS server for a request. A new exit point,
RequestDetails, is called after any DSS routing decisions have been
made but before the request is sent to CICS.
For more information, see Java request monitoring exits.
- You can now record statistics data from CICS Transaction Gateway to a statistics
log file at predefined intervals. For more information,
see Recording statistics
to a file.
- Channel and container information is now available to Java request monitoring exits for ECI requests
that have an associated channel. For more information, see Data available by
FlowType and RequestEvent.
Globalization
- CICS Transaction Gateway
has been updated to support right-to-left bidirectional (bidi) data
in containers. For more information see Bidirectional data support.
- cicsterm on Windows has been enhanced to display bidi
data in BMS maps.
For other changes from previous releases see the
Upgrading section.