This script opens a new, small, floating window and puts TOC<name>.html and IX<name>.html files in it and sets a generic popup window code to enable the display of some viewlets in the WebLogic Platform Tour.
Skip navigation.

Tuxedo Mainframe Adapter for TCP 8.1 Documentation > Release Notes > BEA Tuxedo Mainframe Adapter for TCP Release Notes

Release Notes

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF  
Get
Adobe Reader

BEA Tuxedo Mainframe Adapter for TCP Release Notes

BEA Tuxedo Mainframe Adapter for TCP Version: 8.1
Date: November 2003

The following topics are discussed in this document.

 

About Tuxedo Mainframe Adapter for TCP 8.1

BEA Tuxedo Mainframe Adapter for TCP 8.1 provides Tuxedo applications transparent non-transactional, request-response connectivity to mainframe-based applications.

What's New

The following new features are available in Version 8.1 of the Tuxedo Mainframe Adapter for TCP product:

Dropped Feature Support

The following features are not supported in Version 8.1 of the Tuxedo Mainframe Adapter for TCP product:

Product Packaging

The following items are included in the Tuxedo Mainframe Adapter for TCP product box:

 

BEA Tuxedo Mainframe Adapter for TCP Platform Support

BEA Tuxedo Mainframe Adapter for TCP 8.1 is supported for the following platforms:

Platform

ATMI Platform Version

IBM AIX 5.2

Tuxedo 8.1

HP-UX 11.00 (32 bit) PA-RISC

Tuxedo 8.1

SUN Solaris 8 (32 bit on 64 bit Sparc)

Tuxedo 8.1

Microsoft Windows 2000 Advanced Server

Tuxedo 8.1


 

 

Minimum Hardware Requirements

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

 

BEA Tuxedo Mainframe Adapter for TCP Software Requirements

This section describes the minimum software requirements for the BEA TMA TCP 8.1.

BEA Tuxedo Mainframe Adapter for TCP Supported Stacks

BEA Tuxedo Mainframe Adapter for TCP is designed to work with IBM TCP for MVS stack product. Use the version that is provided with OS/390 V2R10 or z/OS V1R4.

BEA TMA TCP for IMS

The following software runs with BEA TMA TCP for IMS:

BEA TMA TCP for CICS

The following software runs with BEA TMA TCP for CICS:

 

Installing Your Software License

You must enter the license key for Tuxedo Mainframe Adapter for TCP software to enable the connection capabilities for your system. As a prerequisite, BEA Tuxedo must be installed and operational with its license key file available. To enable the Tuxedo Mainframe Adapter for TCP license key, you must append the license key file provided with the product software to the BEA Tuxedo license key file.

Caution: Do not alter any information within sections of the license key files. Doing so may disable your product software.

Perform the following steps to use the license key.

  1. With the text editor of your choice, open the Tuxedo license key file in $TUXDIR/udataobj/lic.txt. An example of this file follows:

Listing 1 Sample BEA Tuxedo License Key File

  1. Append the Tuxedo Mainframe Adapter for TCP license key file to the Tuxedo license key file. An example of the Tuxedo Mainframe Adapter for TCP license key follows:

Listing 2 Sample TMA TCP License Key File


  
[TMATCP v8.1]
LICENSEE=*** BEA SYSTEMS *** 
SERIAL=8882327878
ORDERID=N/A
EXPIRATION=2004-10-20
SIGNATURE=xxx
  1. Save the file and exit the text editor. Your license key is now in effect.

 

Upgrading from eLink TCP 3.x

If you are upgrading to Tuxedo Mainframe Adapter for TCP 8.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 8.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 BEA 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 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.

1

CR080971

Large message hangs in OTMA/IMS.


Problem

The client sends a transaction to IMS via TMA TCP for IMS on the mainframe. The transaction processes and creates a large message that exceeds the 64K limit and causes the message to hang in IMS.


Platform

OS/390

2

CR102475

s0c4 abend in OTMAGET module.


Problem

Problem with multisegment message causing abend in OTMAGet () function.


Platform

OS/390


 

 

Where to Get Product Documentation

Documentation for this product is available from the following locations:

