Preface

Purpose of This Document

This document describes the BEA TUXEDO for OpenVMS product and gives instructions for using the tools for building BEA TUXEDO for OpenVMS applications.

Who Should Read This Document

This document is intended for system administrators, network administrators, and developers who are interested in extending secure, scalable, transaction-based processing. It assumes a familiarity with the BEA TUXEDO system and OpenVMS.

How This Document Is Organized

The BEA TUXEDO for OpenVMS User's Guide is organized as follows:

Chapter 1, "Overview," provides an overview of OpenVMS and the BEA TUXEDO system.
Chapter 2, "Installing the BEA TUXEDO System on OpenVMS," provides installation instructions.
Chapter 3, "Post-Installation," provides instructions for configuring the BEA TUXEDO system on an OpenVMS platform.
Chapter 4, "Sample Applications," contains sample BEA TUXEDO applications for OpenVMS and provides pointers on developing applications.

How to Use This Document

This document 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:

/doc/tuxedo/v6_5/ovms/index.htm

Note: The online documentation requires a Web browser that supports HTML version 3.0. Netscape Navigator version 2.02 and Microsoft Internet Explorer version 3.0 or later are recommended.

Figure 1 shows the online document with the clickable navigation bar and table of contents.

Figure 1 Online Document Displayed in a Netscape Web Browser

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 chapter or appendix you want is displayed and selected in your browser. (To select a chapter or appendix, click anywhere inside the chapter or appendix you want to print. If your browser offers a Print Preview feature, you can use the feature to verify which chapter or appendix you are about to print.)

The BEA TUXEDO 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.

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

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.

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