|
|
The following topics are discussed in this document.
Oracle Tuxedo Mainframe Adapter for TCP 12c Release 2 (12.1.3) provides Oracle Tuxedo applications transparent non-transactional, request-response connectivity to mainframe-based applications.
The following new feature is available in this version of the Oracle Tuxedo Mainframe Adapter for TCP product:
Besides single-byte character set (SBCS) character set translation, Oracle Tuxedo Mainframe Adapter for TCP supports multibyte character set (MBCS) translation. This feature allows translation among more than 200 different SBCS and MBCS character sets.
For more information, see Using Multibyte Character Set (MBCS) Translations in Oracle Tuxedo Mainframe Adapter for TCP Gateway User's Guide.
Oracle Tuxedo Mainframe Adapter for TCP 12c Release 2 (12.1.3) is supported for the following Oracle Tuxedo releases:
For more information, see Oracle Tuxedo Mainframe Adapter for TCP Supported Platforms, Hardware Requirements, and Software Requirements in Installing the Oracle Tuxedo Mainframe Adapter for TCP.
If you are upgrading to Oracle Tuxedo Mainframe Adapter for TCP 12c Release 2 (12.1.3) from eLink TCP 3.x, perform a new product installation. You will need to edit the UBBCONFIG, DMCONFIG, and GWICONFIG files. Refer to configuration information in the
Oracle Tuxedo Mainframe Adapter for TCP Online Documentation.
| Note: | Make certain you have already installed Tuxedo 12c Release 2 (12.1.3), which requires you to set up a new directory for the installation. |
To support data-dependent routing, some additional restrictions are placed on the contents of the GWICONFIG file.
In prior releases, no restrictions were placed on the naming of the entries in the NATIVE and FOREIGN sections of the GWICONFIG file. Beginning with the eLink TCP 3.2, each entry in the NATIVE section of the GWICONFIG files must have a corresponding entry with an identical name in the DM_LOCAL_DOMAINS of the DMCONFIG file. Each entry in the FOREIGN section of the GWICONFIG file must have a corresponding entry with an identical name in the DM_REMOTE_DOMAINS section of the DMCONFIG file.
Because service routing is now determined by the contents of the DMCONFIG file, services in the LOCAL_SERVICES section of the GWICONFIG file no longer need to be tied to NATIVE entries in that file. As a result, the NATIVE keyword is no longer valid for entries in the LOCAL_SERVICES section. Services are now tied to local domains in the DMCONFIG file, by specifying the corresponding LDOM in the service entry in the DM_LOCAL_SERVICES section, or by applying default service assignment rules.
For the same reasons, services in the REMOTE_SERVICES section of the GWICONFIG file no longer need to be tied to FOREIGN entries in that file. As a result, the FOREIGN keyword is no longer valid for entries in the REMOTE_SERVICES section. Services are now tied to remote domains in the DMCONFIG file by specifying the corresponding RDOM in the service entry in the DM_REMOTE_SERVICES section, or by using a routing statement to specify data-dependent routing, or by applying default service assignment rules. For more information, see Oracle Tuxedo documentation.
The JCL provided for linking the CICS requester (LNKIBM, LNKINT) may cause problems on some system configurations. In IBM APARs II10227 and PQ19993, it is recommended that when linking with the SEZACMTX and SCEELKED libraries, SEZACMTX be placed ahead of SCEELKED in the SYSLIB statements, as follows:
//SYSLIB DD ...
// DD DSNAME=hlq.SEZACMTX,DISP=SHR
// DD ...
// DD DSNAME=hlq.SCEELKED,DISP=SHR
// DD ...
The JCL provided does not conform to this recommendation. You may need to edit the provided JCL before linking the requester, as shown in the following example SYSLIB section:
//SYSLIB DD DSN=CICS.SDFHLOAD,DISP=SHR
// DD DSN=&TCPLIB,DISP=SHR
// DD DSN=SYS1.SEZACMTX,DISP=SHR
// DD DSNAME=SYS1.SCEELKED,DISP=SHR
This section describes known problems from previous releases of Tuxedo Mainframe Adapter for TCP that have been fixed in the current release. The following table lists a bug number for each problem.
|