BEA Home | Events | Solutions | Partners | Products | Services | Download | Developer Center | WebSUPPORT
eLink for Mainframe TCP Documentation | eLink TCP for IMS User Guide | Previous Topic | Next Topic | Contents | Index

About This Document

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. This document describes the eLink TCP product and gives instructions for configuring and administering a gateway system.

The BEA eLink for Mainframe TCP IMS User Guide is contains the following topics:

- 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 Security describes how to configure security for the gateway.

- Configuring BEA eLink TCP for IMS describes how to create the configuration file and dynamically change configurations.

- Monitoring BEA eLink TCP for IMS describes how to start the 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 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 eLink TCP application.

- Sample IMS Client and Server Transactions provides sample IMS client and server transactions for use with the eLink TCP application.

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

- Glossary identifies and defines eLink TCP terminology.

What You Need to Know

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

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

You can print a copy of this document from a Web browser, one file at a time, by using the File—>Print option on your Web browser.

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 documentation 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 eLink TCP documentation consists of the following items:

- BEA eLink for Mainframe TCP Release Notes

- BEA eLink for Mainframe TCP Installation Guide

- BEA eLink for Mainframe TCP Tuxedo User Guide

- BEA eLink for Mainframe TCP CICS User Guide

- BEA eLink for Mainframe TCP IMS User Guide

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

Contact Us!

Your feedback on the BEA eLink 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 TCP 3.2 release.

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

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

- Your name, e-mail address, phone number, and fax number

- Your company name and company address

- Your machine type and authorization codes

- The name and version of the product you are using

- A description of the problem and the content of pertinent error messages

Documentation Conventions

The following documentation conventions are used throughout this document.

Convention | Item
--- | ---
boldface text | Indicates terms defined in the glossary.
Ctrl+Tab | Indicates that you must press two or more keys simultaneously.
italics | Indicates emphasis or book 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
{ } | 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.

Copyright © 2001 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.