Preface

The Oracle Transparent Gateway® for IBM DRDA for Sun Solaris provides users with transparent access to DRDA databases as if they were Oracle databases.

Intended Audience

This guide is intended for anyone responsible for installing, configuring, and administering the gateway, and also for application developers.

Read this guide if you are responsible for tasks such as:

• Installing and configuring the Oracle Transparent Gateway for IBM DRDA for Sun Solaris

• Configuring the SunLink SNA Peer-to-Peer product

• Setting up gateway security

• Diagnosing gateway errors

• Using the gateway to access tables in DRDA databases

• Writing applications that access DRDA databases through the gateway

Understand the fundamentals of transparent gateways and the Solaris operating system before using this guide to install or administer the gateway.

Related Publications

The Oracle Transparent Gateway for IBM DRDA Installation and User's Guide for Sun Solaris is included as part of your product shipment. Also included is:

• Oracle 9i Heterogeneous Services, part number A86571

  This guide contains information common to all heterogeneous gateways, including important information on functions, parameters, and error messages.

Refer to the Oracle Technical Publications Catalog and Price Guide for a complete list of documentation provided for Oracle products.

Documentation Accessibility

Oracle's goal is to make our products, services, and supporting documentation accessible to the disabled community with good usability. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

JAWS, a Windows screen reader, may not always correctly read the code examples in this document.

The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Conventions

Examples of input and output for the gateway and Oracle environment are shown in a special font:

S mkdir /ORACLE/your_name

All output is shown as it actually appears. For input, refer to the following table. The first column lists the conventions used in this manual and the second column describes their meanings:

Convention	Meaning
example text	Words or phrases, such as mkdir and ORACLE, must be entered exactly as spelled and in the letter case shown. In this example, mkdir must be entered in lowercase letters and ORACLE in uppercase letters.
italic text	Italicized uppercase or lowercase, such as your_name, indicates that you must substitute a word or phrase, such as the actual directory name.
BOLD text or bold italic TEXT	Bold words or phrases refer to a file directory structure, such as a directory, path or file ID.
{ }	Curly braces indicate that one of the enclosed arguments is required. Do not enter the braces themselves.
[ ]	Brackets enclose optional clauses from which you can choose one or none. Do not enter the brackets themselves.
. . .	Ellipses indicate that the preceding item can be repeated. You can enter an arbitrary number of similar items.
|	Vertical lines separate choices.

Other punctuation, such as commas, quotes, or the pipe symbol (|), must be entered as shown unless otherwise specified. Directory names, file IDs, and so on, appear in the required letter case in examples. The same convention is used when these names appear in text, and the names are highlighted in bold. The use of italics indicates that those portions of a file ID that appear in italics can vary.

Gateway commands, file IDs, reserved words, and keywords appear in uppercase in examples and text. UNIX commands, environment variables, and keywords appear in the required letter case in examples and text. Reserved words and keywords must always be entered as shown. They have reserved meanings within the Oracle system.

SQL*Plus Prompts

The SQL*Plus prompt, SQL>, appears in SQL statements and SQL*Plus command examples. Enter your response at the prompt. Do not enter the text of the prompt, SQL>, in your response.

UNIX Prompts

The UNIX prompt, $, appears in UNIX command examples. Enter your response at the prompt. Do not enter the text of the prompt, $, in your response. A dollar sign ($) is part of some UNIX directory names and should not be confused as a prompt character.

Storage Measurements

Storage measurements use these abbreviations:

• K, for kilobyte, which equals 1024 bytes

• M, for megabyte, which equals 1 048 576 bytes

• G, for gigabyte, which equals 1 073 741 824 bytes