Release Notes

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Oracle Tuxedo Mainframe Adapter for TCP Release Notes

The following topics are discussed in this document.

 


About Oracle Tuxedo Mainframe Adapter for TCP 12c Release 1

Oracle Tuxedo Mainframe Adapter for TCP 12c Release 1 provides Oracle Tuxedo applications transparent non-transactional, request-response connectivity to mainframe-based applications.

What’s New

The following new features are available in this version of the Oracle Tuxedo Mainframe Adapter for TCP product:

 


Oracle Tuxedo Mainframe Adapter for TCP Platform Support

Oracle Tuxedo Mainframe Adapter for TCP 12cR1 is supported for the following platforms:

Table 1 TMA for TCP Supported Platforms
Platform
IBM AIX 6.1 (64-bit) on IBM PowerPC
Red Hat Enterprise Linux 5.5 (64-bit) x86
Oracle Solaris 10 (64-bit) SPARC

For more information, see Oracle Tuxedo Mainframe Adapter for TCP Certified Platform Tables.

 


Minimum Hardware Requirements

This section describes the minimum hardware requirements for the Oracle TMA TCP product.

 


Oracle Tuxedo Mainframe Adapter for TCP Software Requirements

This section describes the minimum software requirements for the Oracle TMA TCP 12cR1.

Note: Support of TMA on higher releases of z/OS and its subsystems depends on IBM's warranty for the specific upper release's backward compatibility to the release that TMA formally supports. If IBM warrants such backward compatibility to the formally supported release, then the new release can be considered supported.

For more information, see Oracle Tuxedo Mainframe Adapter for TCP Certified Platform Tables.

Oracle Tuxedo Mainframe Adapter for TCP Supported Stacks

Oracle Tuxedo Mainframe Adapter for TCP is designed to work with IBM TCP for MVS stack product.

Oracle TMA TCP for IMS

The following software runs with Oracle TMA TCP for IMS:

Oracle TMA TCP for CICS

The following software runs with Oracle TMA TCP for CICS:

 


Upgrading from eLink TCP 3.x

If you are upgrading to Oracle Tuxedo Mainframe Adapter for TCP 12cR1 from eLink TCP 3.x, perform a new installation of the product. 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 12cR1 (12.1.1), which requires you to set up a new directory for the installation.

Upgrading from eLink TCP 3.x to Support Data-dependent Routing

To support the data-dependent routing, some additional restrictions were 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 information about configuring data-dependent routing using the ROUTING command, refer to the Oracle Tuxedo documentation.

 


Known Problems

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 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 of a 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

 


Fixed Problems

This section describes known problems from previous releases of Tuxedo Mainframe Adapter for TCP that have been fixed with the current release of the software. The following table lists a bug number for each problem.

Bug Number
Description
14109860
TMA ABEND U4038 ASSERTION FAILED: MCB->INPUT->IOLENGTH > 0
13965091
TCP - ADD PATCHLEVEL ATTRIBUTE WINTHIN RELEASE XML ELEMENT OF REGISTRY.XML
13824954
TPELIMIT - A SYSTEM LIMIT HAS BEEN REACHED
10330775
CICS TRANSACTIONS HUNG
10187005
[TMA TCP 9.1]ABEND 0C4 IN MODULE BEATCPI AFTER RECEIVING IMS ERROR MESSAGE


  Back to Top       Previous  Next