|
|
The following topics are discussed in this document.
BEA Tuxedo Mainframe Adapter for TCP 9.1 provides Tuxedo applications transparent non-transactional, request-response connectivity to mainframe-based applications.
The following new features are available in Version 9.1 of the Tuxedo Mainframe Adapter for TCP product:
The following items are included in the Tuxedo Mainframe Adapter for TCP product box:
BEA Tuxedo Mainframe Adapter for TCP 9.1 is supported for the following platforms:
This section describes the minimum hardware requirements for the BEA TMA TCP product.
This section describes the minimum software requirements for the BEA TMA TCP 9.1.
BEA Tuxedo Mainframe Adapter for TCP is designed to work with IBM TCP for MVS stack product. Use the version that is provided with z/OS V1R6.
The following software runs with BEA TMA TCP for IMS:
The following software runs with BEA TMA TCP for CICS:
If you are upgrading to Tuxedo Mainframe Adapter for TCP 9.1 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
BEA Tuxedo Mainframe Adapter for TCP
8.1 Online Documentation.
| Note: | Make certain you have already installed Tuxedo 9.0 or 9.1, which requires you to set up a new directory for the installation. |
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 BEA 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 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
This section describes known problems from previous releases of eLink for Mainframe TCP that have been fixed with the current release of the software. The following table lists a Case or CR (Change Request) number for each problem. Refer to this number to conveniently track the solution as the problems are resolved.
Please contact your BEA Customer Support for assistance in tracking any unresolved problems. For contact information, see the Contacting BEA Customer Support. section.
Documentation for this product is available on the BEA corporate Web site. From the BEA Home page at http://www.bea.com, click on Product Documentation or go directly to the “e-docs” Product Documentation page at http://e-docs.bea.com. The Tuxedo Mainframe Adapter for TCP 9.1 Product Documentation will have a link on the following location:
If you have any questions about this version of Tuxedo Mainframe Adapter for TCP, or if you have problems installing and running Tuxedo Mainframe Adapter for TCP, contact BEA Customer Support through BEA WebSupport at www.bea.com. You can also contact Customer Support by using the contact information provided on the Customer Support Card, which is included in the product package.
When contacting Customer Support, be prepared to provide the following information:
|