Information
Feedback
Last updated: Tuesday, 19 November 2013This information details changes that you need to consider when upgrading to the current release from V8.0.
When you upgrade, the installation process keeps your existing <install_path>.
Existing single threaded ECI 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.
When the environment variable CTG_JAVA is not set, the commands ctgadmin, ctgcfg, ctgd, and ctgstart use the Java that is installed with CICS Transaction Gateway. Previously the Java found on the PATH was used. If the environment variable CTG_JAVA has been defined you must remove it or redefine CTG_JAVA to a supported version of Java. For more information, see Java runtime environments for core components.
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 LUWs 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 fails to start and the CTG8449E error is written to the log file. 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.
ECI V2 asynchronous call support is unaffected by the deprecation of these parameters.
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.
The named pipe protocol for Windows is no longer supported. To enable communication with local TXSeries CICS® systems, replace all named pipe server definitions with TCP/IP server definitions.
The JAR file cicsj2ee.jar file is renamed to cicsjee.jar.
Server names must now use characters from the supported character list 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.
For the list of supported characters, see the relevant page on configuring the server name for the required protocol in Configuring CICS server connections.
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.
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.
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.