This script is not for online documents. It is only used by the QuestAgent Java Applet for CD search indexes.
Skip navigation.

Release Notes

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

BEA Tuxedo Mainframe Adapter for OSI TP Release Notes

BEA Tuxedo Mainframe Adapter for OSI TP Version: 8.1
Date: March 2004

The following topics are discussed in this document.

 


What's New!

This release of BEA Tuxedo Mainframe Adapter for OSI TP provides the following new features:

 


About This BEA Tuxedo Mainframe Adapter for OSI TP Release

This distribution of the BEA Tuxedo Mainframe Adapter for OSI TP product (hereafter referenced as BEA TMA OSI TP) includes a CD-ROM that contains the BEA TMA OSI TP Version 8.1 product and a second CD-ROM that contains product documentation.

 


Supported Platforms

The BEA Tuxedo Mainframe Adapter for OSI TP Version 8.1 server and client support platforms running BEA Tuxedo 8.1 on the following operating systems:

Operating System

AIX 5.2

HP-UX 11

Solaris 8

Microsoft Windows 2000 Advanced Server


 

 


Pre-Installation Considerations

Complete the following tasks prior to installing BEA Tuxedo Mainframe Adapter for OSI TP:

 


Prerequisite Software

Install the BEA Tuxedo 8.1 software and make sure it is configured and operational prior to installing BEA Tuxedo Mainframe Adapter for OSI TP 8.1 software.

 


Using the License Key

You must enter the license key for BEA Tuxedo Mainframe Adapter for OSI TP 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 BEA Tuxedo Mainframe Adapter for OSI TP license key, you must append the license key file provided with the product software to the BEA Tuxedo license key file. This can be done automatically by answering a query at BEA Tuxedo Mainframe Adapter for OSI TP installation time. Or it can be done manually as shown in the steps below.

Caution: Do not alter any information within sections of the license key files. This is a violation of the BEA Systems licensing agreement. Doing so may disable the BEA TMA OSI TP and/or additional components.

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 Tuxedo License Key File

[TUXEDO 8.1]
LICENSEE=BEA Professional Services
SERIAL=1000000104
ORDERID=0
USERS=20
TYPE=SDK
WEBGUI=separate
WSCOMPRESSION=separate
EXPIRATION=2004-12-31
SIGNATURE=
  1. Append the BEA Tuxedo Mainframe Adapter for OSI TP license key file to the Tuxedo license key file. An example of the BEA Tuxedo Mainframe Adapter for OSI TP license key follows.

Listing 2 Sample BEA Tuxedo Mainframe Adapter for OSI TP License Key File

[Tuxedo Mainframe Adapter OSI TP]
VERSION=8.1
LICENSEE=*** BEA SYSTEMS ***
SERIAL=8882327878
ORDERID=N/A
EXPIRATION=2004-12-31
SIGNATURE=
  1. Save the file and exit the text editor. Your license key is now in effect.

 


Product Issues

The following sections describe some of the miscellaneous issues you may need to consider before you install BEA TMA OSI TP. Refer to the BEA Tuxedo Mainframe Adapter for OSI TP Installation Guide for more detailed information about installing or upgrading BEA TMA OSI TP.

Known Limitations

This section describes limitations in the current BEA Tuxedo Mainframe Adapter for OSI TP release and includes possible workarounds where applicable.

The table below lists a CR (Change Request) number for each problem. Refer to this number to conveniently track the solution as the problems are resolved. Please contact Unisys Technical Support for assistance in tracking any unresolved problems. For contact information, see Contact Us!

1

N/A

Change in return code

Problem

TPCONNECT gets a return code of 1 with the revent field not set. In previous Tuxedo releases tpsend used to return -1 with tperrno=TPEEVENT and the rEvent=TPEV_SVCSUCC, now tpsend returns 1.

Platform

All

Workaround

None

2

CR053479

dmadmin can only be executed from the $TUXDIR, all other executions just return.

Problem

The Microsoft Windows operating systems have a system file called dmadmin, which is listed in the WINNT\system32 path. If the Tuxedo dmadmin is not executed from the $TUXDIR, the Microsoft dmadmin is called.

Platform

Windows 2000 Professional and Windows 2000 Advanced Server

Workaround

Add TUXEDO\BIN to the beginning of your environment path.


 

Fixed Problems

This section describes known problems from the prior release of the eLink Adapter for Mainframe that have been fixed with the current release of the BEA Tuxedo Mainframe Adapter for OSI TP software. The following table lists a Case or CR (Change Request) number for each problem.

1

CR090077

X_OCTET to STRING translation not adding NUL to end buffer when necessary.


Problem

