Corporate Info | News | Solutions | Products | Partners | Services | Events | Download | How To Buy
eLink Adapter for Mainframe Doc Home | eLink Adapter for Mainframe User Guide | Previous Topic | Next Topic | Contents | Index

About This Document

This guide provides information about BEA eLink Adapter for Mainframe (eAM), an ATMI platform multi-domain connectivity product that enables client/server transactions between OS390/CICS or IMS programs and ATMI applications via a Systems Network Architecture (SNA) network.

This section covers the following topics:

- How this Guide Is Organized

- Who Should Read This Information

- Product Documentation

- Contact Us

How this Guide Is Organized

The BEA eLink Adapter for Mainframe User Guide is organized as follows:

- Understanding the BEA eLink Adapter for Mainframe Solution

  This section gives an overview of the eAM solution.

- Configuring the System

  This section provides instructions for configuring the eAM software based on the configuration of your system.

- Verifying the Software

  This section provides information to build verification tests and run sample applications after the eAM software is installed and configured.

- Security

  The section provides instructions to set up security enhancements of the eAM software, which includes encryption and TCP/IP link authentication.

- Data Translations

  This section provides information about the data translation options such as data conversion, translation rules, and data mapping.

- APPC/IMS Programming Considerations

  This section provides information about using APPC protocols to enter IMS transactions.

- Integrating eAM with Crossplex

  This section provides information about integrating eAM with CrossPlex software.

Who Should Read This Information

The target audience for this document is primarily ATMI platform system application administrators and operators.

Administrators

As the application administrator of an ATMI platform, you will configure eAM using the DMCONFIG file and its associated dm commands. You must have sufficient SNA knowledge to configure the underlying SNA stack so it conforms with definitions created in VTAM and CICS for each remote domain. This document provides information to help you understand the relationship between ATMI platform configuration settings and SNA-based application configuration concepts.

Successfully linking and establishing conversations between ATMI platform applications and SNA-based programs requires special coordination. The names and characteristics of SNA resources, configured in the SNA stack, must agree with resources and characteristics defined in VTAM and CICS. This guide includes examples of these relationships.

Typically, remote VTAM and CICS resources are defined by system personnel in a data center where IBM mainframes are located. Therefore, you need to request the remote names of eAM and CICS resources from data center systems personnel and use those names to configure the local SNA.

Operators

As an operator of an ATMI platform, you will use existing skills with the ATMI platform domain administration facility to modify SNA domain configurations and get information about the configuration and runtime environment.

Product Documentation

The eAM documentation consists of the following:

- BEA eLink Adapter for Mainframe Release Notes

- BEA eLink Adapter for Mainframe Installation Guide

- BEA eLink Adapter for Mainframe User Guide

- BEA CRM Administration Guide

Recommended Reading

You should read the appropriate ATMI platform product documentation, which is essential to comprehending the material in this document.

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://e-docs.beasys.com.

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

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.

Contact Us

Your feedback on the BEA eLink Adapter for Mainframe, 4.0 documentation is important to us. Send us e-mail at docsupport@beasys.com if you have questions or comments. Your comments will be reviewed directly by the BEA professionals who create and update the eLink Adapter for Mainframe, 4.0 documentation.

In your e-mail message, please indicate that you are using the documentation for the BEA eLink Adapter for Mainframe 4.0 release.

If you have any questions about this version of BEA eLink Adapter for Mainframe, 4.0, or if you have problems installing and running BEA eLink Adapter for Mainframe, 4.0, 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

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