Introduction

This document provides instructions for installing BEA Tuxedo Mainframe Adapter for SNA software (hereafter referenced as TMA SNA.)

What You Need to Know

This document is intended for system administrators and application programmers who will install and configure the Tuxedo Mainframe Adapter for SNA product.

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 Tuxedo Mainframe Adapter for SNA 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 Tuxedo Mainframe Adapter for SNA 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 free of charge from the Adobe Web site at http://www.adobe.com/.

The following documents contain information that is relevant to using Tuxedo Mainframe Adapter for SNA:

Your feedback on the Tuxedo Mainframe Adapter for SNA 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 Tuxedo Mainframe Adapter for SNA documentation.

In your e-mail message, please indicate that you are using the documentation for the Tuxedo Mainframe Adapter for SNA 9.0 release.

If you have any questions about this version of Tuxedo Mainframe Adapter for SNA, or if you have problems installing and running Tuxedo Mainframe Adapter for SNA, contact BEA Customer Support through BEA Web Support 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:

Documentation Conventions

Convention	Item
blue text	Indicates a hypertext link in PDF or HTML
italics	Indicates emphasis or book titles or variables.
“string with quotes”	Indicates a string entry that requires quote marks.
UPPERCASE TEXT	Indicates generic file names, device names, environment variables, and logical operators. Examples: LPT1 SIGNON OR
`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` `xa_commit` `( )`
`{ }`	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: `buildclient [-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: `buildclient [-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.

Installation Guide

Introduction

What You Need to Know

e-docs Web Site

How to Print the Document

Documentation Conventions