Upgrading from Version 8 Release 1

This information details changes that you need to consider when upgrading to the current release from V8.1.

Installation directory

When you upgrade, the installation process keeps your existing <install_path>.

Client log files on Windows

The Client daemon information and error log files are now written in the UTF-8 text encoding on Windows. When using existing log files that were created with an earlier version of CICS® TG, new log messages might appear incorrectly due to the change of text encoding. To avoid this, rename or remove existing Client log files before starting CICS Transaction Gateway, or update your CICS Transaction Gateway configuration to use new Client daemon log files. For more information, see Client daemon logging.

Existing ECI V2 and ESI V2 applications on HP-UX

Existing single threaded ECI V2 and ESI V2 applications on HP-UX that are not explicitly linked with the libpthread shared library must be rebuilt to link with libpthread. Applications that are not linked with libpthread might fail to establish a connection when connecting to the Gateway daemon with the error CTG_ERR_CONNECTFAILED. For more information, see Compiling and linking C and COBOL applications on HPUX.

Java Version 7

The default Java location and defining CTG_JAVA on UNIX and Linux
CICS Transaction Gateway requires the Java 7.0 runtime environment. For more information, see Java runtime environments for core components. The Java 7.0 runtime environment is installed with the product.
The default behaviour of commands ctgadmin, ctgcfg, ctgd and ctgstart has changed. When the environment variable CTG_JAVA is not set, the commands use the Java installed with CICS Transaction Gateway. The previous behaviour was to use the Java found on the PATH. If the environment variable CTG_JAVA is defined you must remove it or you must redefine it to a supported version of Java.
To specify an alternate JVM see, Specifying the JVM.

Removal of Gateway daemon resource parameters

The ecigenericreplies, msgqualvalidation, and uowvalidation parameters are no longer supported. This means that ECI_GET_REPLY and ECI_GET_REPLY_WAIT call types are no longer available in remote mode and message qualifiers and LUW tokens are validated so that they can be used only on the JavaGateway connection to that they were allocated.

If one or more of these parameters are specified in the configuration file, the Gateway daemon ignores the value and startup continues. If you use the Configuration Tool to edit a configuration file that contains any of these parameters, the Configuration Tool removes all instances of the deprecated parameters when the configuration file is updated. If you do not use the Configuration Tool to edit your configuration files, you must manually remove the deprecated parameters from the configuration file.

If any of your applications rely on the deprecated parameters, the following situations occur:
  • Java Client applications running in remote mode that use the ECI_GET_REPLY or ECI_GET_REPLY_WAIT call types receive the ECI_ERR_INVALID_CALL_TYPE error when they flow the request to the Gateway daemon. Java Client applications running in local mode can use ECI_GET_REPLY and ECI_GET_REPLY_WAIT call types.
  • Any remote mode Java Client application that relies on the msgqualvalidation parameter being turned off receives the ECI_ERR_NO_REPLY error when trying to use the message qualifier on a connection that did not start the asynchronous pieces of work.
  • Any application that relies on the uowvalidation parameter being turned off receives the ECI_ERR_LUW_TOKEN error when trying to use the LUW token on a connection that did not start the LUW.

ECI V2 asynchronous call support is unaffected by the deprecation of these parameters.

Removal of ciphersuites=128bitonly parameter

Use of the ciphersuites=128bitonly parameter is deprecated. If you use the Configuration Tool to open a configuration file that contains the ciphersuites=128bitonly parameter, the parameter is replaced by the following list of cipher suites:
  • TLS_RSA_WITH_RC4_128_MD5
  • TLS_RSA_WITH_RC4_128_SHA
  • TLS_DHE_DSS_WITH_RC4_128_SHA

SSL keyring settings moved

The SSL key ring settings are now product wide; they have been moved from the SSL protocol handler in the GATEWAY section to the PRODUCT section of the configuration file. The same SSL key ring settings are used for both SSL protocol handler and IPIC server SSL connection definitions. The SSL key ring parameters must be defined in the PRODUCT section in order to use IPIC over SSL. The definition of the SSL key ring parameters in the GATEWAY section is supported, if not using IPIC over SSL, for migration purposes. The SSL key ring settings are: keyring, keyringpw, and keyringpwscrambled.

TLS cipher suites

Cipher suites entered as TLS are no longer converted to SSL when CICS Transaction Gateway starts.

IPIC server idle timeout default setting

The default setting of the server idle timeout period for IPIC server connections (see Server idle timeout) has been changed to zero, so that the idle timeout period is disabled. Previously, IPIC server connections would be closed if idle for more than 60 minutes. This change affects local mode topologies, and also remote mode topologies which do not configure an IPIC server idle timeout.

Message_Qualifier API removal

The deprecated field Message_Qualifier has been removed from the Java API. Applications that used this field will need to use the getMessageQualifier() and setMessageQualifier() methods instead.

Java client applications using the deprecated field can still connect to CICS TG V9.0 when run in remote mode using a CICS TG V8.1 or earlier ctgclient.jar file


Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tg_latest/help/topic/com.ibm.cics.tg.doc//ctgunx/cclaimig90.html