Preventive Service Planning
Abstract
This document details the APARs included with CICS Transaction Gateway for Multiplatforms V8.0 and CICS Transaction Gateway Desktop Edition v8.0 releases. Note that fix packs are cumulative and contain fixes for APARs included in previous fix packs.
Content
CICS Transaction Gateway V8.0.0.6
Released: 1st August 2016
| PI59047 | Update CICS TG jar signer certificate |
| PI48306 | Message CCL9126E is written to the Client daemon error log |
CICS Transaction Gateway V8.0.0.5
Released: 29th September 2014
| PI21449 | rc61444 and Gateway object closed after Java client application sends XA_ROLLBACK |
| PI07057 | ctgclient.jar is not signed |
| PM98106 | Errors logged for the TRN component and the Client daemon becomes unresponsive |
| PM95191 | The Client daemon abnormally ends on HP-UX Itanium |
| PM92505 | Starting multiple Client applications simultaneously might cause one or more applications to become unresponsive |
| PM90912* | CICS TG resource adapters do not follow equality rules |
| PM90080 | CICS TG Client daemon abnormally terminates |
| PM88727 | Client connections that time-out might prevent ConnectionManager threads and IPIC sessions being released |
| PM85074 | An ECI request over the IPIC protocol that times out waiting for a response terminates the connection |
| PM82309 | An XA transaction receives a CICS abendAITJ after a normal shut down of the Gateway daemon is requested |
| PM79626 | The CICS TG Client daemon terminates unexpectedly |
| PM79384 | CICS TG Client daemon abnormally terminates with a SIGSEGV |
| PM78952 | Client daemon trace truncates data to a maximum of 9999 bytes |
| PM78681 | CCL9126E Required message queue (key 0xnnnnnnnn) already exists, will not reuse is written to the CICS Client log |
CICS Transaction Gateway V8.0.0.4
Released: 10th December 2012
| PM77227 | CICS TG fails to shut down after an IPIC connection has been closed |
| PM77164 | CCL9126E Required message queue (key 0xnnnnnnnn) already exists, will not reuse is written to the CICS Client log |
| PM73495 | ECI_ERR_INVALID_DATA_LENGTH is returned when flowing a 32767 byte COMMAREA to IPIC connected CICS servers |
| PM70757 | ECI resource adapters describe the SocketConnectTimeout parameter as being defined in seconds rather than milliseconds |
| PM68154 | CICS TG returns XA_OK to a JEE application server while an in-doubt UR remains in CICS |
| PM67722 | Message CTG6638E Container <container> is not data type CHAR is incorrectly written for BIT-type containers |
| PM65292 | Java clients using the SSL protocol cannot connect to the Gateway daemon |
| PM61395 | If an error occurs when an ECIRequest is sent to CICS over IPIC, the commarea content is replaced with nulls |
| PM56086 | Reported values for GD_CLUWTXN and GD_CSYNCTXN statistics are incorrect |
| PM55800 | Client daemon uses 100% of the processor when no requests are being made |
| PM55718 | CICS TG might use Windows Virtual Folders instead of the default location for diagnostic or configuration files |
| PM55717 | Applications cannot write to the default log and trace location |
| PM55657 | Applications using the statistics API to connect to CICS TG might experience continued increases in allocated memory |
| PM55181 | CICS TG does not shut down normally |
| PM51463 | CICS TG statistics for CICS server average response times are incorrect |
| PM51011 | Client daemon ends unexpectedly if a log file is removed while CICS TG is running |
CICS Transaction Gateway V8.0.0.3
Released: 30th September 2011
| PM48238 | Message CCL4523E contains an incorrect return code, and no server name |
| PM48128 | CICS TG retains excessive Java heap storage for idle worker threads, after channel data has been flowed |
| PM47951 | CICS TG fails to shutdown after applications end unexpectedly |
| PM47400 | cicsterm.exe displays message CCL7031E when using the default cicscol.ini file |
| PM47093 | Shutdown statistics are written to the log multiple times during a normal shutdown |
| PM46110 | The CICS TG Client daemon can become unresponsive if a network socket error occurs |
| PM45026 | CICS TG statistics do not provide any information about time taken for remote client network I/O |
| PM40589 | Incorrect return code sent to application after communication failure with CICS during terminal install |
CICS Transaction Gateway V8.0.0.2
Released: 5th August 2011
| PM43183 | Client daemon API component trace entries are not written |
| PM43128 | ECI_ERR_RESOURCE_SHORTAGE reported when sending extended mode ECI requests over an IPIC connection to a CICS server |
| PM42920 | No response to ECI requests sent over an incorrectly configured IPIC connection to CICS |
| PM42005 | CICS TG Client API trace deactivates unexpectedly |
| PM42004* | Connections are not reused during application managed authentication with the CICS TG resource adapters |
| PM41165 | Calls to TransientPayload.getBytes fail with a NullPointerException |
| PM41164 | Enabling a request monitoring exit impacts performance even when the exit performs no work |
| PM40147 | CICS TG incorrectly returns abend AXTG to the client application after the CICS transaction returns an abend AKCC |
| PM39683 | CICS TG does not start when SRVRETRYINTERVAL=0 |
| PM37316 | LUW rollback over IPIC failed after an implicit commit request for the same LUW failed |
| PM37312 | ESI request over SNA fails to complete because the CICS server is unavailable |
| PM37305 | Failing ECI requests prevent CICS TG shutting down |
| PM36641 | ECI timeout requires SPURGE=YES to be set on the mirror transaction in CICS |
| PM34809 | cicsterm support for additional default colors when using a 3270 datastream with extended attributes |
| PM32332 | Message CCL7060I is displayed incorrectly by cicsterm |
| PM30659 | Statistics GD_LAVRESP, GD_IAVRESP and the T1 timestamp from the Request Monitoring Exits are being calculated incorrectly |
| PM29979 | A sample program compiled using the supplied makefile does not run when moved to a different directory |
| PM29332 | Screen representations in a Client daemon trace formatted with the detailed option of cicsftrc might be incorrect |
| PM28832* | CTG9684E XA error 'XAER_PROTO' occurred when processing XA request type 'XA_START' |
| PM28737 | The cicsprnt 3270 terminal emulator does not have an option to enable printing of blank lines |
| PM25156 | CICS TG ends unexpectedly at the statistics interval when more than 256 servers are defined |
| PM24817 | Double-clicking in the cicsterm 3270 terminal emulator resends the previous AID |
| PM23549 | Slow SSL handshakes cause subsequent SSL connection attempts to wait |
| PM23494 | Statistics C API call causes trap in application |
CICS Transaction Gateway V8.0.0.1
Released: 29th October 2010
| PM23319 | Unexpected results when using CICS TG trace |
| PM22622 | ECI requests fail after restart of CICS TG |
| PM22621 | ChannelNameException thrown by Gateway daemon when a zero length channel or container name is used |
| PM22618 | Install is corrupted if the install path contains DBCS characters |
| PM20958 | CICS TG might not generate unique correlators for use with CICS |
| PM20903 | Applications cannot be compiled using Microsoft Visual Studio 2010 |
| PM20895 | Miscellaneous problems when connecting to CICS over IPIC |
| PM20887 | Errors in documentation and messages |
| PM20882 | Miscellaneous problems when using the Java ECI API |
| PM20871 | Miscellaneous problems when running XA transactions |
| PM19800 | Backslash in trace file name prevents memory mapped wrapping trace from starting |
| PM18876 | CICS TG V7.2 ECI resource adapter prevents the use of MappedRecord with COMMAREA applications |
| PM16908 | Send() timeout causes delay in CICS TG processing. |
| PM13698 | The configuration tool allows non-valid log file parameters to be defined, preventing the Gateway daemon from starting |
CICS Transaction Gateway V8.0.0.0
Released: 18th June 2010
| PM10467 | Extended mode ECI requests over IPIC with large containers fail with abend AXTG reported to the client and abend AITJ in CICS |
| PM10466 | CICS TG fails to reconnect to CICS using an IPIC connection and the client application receives an ECI_ERR_NO_CICS |
| PM10465 | When a COMMAREA is returned unchanged by a target CICS program, over an IPIC connection, it contains only nulls |
| PM08404 | A client application becomes unresponsive after specifying an incorrect mirror transaction with a large channel over IPIC |
| PM06919 | NoSuchAlgorithmException thrown during connection to Gateway daemon using SSL protocol |
| PK87193 | Using the statistics and ECI V2 APIs in the same application causes a segmentation fault |
[{"Product":{"code":"SSGMJ2","label":"CICS Transaction Gateway"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Maintenance","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.0.0.6;8.0.0.5;8.0.0.4;8.0.0.3;8.0.0.2;8.0.0.1;8.0","Edition":"All","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21450847