		BEA eLink TCP for TUXEDO 3.1 Information Center
		HOME \| SEARCH \| CONTACT \| PDF FILES \| WHAT'S NEW
		TABLE OF CONTENTS \| PREVIOUS TOPIC \| NEXT TOPIC \| INDEX

Preface

BEA eLink for Mainframe TCP for TUXEDO (hereafter referenced as eLink TCP for TUXEDO) is a gateway connectivity feature that enables application programs on BEA TUXEDO systems to perform various non-transactional tasks with application programs that reside on different kinds of computers.

Purpose of This Document

This document describes the eLink TCP for TUXEDO product and gives instructions for using the tools for building eLink TCP for TUXEDO applications.

This guide explains how to configure and administer eLink TCP for TUXEDO and how eLink TCP for TUXEDO fits into the BEA TUXEDO environment. In addition, this guide:

Explains how eLink TCP for TUXEDO processes service requests, those that originate locally and those that originate on remote systems
Explains how eLink TCP for TUXEDO affects BEA TUXEDO application programs
Provides conceptual and procedural information that will help you configure and administer eLink TCP for TUXEDO

Who Should Read This Document

This document is intended for system administrators who will configure and administer eLink TCP for TUXEDO. In addition, programmers will find useful pointers for developing client programs and service routines that send data through eLink TCP for TUXEDO.

How This Document Is Organized

The BEA eLink TCP for TUXEDO User Guide is organized as follows:

Introducing BEA eLink TCP for TUXEDO introduces eLink TCP for TUXEDO, explains how eLink TCP for TUXEDO fits into the BEA TUXEDO environment, and lists hardware and software requirements.
Understanding How BEA eLink TCP for TUXEDO Works explains how to start eLink TCP for TUXEDO, how it processes services requests, and how it is terminated. It also provides information that helps programmers develop clients' programs and service routines that send data through eLink TCP for TUXEDO.
Configuring BEA eLink TCP for TUXEDO for Data Mapping provides detailed information about the eLink TCP for TUXEDO configuration file (GWICONFIG) and associated configuration parameters. In addition, this document explains how to update the BEA TUXEDO configuration file (UBBCONFIG) so that eLink TCP for TUXEDO can interact with BEA TUXEDO software.
Setting Up Security for BEA eLink TCP for TUXEDO provides detailed information about the eLink TCP for TUXEDO configuration file (GWICONFIG) and associated configuration parameters. In addition, this document explains how to update the BEA TUXEDO configuration file (UBBCONFIG) so that eLink TCP for TUXEDO can interact with BEA TUXEDO software.
Configuring BEA eLink TCP for TUXEDO provides detailed information about the eLink TCP for TUXEDO configuration file (GWICONFIG) and associated configuration parameters. In addition, this document explains how to update the BEA TUXEDO configuration file (UBBCONFIG) so that eLink TCP for TUXEDO can interact with BEA TUXEDO software.
Starting BEA eLink TCP for TUXEDO explains how to set environmental variables, test connectivity with remote regions, and invoke eLink TCP for TUXEDO.
Error and Informational Messages describes messages and resolutions for the system.
Code Page Translation Tables provides the code page tables that are distributed with the product and instructions for modifying these tables.

How to Use This Document

The BEA eLink TCP for TUXEDO User Guide is designed primarily as an online, hypertext document. If you are reading this as a paper publication, note that to get full use from this document you should install and access it as an online document via a Web browser.

The following sections explain how to view this document online, and how to print a copy of this document.

Opening the Document in a Web Browser

To access the online version of this document if it is installed on a Web server, open the following HTML file.

http://(directory path to eLink TCP HTML files)/index.htm

Note: The online documentation requires a Web browser that supports HTML 3.0. Netscape Navigator 4.0 or higher or Microsoft Internet Explorer 4.0 or higher are recommended.

Printing from a Web Browser

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

Document Conventions

The following documentation conventions are used throughout this manual.


Item	Examples
Variable names	Variable names represent information you must supply or output information that can change; they are intended to be replaced by actual names. Variable names are displayed in italics and can include hyphens but not underscores. The following are examples of variable names in text. error-file-name The when-return value...
Function names in text	C function names are displayed in lower case type and can include parentheses and possibly underscores, as follows. routine_name() COBOL function or subprogram names are displayed in uppercase type without underscores or hyphens, as follows. ROUTINENAME()
Symbolic constants for languages (keywords, error codes, and flags)	C symbolic constants are displayed in uppercase type and can include underscores, as follows. CONSTANT_NAME COBOL symbolic constants are displayed in uppercase type and can include hyphens, as follows. CONSTANT-NAME
User input and screen output	For screen displays and other examples of input and output, user input appears as in the first of the following lines; system output appears as in the second through fourth lines. `dir c:\accounting\data` Volume in drive C is WIN_NT_1 Volume Serial Number is 1234-5678 Directory of C:\ACCOUNTING\DATA
Syntax	Code samples can include the following elements: Variable names can include hyphens but not underscores (e.g., error-file-name) Optional items are enclosed in square brackets: [ ]. If you include an optional item, do not code the square brackets. A required element for which alternatives exist is enclosed in braces {}. The alternatives are separated by the pipe (vertical bar) character: \|. You must include only one of the alternatives for that element. Do not code the braces or pipe character. An ellipsis ( ... ) indicates that the preceding element can be repeated as necessary. C synopsis: int tpacall(char svc, char data, long len, long flags) COBOL statement: CALL "TPACALL" USING TPSVCDEF-REC TPTYPE-REC DATA-REC TPSTATUS-REC.
Omitted code	An ellipsis ( ... ) is used in examples to indicate that code that is not pertinent to the discussion is omitted. The ellipsis can be horizontal or vertical.