Preface

Purpose of This Manual

This book describes BEA TUXEDO Release 6.5 for the AS/400® platform.

Who Should Read This Manual

This book is primarily intended for users who are already familiar with BEA TUXEDO (perhaps on a UNIX system) but who are new to the AS/400 system.

How This Manual Is Organized

This book is organized as follows:

Chapter 1, "Installing the BEA TUXEDO System on the AS/400," provides installation instructions for the BEA TUXEDO Core System and the Link-Level Encryption add-on packages.
Chapter 2, "Using the BEA TUXEDO System on UNIX and AS/400 Platforms," describes the differences between running a BEA TUXEDO application on a UNIX platform and an AS/400 platform.
Chapter 3, "Configuration for BEA TUXEDO System Administration," provides instructions for creating a profile for a BEA TUXEDO administrative group and requesting *JOBCTL authorization in an administrator's user profile.

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.