BEA Logo BEA eLink for Mainframe TCP Release 3.2

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

 

   eLink for Mainframe TCP Documentation   |   eLink for Mainframe TCP Installation Guide   |   Previous Topic   |   Next Topic   |   Contents   |   Index

About This Document

The BEA eLink Adapter for Mainframe (hereafter referred to a eLink TCP) is a gateway connectivity application that enables applications on BEA Tuxedo systems to perform various non-transactional tasks with applications that reside on different kinds of computers

This document provides the following topics on installing eLink TCP software:

 


What You Need to Know

This document is primarily for system administrators who install and configure the eLink TCP product.

System administrators who work with eLink TCP should be familiar with TCP/IP networking. Programmers and system administrators who work with eLink TCP should be familiar with the concept of distributed multi-tier client/server processing.

Readers of this document should also be familiar with the operating system and BEA Tuxedo software.

 


e-docs Web Site

BEA product documentation is available on the BEA corporate Web site. From the BEA Home page, click on Product Documentation or go directly to the "e-docs" Product Documentation page at http://www.oracle.com/technology/documentation/index.html.

 


How to Print the Document

A PDF version of this document is available on the eLink TCP documentation Home page on the e-docs Web site (and also on the installation CD). You can open the PDF in Adobe Acrobat Reader and print the entire document (or a portion of it) in book format. To access the PDFs, open the eLink TCP documentation Home page, click the PDF files button, and select the document you want to print.

If you do not have the Adobe Acrobat Reader, you can get it for free from the Adobe Web site at http://www.adobe.com/.

 


Related Information

The following BEA publications are available for eLink TCP:

For information about other BEA products, refer to http://www.oracle.com/technology/documentation/index.html.

 


Contact Us!

Your feedback on the BEA eLink for Mainframe TCP documentation is important to us. Send us e-mail at docsupport@bea.com if you have questions or comments. Your comments will be reviewed directly by the BEA professionals who create and update the eLink TCP documentation.

In your e-mail message, please indicate that you are using the documentation for the BEA eLink for Mainframe TCP 3.2 release.

If you have any questions about this version of eLink TCP, or if you have problems installing and running eLink 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 that is included in the product package.

When contacting Customer Support, be prepared to provide the following information:

 


Documentation Conventions

The following documentation conventions are used throughout this document.

Convention

Item

blue text

Indicates a hypertext link in PDF or HTML

italics

Indicates emphasis or book titles or variables.

"string with quotes"

Indicates a string entry that requires quote marks.

UPPERCASE TEXT

Indicates generic file names, device names, environment variables, and logical operators.

Examples:

LPT1

SIGNON

OR

monospace text

Indicates code samples, commands and their options, data structures and their members, data types, directories, and file names and their extensions. Monospace text also indicates text that you must enter from the keyboard.

Examples:

#include <iostream.h> void main ( ) the pointer psz

chmod u+w *

\tux\data\ap

.doc

tux.doc

BITMAP

float

monospace boldface text

Identifies significant words in code.

Example:

void xa_commit ( )

{ }

Indicates a set of choices in a syntax line. The braces themselves should never be typed.

[ ]

Indicates optional items in a syntax line. The brackets themselves should never be typed.

Example:

buildclient [-v] [-o name ] [-f file-list]... [-l file-list]...

|

Separates mutually exclusive choices in a syntax line. The symbol itself should never be typed.

...

Indicates one of the following in a command line:

The ellipsis itself should never be typed.

Example:

buildclient [-v] [-o name ] [-f file-list]... [-l file-list]...

.
.
.

Indicates the omission of items from a code example or from a syntax line. The vertical ellipsis itself should never be typed.


 

 

back to top previous page next page