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

Preface

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

Purpose of This Document

This document describes the BEA eLink TCP product and gives instructions for configuring and administering a gateway system.

Who Should Read This Document

This document is intended for system administrators who will configure and administer the BEA eLink TCP system. In addition, programmers will find useful information for developing client programs and service routines that exchange data with the remote BEA eLink gateways.

How This Document Is Organized

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

Introducing BEA eLink TCP for IMS provides a description of concepts and processes.
Understanding How BEA eLink TCP for IMS Works describes how to develop applications that exchange data with a remote BEA eLink gateway.
Configuring BEA eLink TCP for IMS describes how to create the configuration file, set up security, and dynamically change configurations.
Monitoring BEA eLink TCP for IMS describes how to start the BEA eLink TCP application and test connectivity with remote BEA eLink gateways. It also provides information on implementing the gateway system and handling errors.
Programming BEA eLink TCP for IMS describes how to program your application in COBOL, including message formats and field descriptions.
System Services Descriptions describes various OS/390, IMS, and TCP/IP services used by BEA eLink TCP.
Error and Informational Messages describes messages and resolutions for the system.
Example Configuration Files provides sample configurations.
Sample JCL and User Exits provides sample job control language (JCL) required to install and execute the BEA eLink TCP application.
Sample IMS Client and Server Transactions provides sample IMS client and server transactions for use with the BEA eLink TCP application.

Error and Reason Codes describes error and reason codes issued by the gateway.

How to Use This Document

The BEA eLink TCP for IMS 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, open the following HTML file in a Web browser:

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 copy 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 major topic, click anywhere inside the major topic you want to print. If your browser offers a Print Preview feature, you can use the feature to verify which major topic you are about to print.)

The BEA eLink TCP Online Documentation CD also includes Adobe Acrobat PDF files of all of the online documents. You can use the Adobe Acrobat Reader to print all or a portion of each document.

Documentation Conventions

The following documentation conventions are used throughout this document.


Convention	Item
Ctrl+Tab	Indicates that you must press two or more keys sequentially.
italics	Indicates emphasis, book titles, or major topic titles.
`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` `commit` `( )`
`monospace italic text`	Identifies variables in code. Example: `String` `expr`
UPPERCASE TEXT	Indicates device names, environment variables, and logical operators. Examples: LPT1 SIGNON OR
underscore	Indicates default values in a syntax line.
`{ }`	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: `buildobjclient [-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: That an argument can be repeated several times in a command line That the statement omits additional optional arguments That you can enter additional parameters, values, or other information The ellipsis itself should never be typed. Example: `buildobjclient [-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.