> CRM Administration Guide > Introduction

CRM Administration Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Introduction

This document explains how the BEA Tuxedo Mainframe Adapter for SNA Communications Resource Manager (CRM) provides the emulation allowing Customer Information Control System (CICS) and Information Management System (IMS) protocols to flow into and out of the Tuxedo environment. This document also describes how to administer application domains with the CRM.

This document covers the following topics:

 

Audience

This document is intended mainly for system administrators and operators who will use the CRM to monitor and link communications resources between mainframe and UNIX or Windows applications.

 

Related Information

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

 

Documentation Conventions

The following documentation conventions are used throughout this document:

Convention
Item
boldface text
Indicates terms defined in the glossary.
blue text
Indicates hypertext links in PDF documents.
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.


  Back to Top       Previous  Next