When data is going from the gateway (X_OCTET_ to a Tuxedo application (STRING), the NULL should be added at the end of the X_OCTET buffer so that the Tuxedo application can use it. The gateway does not add the NULL at the end of the buffer


Platform

All

2

CR098720

Integrating various fixes and patch level for Unisys code.


Problem

This CR resolves the following problems in the Unisys source:

  • Resource leak (timing issue) issuing aborts.

  • Network events lost when "Connection timed out" error occurs.

  • Memory leak when using XATMI_ENCODING=NATIVE_A_SERIES with no data.

  • "pdu_type=UNKNOWN" message appears with tracing turned on.

  • Incoming calls are rejected, remote domain name is junk in ULOG.

  • User cannot use OSIADMIN without Windows administrator access.


Platform

All

3

CR110391

Dynamically adding local services causes GWOSITP to die.


Problem

When using dmadmin -c command to dynamically add local services, GWOSITP dies. The update completes successfully and then GWOSITP dies and is removed from the BBL.


Platform

HP-UX

4

CR120219

Integrating various fixes and patch level for Unisys code.


Problem

This CR resolves the following problems in the Unisys source:

  • Misleading P-ABORT IND messages appear in the ULOG file.

  • GWOSITP or PORTPROXY terminates abnormally during connection termination.

  • Multiplexed connection collision results in high processor usage on UNIX and Windows.

  • GWOSITP on AIX 5 consumes large amounts of processor time when reconnecting.


Platform

All

5

CR123289

Integrating various fixes and patch level for Unisys code.


Problem

GWOSITP terminates with locking error.


Platform

All

6

CR132672

Memory leak running on Solaris 8 with an array of strings using XATMI_ENCODING="PRELIMINARY".


Problem

A memory leak occurs with an array of strings using PRELIMINARY encoding.


Platform

Sun Solaris 8

7

CR132890

IP address changed at tmboot time if 0 is in third arc.


Problem

GWOSITP incorrectly copies the four IP address bytes into the osiLDOM_t or osiRDOM_t structure.


Platform

All


 

 


Where to Get Product Documentation

Documentation for this product is available from the following locations:

Using the BEA TMA OSI TP 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 CDROM in the docs/tuxedo/ositp/v81 directory. Note the filename path to the directory where you install them on your server or client.

The Online Documentation CD includes a Java search applet to help you find BEA TMA OSI TP 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 CD 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 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:

Use the following path to access the document from the CD.

Listing 3 Accessing Online Documentation from a CD

<cdrom>/docs/tuxedo/ositp/v81/index.htm

Use the following path to access the document installed to a Web server.

Listing 4 Accessing Online Documentation from a Web Server

http://(directory path to BEA TMA OSI TP HTML files)/index.htm

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 BEA Tuxedo Mainframe Adapter for OSI TP Online Documentation 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 home site at www.adobe.com. (Please note that the BEA Tuxedo Mainframe Adapter for OSI TP Documentation PDF page contains a hot 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 CD Search Applet Limitations

The Online Documentation CD includes a Java search applet to help you find BEA TMA OSI TP 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.

UNC Path Names

The Java search applet uses a pre-compiled 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 documentation 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 documentation 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 documentation CD on a Network Neighborhood system's shared CD device, for all other relative hyperlinks on the CD.

Additional CD 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

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.

Documentation Notes

The following documentation can help you use BEA Tuxedo Mainframe Adapter for OSI TP:

Additional Information

For additional information, please see the BEA Tuxedo Online Documentation athttp://www.oracle.com/technology/documentation/index.html.

 


Contact Us!

BEA TMA OSI TP is a product jointly developed by BEA Systems, Inc. and Unisys Corporation. Support services and contacts are described in the following sections.

SURETY Support Services

A SURETY service agreement gives you easy access to Unisys Support Online or Unisys Client Support Centers. These services are described below.

Unisys Customer Support

Unisys customer support gives clients easy access, on the World Wide Web or by telephone, to these service options:

Clients with valid support agreements can visit an electronic database of reported problems and solutions. They can also use e-mail or telephone to contact our product specialists with technical questions. Clients are eligible to receive updates to a product when critical problems have been fixed.

Support Online

Unisys has a World Wide Web site available to customers who have support agreements. If you have any questions or problems with a Unisys product, your first source of information is Support Online, an online technical resource available through the World Wide Web at http://www.support.unisys.com.

This technical resource is available 24 hours a day, 7 days a week. It offers a wealth of information about Unisys hardware and software systems. Take some time to explore Support Online and discover the services available to you.

Client Support Centers

Unisys clients with valid support agreements can also access Client Support Centers. If you have unresolved questions or problems concerning Unisys product installation or operation (after referring to the documentation or your system administrator), call the appropriate Client Support Center:

Within the continental United States or Canada, call one of the following toll-free numbers:

1-800-328-0440 (prompt 4) - United States

1-800-387-6181 - Canada

1-800-361-8097 - French Canada

Outside the continental United States, obtain a support center telephone number from your local Unisys customer support representative.

To expedite your request, please have the following information ready before contacting Unisys.

Tech Advantage

In addition, Unisys Client Support Centers offer Tech Advantage, a full complement of technical service packages that provide you with cost-effective, fast-cycle support. Tech Advantage services can help you solve your most difficult problems or maximize the effectiveness of your system, regardless of your product choice.

Here are some ways to put Tech Advantage to work for you:

For more information on Tech Advantage, visit the Support Online Web page and follow the link to Tech Advantage or call your Client Support Center.

Reporting a Software Problem with a User Communication Form

A customer representative may provide instructions or solutions from the Client Support Center database. If this help is insufficient, provide your representative with a full description of the problem, including any relevant error messages, and, if possible, a full description of the function you were attempting and your actions immediately prior to the error. The representative will then submit an electronic User Communication Form (UCF) to Unisys on your behalf, and give you the following information:

VAR Customer Support

All clients of Unisys resellers should contact their Value Added Resellers (VARs) for support access details.

 

Back to Top Previous Next