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

About This Document

BEA eLink for Mainframe TCP for CICS (hereafter referenced as eLink TCP for CICS) 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 CICS. This document describes the eLink TCP for CICS product and gives instructions for using the tools for building eLink TCP for CICS applications. This document also explains how to configure and administer eLink TCP for CICS.

The BEA eLink TCP for CICS User Guide contains the following topics:

- Introducing BEA eLink TCP for CICS introduces eLink TCP, explains how eLink TCP fits into the BEA Tuxedo configuration, and lists MVS software requirements.

- Understanding How BEA eLink TCP for CICS Works explains how eLink TCP is started, how it processes services requests, and how it is terminated.

- Configuring the eLink TCP Security provides background information to configure security for eLink TCP.

- Configuring and Administering BEA eLink TCP for CICS provides background information to configure eLink TCP.

- Programming BEA eLink TCP for CICS provides information that helps programmers develop service routines that send data to the remote eLink TCP gateway.

- Error and Informational Messages provides a detailed list of the messages eLink TCP generates both for the local CICS log and the remote BEA Tuxedo ULOG.

What You Need to Know

This document is primarily for CICS system administrators who configure and administer eLink TCP. In addition, programmers can find useful pointers for developing client programs and service routines that send data through to the remote BEA eLink gateway.

Programmers who work with eLink TCP should be familiar with CICS applications development.

System administrators who work with eLink TCP should be familiar with the following concepts, tools, and procedures:

- TCP/IP networking

- IBM CICS Sockets Interface

- Defining new resources to CICS

- Standard CICS monitoring tools

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 for Mainframe 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 for Mainframe 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 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 for Mainframe 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 BEA eLink for Mainframe TCP, or if you have problems installing and running BEA eLink for Mainframe 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.