|  | BEA eLink TCP for CICS 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 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.

## Purpose of This Document

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.

### Who Should Read This Document

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

  ### How This Document Is Organized

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

  - 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.

  ## How to Use This Document

  The BEA eLink TCP for CICS 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 topic you want is displayed and selected in your browser. (To select a major topic, click anywhere inside the topic you want to print. If your browser offers a Print Preview feature, you can use the feature to verify which 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.

  ### Document 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, major topic titles, or book titles. Italic text also represents variable names 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.
  `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. COBOL function or subprogram names are displayed in uppercase type without underscores or hyphens, as follows. ROUTINENAME() 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
  `{ }` | 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.

  ## Related Documentation

  The following sections list the documentation provided with the eLink TCP for CICS software, and other publications related to OLTP technology.

  ### BEA eLink TCP Documentation

  The eLink TCP documentation consists of the following items:

  - BEA eLink TCP for CICS User Guide

  - BEA eLink TCP for IMS User Guide

  - BEA eLink TCP for TUXEDO User Guide

  - BEA eLink TCP Installation Guide

  - BEA eLink TCP Release Notes

    Note: 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.

  ### BEA Publications

  The following BEA publications are also available:

  - TUXEDO System 6 Reference Manual

  - TUXEDO System 6 Programmer's Guide, Volumes 1 and 2

  ### Other Publications

  For more information about online transaction processing (OLTP) technology, refer to the following books:

  - The TUXEDO System (Andrade, Carges, Dywer, Felts)

  - TUXEDO: An Open Approach to OLTP (Primatesta)

  - Building Client/Server Applications Using TUXEDO (Hall)

  ## Contact Information

  The following sections provide information about how to obtain support for the documentation and software.

  ### Documentation Support

  If you have questions or comments on the documentation, you can contact the BEA Information Engineering Group by e-mail at docsupport@beasys.com. (For information on how to contact Customer Support, refer to the following section.)

  ### Customer Support

  If you have any questions about this version of eLink TCP for CICS, or if you have problems installing and running eLink TCP for CICS, contact BEA Customer Support through BEA WebSupport at `www.beasys.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

  TABLE OF CONTENTS | PREVIOUS TOPIC | NEXT TOPIC | INDEX