Items that you need to consider when upgrading to a newer version of CICS® Transaction Gateway on Windows.
When you upgrade, the installation process keeps your existing <install_path>.
The CICS Transaction Gateway now runs as a single service on all supported Windows operating systems. Messages associated with running the CICS Transaction Gateway as a service are written to the Application and System sections of the Windows Event log.
The Gateway daemon always runs as a Windows service and it is no longer possible to operate the Gateway daemon in console mode. The ctgstart command is removed from the product and the ctgadmin command is extended to support starting the Gateway daemon.
The default location of configuration, log and trace files is changed from <install_path>/bin to <product_data_path>. The installer automatically moves configuration files from <install_path>/bin to <product_data_path>. For more information see File path terminology
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 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.
ECI V2 asynchronous call support is unaffected by the deprecation of these parameters.
The named pipe protoco is no longer supported. To enable communication with local TXSeries CICS systems replace all named pipe server definitions with TCP/IP server definitions.
On Windows LUALIASNAMES is replaced by LOCALLUALIAS and PARTNERLUALIAS.
If LUALIASNAMES is found in the configuration file after upgrade, the Client daemon attempts to start the SNA Server connection and generates a warning in the Client daemon log file indicating that the deprecated entry LUALIASNAMES exists.
The releases of CICS Transaction Gateway V7.0 and CICS Universal Client V7.0 are the last releases that contained TCP62 support for the AnyNet® protocol communicating with remote CICS systems using SNA over TCP/IP protocol encapsulation. Accordingly, this capability is removed from the V7.1 level of the products. For continued use of SNA over TCP/IP, it is necessary to move TCP62 server definitions to SNA and implement another IBM® Communications Server TCP/IP protocol encapsulation solution, such as Enterprise Extender or Remote API client support.
For information about moving from TCP62 to Enterprise Extender support refer to the IBM publication Migrating an SNA connection from TCP62 to Enterprise Extender - GC34-6889-00.
For information about the removal of AnyNet support from z/OS® Communications Server, refer to the z/OS and z/OS statements of direction announcement, Software Announcement 203-266, dated October 7, 2003, and the z/OS V1.7 preview announcement, Software Announcement 205-034, dated February 15, 2005.
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 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.