Upgrading from Version 7 Release 1

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

Configuration files

CICS® Transaction Gateway configurations that worked with previous releases might not work after upgrade. Configuration checking is enhanced to ensure that the values used by CICS Transaction Gateway are the intended ones. Protocol handlers are not started unless explicitly configured.

The Configuration Tool is removed from this version of CICS Transaction Gateway for z/OS®. To assist in configuring CICS Transaction Gateway additional scenario configuration files are provided. For more information, see Scenarios.

Java Version 7

Ensure the PATH environment variable in the STDENV file used during CICS TG initialization contains the location of the IBM® Java™ 7 runtime environment.

Removal of Gateway daemon resource parameters

The uowvalidation parameter is longer supported. This means that LUWs tokens are validated so that they can be used only from the client application connection from which the LUW was started.

If the uowvalidation parameter is specified in the configuration file, the Gateway daemon fails to start. You must remove the uowvalidation parameter from the configuration file.

If any of your applications rely on the uowvalidation parameter being turned off, the application receives the ECI_ERR_LUW_TOKEN error when trying to use the LUW token on a connection, to the Gateway daemon, that did not start the LUW.

Upgrading a statistics API port definition

If you configured a statistics API port defined by a statsport parameter in the GATEWAY section of your configuration file, upgrade to using a full statistics API protocol handler definition.

Previous releases of CICS Transaction Gateway bound the statistics API port exclusively to localhost. These monitoring applications were restricted to running on the same machine as the Gateway daemon. If you define a full statistics API protocol handler the remote monitoring applications can connect to the Gateway daemon. See Statistics API protocol settings for details on remote statistics API connections.

Upgrading XA configurations

When you upgrade from Version 7 Release 1 and were previously using XA support over IPIC connections without using CTGRRMS you must enable CTGRRMS.

Determine whether you are using CTGRRMS by checking the xasupport parameter in the Gateway daemon configuration file.
  • If xasupport=off, or if the configuration file does not contain the xasupport parameter, no upgrade steps are needed and the CICS Transaction Gateway will work as it did before the upgrade.
  • If xasupport=on, you are using XA and you must follow the upgrade steps. For more information see Configuring XA support.

When you enable XA support, check the Gateway daemon log for message CTG6737I which indicates that XA support is enabled.

When you upgrade from Version 7 Release 1 or earlier, if you have a Gateway daemon configuration using XA support, you must change the configuration settings. For more information see Upgrading XA configurations.

Using the JEE interfaces in nonmanaged mode

The JAR file cicsj2ee.jar file is renamed to cicsjee.jar.

Supported characters in server names

Server names must now use characters from the supported character list (see Server name) to ensure that all CICS TG functions work correctly. Existing configuration files containing server names using unsupported characters can continue to be used as an aid to migration but might not work in all scenarios. Configuration files containing server names that use unsupported characters should be migrated as soon as possible.

IPIC server idle timeout default setting

The default setting of the server idle timeout period for IPIC server connections 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.

Removal of ciphersuites=128bitonly parameter

Use of the ciphersuites=128bitonly parameter is deprecated.

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: esmkeyring, hwcrypt, keyring, keyringpw, and keyringpwscrambled. The esmkeyring and hwcrypt parameters now take a parameter value when defined in the PRODUCT section.

TLS cipher suites

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

Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tgzos_latest/help/topic/com.ibm.cics.tg.zos.doc//ctgzos/cclaimig72.html