Using the Tuxedo Mainframe Adapter for TCP Online Documentation

You can install the HTML files on your server or client, or leave them on the CD. If you copy the files to your system, you should maintain the directory structure that was provided on the CD. However, you can move that directory structure to any location. The files are located on the CD-ROM in the docs/tuxedo/tcp/v81 directory. Note the pathname for the directory where you install them on your server or client.

The documentation CD includes a Java search applet to help you find TMA TCP topics in the documentation. To use the search capabilities, your browser must have Java support enabled. For information on limitations of the search capabilities, see Documentation Search Applet Limitations.

To view the documentation, you need a Web browser that supports HTML 4.0 features including tables and frames. Netscape Navigator 7.0 or later or Microsoft Internet Explorer 6.0 or later are recommended. When you install the HTML files, they will be located in a directory on your system. You should keep the HTML files that are contained within a directory together. However, you can move that directory to any location.

Note: It is recommended that you locate the HTML browser and the HTML files on the same client or server device.

Accessing the Documentation

To begin viewing the online documentation, use one of the following methods to open the HTML file in a Web browser:

On UNIX systems, you may need to mount the CD before you are able to access the index.htm page. For mounting instructions on UNIX platforms, refer to the installation instructions in the Tuxedo Mainframe Adapter for TCP CD-ROM.

Printing the PDF File

You must have the Adobe Acrobat Reader to view and print the PDF file. If you do not have this reader, you can obtain it free of charge from the Adobe Systems Incorporated Web site at www.adobe.com. (Please note that the Tuxedo Mainframe Adapter for TCP Documentation home page contains a link to this site.)

Printing from the Web Browser

You can print a copy of this document, one file at a time, from the Web browser. Before you print, make sure that the topic you want is displayed and selected in your browser. (To select a topic, click anywhere inside the frame you want to print. If your browser offers a Print Preview feature, you can use the feature to verify the topic you are about to print.)

Documentation Search Applet Limitations

The documentation CD includes a Java search applet to help you find Tuxedo Mainframe Adapter for TCP topics. The following sections describe current limitations with the search applet.

Special Characters

The search applet does not find strings containing some special characters, such as slashes(/) and/or dollar signs ($). The Java search applet does find strings containing underscores (_) and periods (.). Attempts to search for strings with unsupported special characters result in a "No matches" message.

The Java search applet uses a precompiled search database of topics. Because of the way the search database is built, you must adhere to one of the following options to use the CD search feature:

You cannot use the search applet if you have accessed the CD or a copy of its content through a Universal Naming Convention (UNC) path. For example, UNC paths are used by the Windows NT Network Neighborhood. The search applet does not interpret relative paths to the matched target *.htm pages because the UNC path is added to the beginning of each link. To use the CD search feature, please use one of the four recommended methods listed earlier in this section.

Only the search applet's results list is affected by this UNC limitation. You can use UNC paths, such as accessing the CD on a Network Neighborhood system's shared CD device, for all other relative hyperlinks on the CD.

Additional Search Tip

The search applet returns a list of HTML files that contain the search keyword(s) you enter. When you double-click an entry in the search results list, the applet displays the target HTML file. To get the name of the book containing this HTML file, click the [TOP] hyperlink. The book's title page (which shows the name of the book) is displayed. You can then click the Back button in the browser to return to the HTML file that was originally displayed.

Browser Error on UNIX Platforms

On some UNIX platforms, you may encounter a browser error message similar to the following: 

Unable to start a java applet: Can't find 'java40.jar' in your CLASSPATH. Read the release notes and install 'java40.jar' properly before restarting.

If the search applet does not work on your UNIX platform, try using the latest Netscape browser for the platform and add the Netscape Java Archive (JAR) file to your CLASSPATH environment variable. The path to the JAR file is in the directory in which you installed Netscape. For example: 

CLASSPATH=mytools/netscape/communicator/program/java/classes/java40.jar

After you revise the CLASSPATH variable, exit Netscape and then restart Netscape in the updated environment. When you access the search page, the search feature should work properly.

 

Contacting BEA Customer Support

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:

 

Back to Top Previous Next