Oracle® Transparent Gateway for DRDA

Installation and User's Guide

10g Release 2 (10.2) for Microsoft Windows

B16218-03

November 2008

Oracle Transparent Gateway for DRDA Installation and User's Guide, 10g Release 2 (10.2) for Microsoft Windows

B16218-03

Copyright © 2001, 2008, Oracle. All rights reserved.

Primary Author:  Maitreyee Chaliha

Contributing Author: Peter A Castro

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

List of Figures

List of Tables

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

- SQL*Plus Prompts

- DOS Prompts

- Storage Measurements

- Directory Names

1 Introduction

- Introduction to the Oracle Transparent Gateway

- Protection of Current Investment

- Release 10g Gateways

- Advantages of the Gateway

- Gateway Capabilities

- Transparency at All Levels

- Extended Database Services

- Extended Advanced Networking, Internet and Intranet Support

- Dynamic Dictionary Mapping

- SQL

- Data Definition Language

- Data Control Language

- Passthrough and Native DB2 SQL

- Stored Procedures

- Oracle Stored Procedures

- Native DB2 Stored Procedures

- Languages

- Oracle Database Server Technology and Tools

- SQL*Plus

- TwoEPhase Commit and Multisite Transactions

- Site Autonomy

- Migration and Coexistence

- Security

- Terms

- Architecture

- Implementation

- How the Gateway Works

- SQL Differences

- Oracle Tools and the Gateway

- SQL*Plus

- Features

- Heterogeneous Services Architecture

- Performance Enhancements

- Fetch Reblocking

- Oracle Database 10g Passthrough Supported

- Retrieving Result Sets Through Passthrough

- Support for TCP/IP

- Native Semantics

- Columns Supported in a Result Set

- EXPLAIN_PLAN Improvement

- Heterogeneous Database Integration

- Minimum Impact on Existing Systems

- Large Base of Data Access

- Application Portability

- Remote Data Access

- Support for Distributed Applications

- Application Development and End User Tools

- Password Encryption Utility

- Support for DB2/OS390 V6, V7, and V8 Stored Procedures

- Codepage Map Facility

- IBM DB2 Universal Database Support

- IBM DB2 Version 5.1 ASCII Tables

- Read-Only Support

- Support for Graphic and Multibyte Data

- Support for DB2/UDB on Intel Hardware

- Data Dictionary Support for DB2/UDB

2 Release Information

- Product Set

- Changes and Enhancements

- Bugs Fixed in 10g Release 2 (10.2)

- Known Problems

- Known Restrictions

- DB2 Considerations

- SQL Limitations

3 System Requirements

- Hardware Requirements

- Processor

- Memory

- Network Attachment

- Disk Space

- Software Requirements

- Operating System

- DRDA Databases

- Communications

- Oracle Database server

- Oracle Networking Products

- Documentation Requirements

4 Installing the Gateway

- Introduction

- Before You Begin

- Checklist for Gateway Installation

- Installation Overview

- Preinstallation

- Installing the Gateway from the Installation Media

- Step 1: Log on to the host

- Step 2: Load the CD-ROM into the CD-ROM Drive

- Step 3: Start the Oracle Universal Installer on Microsoft Windows

- Step 4: Step through the Oracle Universal Installer

- Step 5: Verify Installation Success

- Installation Complete

- Removing the Gateway

5 Configuring the DRDA Server

- Checklists for Configuring the DRDA Server

- DB2/OS390

- DB2/400

- DB2/UDB (Universal Database)

- DB2/VM

- DB2/OS390

- Step 1: Configure the Communications Server

- Step 2: Define the user ID that owns the package

- Step 3: Define the recovery user ID

- Step 4: Determine DRDA location name for DB2 instance

- Step 5: Configure DB2 Distributed Data Facility for Gateway

- DB2/400

- Step 1: Configure the Communications Server

- Step 2: Define the user ID that owns the package

- Step 3: Define the recovery user ID

- Step 4: Determine DRDA location name for DB2/400 instance

- DB2/UDB (Universal Database)

- Step 1: Configure the SNA Communications Server

- Step 2: Define the user ID that owns the package

- Step 3: Define the recovery user ID

- Step 4: Determine DRDA location name for DB2/UDB instance

- DB2/VM

- Step 1: Configure the Communications Server

- Step 2: Define the user ID that owns the package

- Step 3: Define the recovery user ID

- Step 4: Determine DRDA location name for DB2/VM instance

6 Configuring Microsoft SNA Server or Host Integration Server

- Before You Begin

- Steps for Configuring the Communications Interfaces

- Creating SNA Server Profiles for the Gateway

- Independent Versus Dependent LUs

- Creating SNA Definitions for the Gateway

- Sample SNA Server Definitions

- Definition Types

- SNA Server Definitions

- Server Selection

- Service Properties

- Link Service Definition

- Connection Definition

- Local LU Definition

- Mode Definition

- Remote LU Definition

- CPIEC Symbolic Destination Names

- Testing the Connection

- Using SNA Session Security Validation

- SNA Conversation Security

- SNA Security Option SECURITY=PROGRAM

- SNA Security Option SECURITY=SAME

7 Configuring IBM Communication Server

- Before You Begin

- Checklist for Configuring the Communications Interfaces

- Creating IBM Communication Server Profiles for the Gateway

- Independent Versus Dependent LUs

- Creating SNA Definitions for the Gateway

- Sample IBM Communication Server Definitions

- Definition Types

- IBM Communication Server Definitions

- Creating the Configuration

- Defining the Node

- Testing the Connection

- Using SNA Session Security Validation

- SNA Conversation Security

- SNA Security Option SECURITY=PROGRAM

- SNA Security Option SECURITY=SAME

8 Configuring TCP/IP

- Before You Begin

- Port Number

- Configuring TCP/IP

9 Oracle Net

- Checklists for Oracle Net

- Configuring Oracle Net

- Advanced Security Encryption

- Setting Up Advanced Security Encryption for Test

- Testing Advanced Security Encryptions

- Oracle Net and SQL*Net Introduction

- Oracle Net Overview

- Distributed Processing

- Distributed Database

- Terminology for Oracle Net

- Configuring Oracle Net

- Step 1: Modify the listener.ora file

- Step 2: Modify the tnsnames.ora file

- Advanced Security Encryption

- Setting Up Advanced Security Encryption for Test

- Step 1: Set Advanced Security Encryption Parameters for the Gateway

- Step 2: Set Advanced Security Encryption Parameters

- Testing Advanced Security Encryptions

- Step 1: Connect the Gateway and Oracle the Integrating Server

- Step 2: Reset Configuration Parameters on the Gateway

10 Configuring the Gateway

- Configuration Checklist

- Choosing a Gateway System Identifier (SID)

- Enter the SID on the Worksheet

- Gateway Configuration

- Configuring the Host

- Step 1: Copy the gateway initialization

- Step 2: Determine settings for gateway initialization parameters

- Required Parameters

- Optional Parameters

- Step 3: Tailor the initsid.ora File

- Binding the DRDA Gateway Package

- Binding Packages on DB2/Universal Database (DB2/UDB)

- DRDA Gateway Package Considerations

- Before Binding the DRDA Gateway Package

- Step 1: Check all DRDA parameter settings

- Step 2: If using DB2/UDB, then create ORACLE2PC table

- Sample SQL scripts

- Step 1:  Run Data Dictionary scripts

- Step 1a:  Upgrading from a previous gateway version

- Step 1b: Creating the Data Dictionary tables and views

- Step 2: DB2/UDB or other server

- Step 2a: If server is DB2/UDB, then grant authority to package

- Step 2b: If server is not DB2/UDB, then create the ORACLE2PC table

- Backup and Recovery of Gateway Configuration

- Configuring the Oracle Integrating Server

- Step 1: Create a database link

- Step 2: Create synonyms and views

- Accessing the Gateway from Other Oracle Servers

- Accessing Other DRDA Servers

- Gateway Installation and Configuration Complete

11 Using the Gateway

- Processing a Database Link

- Creating Database Links

- Guidelines for Database Links

- Dropping Database Links

- Examining Available Database Links

- Limiting the Number of Active Database Links

- Accessing the Gateway

- Step 1: Log in to the Oracle integrating server

- Step 2: Create a database link to the DRDA database

- Step 3: Retrieve data from the DRDA database

- Accessing AS/400 File Members

- Using the Synonym Feature

- Performing Distributed Queries

- Example of a Distributed Query

- TwoEPhase Commit Processing

- Distributed DRDA Transactions

- ReadEOnly Gateway

- Replicating in a Heterogeneous Environment

- Oracle Database 10g Server Triggers

- Oracle Snapshots

- Copying Data from the Oracle Server to the DRDA Server

- Copying Data from the DRDA Server to the Oracle Server

- Tracing SQL Statements

12 Developing Applications

- Gateway Appearance to Application Programs

- Fetch Reblocking

- Using Oracle Stored Procedures with the Gateway

- Using DRDA Server Stored Procedures with the Gateway

- Oracle Application and DRDA Server Stored Procedure Completion

- Procedural Feature Considerations with DB2

- Database Link Behavior

- Oracle Server SQL Construct Processing

- Compatible SQL Functions

- Translated SQL Functions

- Compensated SQL Functions

- Native Semantic SQL Functions

- DB2/OS390 SQL Compatibility

- DB2/Universal Database SQL Compatibility

- DB2/400 SQL Compatibility

- DB2/VM SQL Compatibility

- Native Semantics

- SQL Functions That Can Be Enabled

- SQL Functions That Can Be Disabled

- SQL Set Operators and Clauses

- DRDA Data Type to Oracle Data Type Conversion

- Performing Character String Operations

- Converting Character String data types

- Performing Graphic String Operations

- Performing Date and Time Operations

- Processing TIME and TIMESTAMP Data

- Processing DATE Data

- Performing Date Arithmetic

- Dates

- HS_NLS_DATE_FORMAT Support

- Oracle TO_DATE Function

- Performing Numeric Data Type Operations

- Mapping the COUNT Function

- Performing Zoned Decimal Operations

- Passing Native SQL Statements through the Gateway

- Processing DDL Statements through Passthrough

- Using the DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE Function

- Examples

- Retrieving Result Sets Through Passthrough

- Example

- Oracle Data Dictionary Emulation on a DRDA Server

- Using the Gateway Data Dictionary

- Using the DRDA Catalog

- Defining the Number of DRDA Cursors

13 Security Considerations

- Security Overview

- Authenticating Application Logons

- Defining and Controlling Database Links

- Link Accessibility

- Links and CONNECT Clauses

- TCP/IP Security

- Processing Inbound Connections

- User ID Mapping

- DB2/OS390

- DB2/VM

- DB2/400

- DB2/Universal Database

- Passwords in the Gateway Initialization File

14 Migration and Coexistence with Existing Gateways

- Migrating Existing V4, V8, or V9 Gateway Instances to New Release

- Step 1: Install the new Release

- Step 2: Transferring initsid.gtwboot Gateway Boot Initialization parameters.

- Step 3: Transferring initsid.ora gateway initialization file parameters.

- Backout Considerations When Migrating to New Releases

- New and Changed Parameters When Migrating to Release 10

- New Parameters

- New Gateway Initialization File Parameters

- Parameters That Have Been Changed in Usage

- Parameters That Have Been Renamed

- Obsolete Parameters

- DRDA Server Considerations

- Oracle Net Considerations

15 Error Messages, Diagnosis, and Reporting

- Interpreting Gateway Error Messages

- Errors Detected by the Oracle Integrating Server

- Errors Detected by the Gateway

- Errors Detected in the DRDA Software

- Communication Errors

- Errors Detected by the Server Database

- Mapped Errors

- Gateway Error Codes

- SQL Tracing and the Gateway

- SQL Tracing in the Oracle Database

- SQL Tracing in the Gateway

A Oracle DB2 Data Dictionary Views

- Supported Views

- Data Dictionary View Tables

- ALL_CATALOG

- ALL_COL_COMMENTS

- ALL_CONS_COLUMNS

- ALL_CONSTRAINTS

- ALL_INDEXES

- ALL_IND_COLUMNS

- ALL_OBJECTS

- ALL_SYNONYMS

- ALL_TABLES

- ALL_TAB_COLUMNS

- ALL_TAB_COMMENTS

- ALL_USERS

- ALL_VIEWS

- COLUMN_PRIVILEGES

- DICTIONARY

- DUAL

- TABLE_PRIVILEGES

- USER_CATALOG

- USER_COL_COMMENTS

- USER_CONSTRAINTS

- USER_CONS_COLUMNS

- USER_INDEXES

- USER_OBJECTS

- USER_SYNONYMS

- USER_TABLES

- USER_TAB_COLUMNS

- USER_TAB_COMMENTS

- USER_USERS

- USER_VIEWS

B Sample Files

- Sample gateway initialization file

- Sample Oracle Net tnsnames.ora File

- Sample Oracle Net listener.ora File

C DRDAESpecific Parameters

- Modifying the Gateway Initialization File

- Setting Parameters in the Gateway Initialization File

- Syntax and Usage

- Gateway Initialization File Parameters

- DRDA_CACHE_TABLE_DESC

- DRDA_CAPABILITY

- DRDA_CODEPAGE_MAP

- DRDA_COMM_BUFLEN

- DRDA_CONNECT_PARM (SNA format)

- DRDA_CONNECT_PARM (TCP/IP format)

- DRDA_CMSRC_CM_IMMEDIATE

- DRDA_DEFAULT_CCSID

- DRDA_DESCRIBE_TABLE

- DRDA_DISABLE_CALL

- DRDA_FLUSH_CACHE

- DRDA_GRAPHIC_PAD_SIZE

- DRDA_GRAPHIC_LIT_CHECK

- DRDA_GRAPHIC_TO_MBCS

- DRDA_GRAPHIC_CHAR_SIZE

- DRDA_ISOLATION_LEVEL

- DRDA_LOCAL_NODE_NAME

- DRDA_MBCS_TO_GRAPHIC

- DRDA_OPTIMIZE_QUERY

- DRDA_PACKAGE_COLLID

- DRDA_PACKAGE_CONSTOKEN

- DRDA_PACKAGE_NAME

- DRDA_PACKAGE_OWNER

- DRDA_PACKAGE_SECTIONS

- DRDA_READ_ONLY

- DRDA_RECOVERY_PASSWORD

- DRDA_RECOVERY_USERID

- DRDA_REMOTE_DB_NAME

- DRDA_SECURITY_TYPE

- FDS_CLASS

- FDS_CLASS_VERSION

- FDS_INSTANCE

- HS_FDS_FETCH_ROWS

- HS_LANGUAGE

- HS_NLS_NCHAR

- LOG_DESTINATION

- ORA_MAX_DATE

- ORA_NLS10

- ORACLE_DRDA_TCTL

- ORACLE_DRDA_TRACE

- TRACE_LEVEL

D National Language Support

- Overview of NLS Interactions

- Client and Oracle Integrating Server Configuration

- Gateway Language Interaction with DRDA Server

- Gateway Configuration

- NLS Parameters in the Gateway Initialization File

- HS_LANGUAGE

- HS_NLS_NCHAR

- HS_NLS_DATE_FORMAT

- HS_NLS_DATE_LANGUAGE

- Gateway Codepage Map Facility

- Multibyte and DoubleEByte Support in the Gateway

- Message Availability

- Example of NLS Configuration

E Configuration Worksheet

F Quick Reference to Oracle SQL Functions

G Sample Applications

- DB2INS

- ORAIND

Index

List of Figures

- 1-1 The Gateway Architecture

- 6-1 SNA Server Manager Main Screen: Select a Server

- 6-2 Server Properties Dialog Box

- 6-3 Insert Link Service

- 6-4 Select Link Service Properties

- 6-5 Connection Properties Menu

- 6-6 General Connection Properties

- 6-7 Enter Remote Addresses

- 6-8 Enter System Identification

- 6-9 Enter DLC Values

- 6-10 Local LU Properties Menu

- 6-11 Enter Local APPC LU Properties

- 6-12 Set Up Parallel Session

- 6-13 Select APPC Mode Definition

- 6-14 APPC Mode General Properties Dialog Box

- 6-15 Enter the APPC Mode Limits

- 6-16 Set APPC Mode Characteristics

- 6-17 APPC Remote LU Menu

- 6-18 Enter General Remote APPC LU Properties

- 6-19 Remote APPC LU Properties Options

- 6-20 CPI-C Symbolic Destination Name Window

- 6-21 Enter General CPI-C Name Properties

- 6-22 Enter CPI-C Name Properties Partner Information

- 6-23 Relationship Between SNA Server Definitions and Host VTAM Definitions

- 7-1 Choosing a Configuration Scenario

- 7-2 Creating the Node Configuration

- 7-3 Node Definition

- 7-4 Creating Devices

- 7-5 Choosing the Device Type

- 7-6 Configuring a LAN Device

- 7-7 Creating Peer Connections

- 7-8 Defining the Link station

- 7-9 Defining the Adjacent Node

- 7-10 Create Local LUs

- 7-11 Defining Local LUs

- 7-12 Create Partner LUs

- 7-13 Defining Partner LUs

- 7-14 Creating the IBMRDB Mode

- 7-15 Define the IBMRDB Mode

- 7-16 Create the CPI-C Side Information Profile

- 7-17 Define the CPI-C Side Information Profile

- 7-18 Relationship Between IBM Communication Server Definitions and Host VTAM Definitions

- 8-1 Network Configuration Tool

- 8-2 TCP/IP Properties Panel

- 8-3 Define a Name Server

- 12-1 Calling Oracle Stored Procedures in a Distributed Oracle Environment

- 12-2 Running DRDA Server Stored Procedures

- D-1 Architecture of NLS Interactions with Your System Components

- D-2 Gateway Language Interaction with DRDA Server

List of Tables

- 4-1 Steps to Install the Gateway Using the Oracle Universal Installer

- 10-1 Optional DRDA-Specific Parameters

- 12-1 DB2/OS390 SQL Compatibility, by Oracle SQL Function

- 12-2 DB2/Universal Database SQL Compatibility, by Oracle SQL Function

- 12-3 DB2/400 SQL Compatibility, by Oracle SQL Function

- 12-4 DB2/VM SQL Compatibility, by Oracle SQL Function

- 12-5 List of SQL Functions That Can Be Enabled

- 12-6 Data Type Mapping and Restrictions

- 12-7 HS_NLS_DATE_FORMAT Patterns

- 14-1 Parameters That Have Been Renamed

- 15-1 Mapped sqlstate Errors

- C-1 Isolation Levels and Their Descriptions

- D-1 Parameters Needed for NLS Processing in Your System Environments

- E-1 List of Parameters Needed to Configure the Gateway

- F-1 Oracle SQL Functions in Alphabetic Order

Preface

The Oracle Transparent Gateway for DRDA for Microsoft Windows provides users with transparent access to DRDA databases as if they were Oracle databases.

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 DRDA

- 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

- Configuring the SNA server product

You must understand the fundamentals of transparent gateways and the Microsoft Windows operating system before using this guide to install or administer the gateway.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. 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. Accessibility 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 more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers 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, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

TTY Access to Oracle Support Services

To reach AT&T Customer Assistants, dial 711 or 1.800.855.2880. An AT&T Customer Assistant will relay information between the customer and Oracle Support Services at 1.800.223.1711. Complete instructions for using the AT&T relay services are available at http://www.consumer.att.com/relay/tty/standard2.html. After the AT&T Customer Assistant contacts Oracle Support Services, an Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process.

Related Documents

The Oracle Transparent Gateway for DRDA Installation and User's Guide for Microsoft Windows is included as part of your product. Also included is:

Oracle Database Heterogeneous Connectivity Administrator's Guide

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

Oracle Database Administrator's Guide

Oracle Database Concepts

Oracle Database Error Messages

Oracle Database Performance Tuning Guide

Oracle Database Security Guide

Oracle Database Heterogeneous Connectivity Administrator's Guide

Conventions

In this manual, "Windows" refers to any Microsoft Windows operating system.

In examples, an implied carriage return occurs at the end of each line, unless otherwise noted. You must press the Return key at the end of a line of input.

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

> mkdir D:\ORACLE\your_name

All output is shown as it actually appears. For input, refer to the following list. The first part of each line represents the conventions used in this manual, and the second part describes their meanings:

... Horizontal ellipsis points in statements or commands mean that parts of the statement or command (that are not directly related to the example) have been omitted. Vertical ellipsis points in an example also mean that information that is not directly related to the example has been omitted.

italic font indicates that a word or phrase of your choice must be substituted for the term in italic font, such as your actual member name or directory name.

boldface text Boldface type in text indicates a term that is defined in the text.

< > Angle brackets enclose user-supplied names.

{ } Curly braces indicate that one of the enclosed arguments is required. Do not enter the braces themselves.

[ ] Square brackets indicate that the enclosed arguments are optional. You can choose one or none. Do not enter the brackets themselves.

│ 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 examples. When these names appear in text, they may be highlighted in bold. The use of italics indicates that those portions of a file ID that appear in italics can vary.

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.

DOS Prompts

The DOS prompt, >, appears in DOS 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 DOS directory names and should not be confused as a prompt character.

Storage Measurements

Storage measurements use the following abbreviations:

- KB, for kilobyte, which equals 1,024 bytes

- MB, for megabyte, which equals 1,048,576 bytes

- GB, for gigabyte, which equals 1,073,741,824 bytes

Directory Names

Throughout this document, there are references to the directories in which product-related files reside. ORACLE_HOME is used to represent the Oracle home directory. This is the default location for Oracle products. If you have installed into a location other than ORACLE_HOME, replace all references to ORACLE_HOME with the drive and path specification you have used.

1 Introduction

The Oracle Transparent Gateway for DRDA enables you to:

- Integrate heterogeneous database management systems so that they appear as a single homogeneous database system

- Read and write data from Oracle applications to data in DB2/OS390, DB2/400, DB2 Universal Database, DB2/VM, and IBM SQL/DS on VM databases in addition to any Oracle database server data.

Read this chapter for information about the architecture, uses, and features of the Oracle Transparent Gateway for DRDA. It contains the following sections:

- Introduction to the Oracle Transparent Gateway

- Release 10g Gateways

- Gateway Capabilities

- Terms

- Architecture

- Implementation

- How the Gateway Works

- Oracle Tools and the Gateway

- Features

Introduction to the Oracle Transparent Gateway

In today's global economy, information is a company's most valuable resource. Whether you need to analyze new markets, tailor your products to meet local demands, increase your ability to handle complex customer information, or streamline operations, your company requires instant access to current and complete information

Company growth and diversification often mean functioning with a collage of applications and geographically scattered data that may be using incompatible networks, platforms, and storage formats. Diverse application standards and storage formats can make integration of information difficult. Oracle offers integration technologies to overcome these technical barriers. Oracle Enterprise Integration Gateways simplify complex systems and remove obstacles to information, thereby providing your company the opportunity to focus on business.

Protection of Current Investment

Oracle Transparent Gateway for DRDA gives your company the ability to develop its information systems without forfeiting its investments in current data and applications. The gateway gives you access to the Oracle and DB2 data with a single set of applications while you continue to use existing IBM applications to access your DB2 data. You can also use more productive database tools and move to a distributed database technology without giving up access to the current data.

If you choose to migrate to Oracle Database technology and productivity, then the gateway enables you to control the pace of your migration. As you transfer applications from your previous technology to the Oracle Database, you can use the gateway to move the DB2 data into Oracle databases.

Release 10g Gateways

Oracle Database 10g provides the foundation for the next generation of the Oracle Enterprise Integration Gateways Release 10g, which will deliver enhanced integration capabilities by exploiting Oracle Database 10g Heterogeneous Services. Heterogeneous Services is a component of the Oracle Database 10g server. The Oracle Database 10g server provides the common architecture for future generations of the gateways. For detailed information on Oracle Heterogeneous Services, refer to Oracle Database Heterogeneous Connectivity Administrator's Guide.

The version 10 gateways are even more tightly integrated with the Oracle Database 10g server than previous versions, enabling improved performance and enhanced functionality while still providing transparent integration of Oracle and nonEOracle data. For example, connection initialization information is available in the local Oracle Database 10g server, reducing the number of round trips and the amount of data sent over the network. SQL processing is also faster, because statements that are run by an application are parsed and translated once and can then be reused by multiple applications.

Release 10g gateways leverage any enhancements in the Oracle Database 10g server, and you can quickly extend those benefits to the nonEOracle data.

Advantages of the Gateway

Oracle Transparent Gateway for DRDA enables Oracle applications to access the DRDA Application Servers, such as DB2 for OS/390 (MVS), through Structured Query Language (SQL). The gateway and the Oracle Database 10g server together create the appearance that all data resides on a local Oracle Database 10g server, though data might be widely distributed. If data is moved from a DRDA Application Server database to an Oracle Database server, then no changes in application design or function are needed. The gateway handles all differences in both data types and SQL functions between the application and the database.

Gateway Capabilities

Oracle Transparent Gateway for DRDA gives you the power to integrate your heterogeneous systems into a single, seamless environment. This integration enables you to make full use of existing hardware and applications throughout your corporatewide environment. You can eliminate the need to rewrite applications for each configuration, and you can avoid the tedious, errorEprone process of manual data transfer. Together with the Oracle tools, networking, and data server technology, the Oracle Transparent Gateway for DRDA sets a high standard for seamless, enterprise wide information access.

Oracle Transparent Gateway for DRDA enables applications to read and update DB2 data and Oracle data as if all of the data were stored in a single database. As a result, users and application programmers are not required to know either the physical location or the storage characteristics of the data. This transparency not only permits you to integrate heterogeneous data seamlessly, but also simplifies your gateway implementation, application development, and maintenance.

Transparency at All Levels

The Oracle Transparent Gateway for DRDA gives you transparency at every level within your enterprise.

- Location transparency
Users can access tables by name without needing to understand the physical location of the tables.

- Network transparency
The gateways exploit Oracle Net technology to enable users to access data across multiple networks without concern for the network architecture or protocols. TCP/IP protocol is supported.

- Operating system transparency
You can access data that is stored under multiple operating systems without being aware of the operating systems that hold the data.

- Data storage transparency
Data can be accessed regardless of the database or file format.

- Access method transparency
You can use a single dialect of SQL for any data store, eliminating the need to code for databaseEspecific access methods or SQL implementations.

Extended Database Services

Following are some of the more sophisticated Oracle Database 10g server services that are available through the gateway.

- SQL functions
Your application can access all of your data using Oracle SQL, which is rich in features. Advanced Oracle Database 10g server functions, such as outer joins, are available even if the target data stores do not support them in a native environment. The method by which the gateways are integrated with the Oracle Database 10g server ensures that the newest features of each database release are always available immediately to the gateway.

- Distributed capabilities
Heterogeneous data can be integrated seamlessly because Oracle Database distributed capabilities, such as JOIN and UNION, can be applied to nonEOracle data without any special programming or mapping.

- Distributed query optimization
The Oracle Database 10g server can use its advanced query optimization techniques to ensure that SQL statements are run efficiently against any of your data. The data distribution and storage characteristics of local and remote data are equally considered.

- TwoEphase commit protection
The Oracle server twoEphase commit mechanism provides consistency across data stores by ensuring that a transaction that spans data stores is still treated as a single unit of work. Changes are not committed (or permanently stored) in any data store unless the changes can be committed in all data stores that will be affected.

- Stored procedures and database triggers
The same Oracle stored procedures and database triggers can be used to access all of the data, thereby ensuring uniform enforcement of business rules across the enterprise.

Extended Advanced Networking, Internet and Intranet Support

The gateway integration with the Oracle Database 10g server extends (to nonEOracle data) the benefits of the Oracle Internet software, and Oracle Net software and extends the benefits of the Oracle client/server and server/server connectivity software. These powerful features include:

- Application server support
Any Internet or intranet application that can access data in Oracle database can also incorporate information from data stores that are accessible through the gateways. Web browsers can connect to Oracle database using any application server product that supports Oracle software.

- Implicit protocol conversion
Oracle Database and Oracle Net can work together as a protocol converter, enabling applications to transparently access other data stores on platforms that do not support the network protocol of the client. An Oracle Database 10g server can use TCP/IP to communicate with the gateway and another data store.

- Advanced Security
NonEOracle data can be protected from unauthorized access or tampering during transmission to the client. This is done by using the hardwareEindependent and protocolEindependent encryption and CHECKSUM services of Advanced Security.

- Wireless communication
Oracle Mobile Agents, an industryEleading Oracle mobile technology, enables wireless communication to Oracle Database 10g servers or to any databases that are accessible through the gateways. This gives your field personnel direct access to enterprise data from mobile laptop computers.

Dynamic Dictionary Mapping

The simple setup of the gateway does not require any additional mapping. Before an application can access any information, the application must be told the structure of the data, such as the columns of a table and their lengths. Many products require administrators to manually define that information in a separate data dictionary stored in a hub. Applications then access the information using the hub dictionary instead of the native dictionaries of each database. This approach requires a great deal of manual configuration and maintenance on your part. As administrators, you must update the data dictionary in the hub whenever the structure of a remote table is changed.

Inefficient duplication is not necessary with Oracle Transparent Gateway for DRDA. The gateway uses the existing native dictionaries of each database. The applications access data using the dictionaries that are designed specifically for each database, which means that no redundant dictionary ever needs to be created or maintained.

SQL

Oracle Transparent Gateways ease application development and maintenance by enabling you to access any data using a uniform set of SQL queries. Changes to the location, storage characteristics, or table structure do not require any changes to the applications. ANSI and ISO standard SQL are supported, along with powerful Oracle extensions.

Data Definition Language

Oracle applications can create tables in target data stores by using native data definition language (DDL) statements.

Data Control Language

You can run native data control language (DCL) statements from an Oracle environment, enabling central administration of user privileges and access levels for heterogeneous data stores.

Passthrough and Native DB2 SQL

Running of native DB2 SQL can be passed through the gateway for processing directly against DB2. This enables applications to send statements, such as a DB2 CREATE TABLE, to the gateway for running on a target DB2 system.

Stored Procedures

The gateway enables you to exploit both Oracle and nonEOracle stored procedures, leveraging your investments in a distributed, multi database environment. Oracle stored procedures can access multiple data stores easily, without any special coding for heterogeneous data access.

Oracle Stored Procedures

Oracle stored procedures enable you to access and update DB2 data by using centralized business rules that are stored in the Oracle Database 10g server. Using Oracle stored procedures can increase database performance by minimizing network traffic. Instead of sending individual SQL statements across the network, an application can send a single EXECUTE command to begin an entire PL/SQL routine.

Native DB2 Stored Procedures

The gateway can run DB2 stored procedures using standard Oracle PL/SQL. The Oracle application run the DB2 stored procedure as if it were an Oracle remote procedure.

Languages

Any application or tool that supports the Oracle Database 10g server can access over thirty different data sources through the Oracle gateways. A wide variety of open system tools from Oracle and thirdEparty vendors can be used, even if the data is stored in legacy, proprietary formats. Hundreds of tools are supported, including ad hoc query tools, Web browsers, turnkey applications, and application development tools.

Oracle Database Server Technology and Tools

The gateway is integrated into the Oracle Database server technology, which provides global query optimization, transaction coordination for multisite transactions, support for all Oracle Net configurations, and so on. Tools and applications that support the Oracle Database server can be used to access heterogeneous data through the gateway.

SQL*Plus

You can use SQL*Plus for moving data between databases. This product gives you the ability to copy data from your department databases to corporate Oracle databases.

TwoEPhase Commit and Multisite Transactions

The gateway can participate as a partner in multisite transactions and twoEphase commit. How this occurs depends on the capabilities of the underlying data source, meaning that the gateway can be implemented as any one of the following:

- A full twoEphase commit partner

- A commit point site

- A singleEsite update partner

- A readEonly partner

The deciding factors for the implementation of the gateway are the locking and transactionEhandling capabilities of the target database.

Oracle Transparent Gateway for DRDA, by default, is configured as a commit point site (that is, commit confirm protocol). Optionally, you can configure the gateway as readEonly if you choose to enforce readEonly capability through the gateway. Other protocols are not supported. Refer to "ReadEOnly Gateway" in Chapter 11, "Using the Gateway".

Site Autonomy

All Oracle Database server products, including gateways, supply site autonomy. For example, administration of a data source remains the responsibility of the original system administrator. Site autonomy also functions so that gateway products do not override the security measures that are established by the data source or the operating environment.

Migration and Coexistence

The integration of a data source through the gateway does not require any changes to be made to applications at the data source. The result is that the Oracle Database server technology is nonintrusive, providing coexistence and an easy migration path.

Security

The gateway does not bypass existing security mechanisms. Gateway security coexists with the security mechanisms that are already used in the operating environment of the data source.

Functionally, gateway security is identical to that of an Oracle Database server, as described in the Oracle Database Administrator's Guide. Oracle Database security is mapped to the data dictionary of the data source.

Terms

The terms that are used in this guide do not necessarily conform to IBM terminology. The following table presents several terms and their meanings as used within this guide:

Terms

Meaning

DRDA data

Any database data that is accessed through DRDA

DRDA database

The collection of data that belongs to a DRDA Server

DRDA Server

A database server that can be accessed through DRDA. IBM terminology for a DRDA Server is a DRDA Application Server, or AS.

DRDA server type

A specific database product or program that can act as a DRDA server

Oracle integrating server

Any Oracle Database 10g server instance that communicates with the Oracle Transparent Gateway for DRDA to distribute database access operations to a DRDA Server. The Oracle integrating server can also be used for non-gateway applications.

DB2 Universal Database

A generic name for the UNIX-based implementations of DB2. DB2/UDB is frequently used as an abbreviation for DB2 Universal Database.

Architecture

The Oracle Transparent Gateway for DRDA works with the Oracle Database 10g server to shield most of the differences of the nonEOracle database from Oracle applications. This means that the Oracle applications can access the Oracle Database 10g server data and also can access the DRDA database data as if it were Oracle data located at the Oracle integrating server.

The architecture consists of the following main components:

- Client
The client is an Oracle application or tool.

- Oracle integrating server
The Oracle integrating server is an Oracle Database instance that is accessed by an Oracle Database 10g server with procedural and distributed options. Usually, the Oracle integrating server is installed on the same host as the gateway, but this is not a requirement. The Oracle integrating server and the gateway communicate in the normal Oracle serverEtoEserver manner.

If the Oracle integrating server is not on the host where the gateway resides, then you must install the correct Oracle networking software on the platform where the server resides. For Oracle Database 10g, you must install Oracle Net on the Oracle Database 10g server system.

- Oracle Transparent Gateway for DRDA
The gateway must be installed on hosts that are running the appropriate operating system.

If the Oracle integrating server is not on the same host, then you must also install Oracle Net so that the gateway and Oracle Database 10g server can communicate.

- DRDA Server
The DRDA Server must be a DB2/OS390, DB2/400, DB2 Universal Database, or DB2 server for VM database on a system that is accessible to the host using either the SNA or TCP/IP protocol.

Multiple Oracle Database 10g servers can access the same gateway. A single host gateway installation can be configured to access more than one DRDA Server.

Figure 1-1 illustrates the gateway architecture that was just described.

Figure 1-1 The Gateway Architecture

Implementation

When the gateway is installed on your host, it has some of the same components as an Oracle Database instance on Microsoft Windows. The gateway has the following components:

- A base file directory, similar to the one that is associated with the ORACLE_HOME environment variable of an Oracle Database instance

- A gateway system identifier (SID), comparable to the ORACLE_SID of an Oracle Database instance

- Oracle Net to support communication between the Oracle integrating server and the Oracle Transparent Gateway for DRDA

The gateway does not have:

- Control, redo log, or database files

- The full set of subdirectories and ancillary files that are associated with an installed Oracle Database 10g server

Because the gateway does not have background processes and does not need a management utility such as Oracle Enterprise Manager, you do not need to start the gateway product. Each Oracle Database 10g server user session that accesses a particular gateway creates an independent process on the host. This process runs the gateway session and runs SNA or TCP/IP functions to communicate with a DRDA Server.

How the Gateway Works

The gateway has no database functions of its own. Instead, it provides an interface by which an Oracle Database 10g server can direct part or all of a SQL operation to a DRDA database.

The gateway that is supporting the DRDA Server is identified to the Oracle integrating server by using a database link. The database link is the same construct that is used to identify other Oracle Database 10g server databases. Tables on the DRDA Server are referenced in SQL as:

table_name@dblink_name

or

owner.table_name@dblink_name

If you create synonyms or views in the Oracle integrating server database, then you can refer to tables on the DRDA Server by using simple names as though the table were local to the Oracle integrating server.

When the Oracle integrating server encounters a reference to a table that is on the DRDA Server, the applicable portion of the SQL statement is sent to the gateway for processing. Any host variables that are associated with the SQL statement are bound to the gateway and, therefore, to the DRDA Server.

The gateway is responsible for sending these SQL statements to the DRDA Server for processing and for fielding and is also responsible for returning responses. The responses are either data or messages. Any conversions between Oracle data types and DRDA data types are performed by the gateway. The Oracle integrating server and the application read and process only Oracle data types.

SQL Differences

Not all SQL implementations are the same. The Oracle Database 10g server supports a larger set of builtEin functions than the databases that are currently accessed through the gateway. The Oracle integrating server and the gateway work together to convert SQL to a form that is compatible with the specific DRDA Server.

During this conversion, an Oracle Database 10g server function can be converted to a function that is recognizable to the specific DRDA Server. For example, the Oracle Database 10g server NVL function is converted to the DB2 VALUE function.

Alternatively, the Oracle integrating server withholds functions that are not executable by the DRDA Server, and it performs them after rows are fetched from the DRDA database. This processing generally applies to SELECT statements. The Oracle integrating server and the gateway cannot perform this kind of manipulation on UPDATE, INSERT, or DELETE statements because doing so changes transaction semantics.

Oracle Tools and the Gateway

Use the gateway to run applications, such as Oracle tools, that read and write data that is stored in DRDA databases.

Although the Oracle Transparent Gateway for DRDA provides no new application or development facilities, it extends the reach of existing Oracle tools to include data in nonEOracle databases that support DRDA.

Using the Oracle Transparent Gateway for DRDA with other Oracle products can greatly extend the capabilities of the standalone gateway. The following examples demonstrate how powerful the gateway is with other Oracle tools.

SQL*Plus

Use SQL*Plus and the Oracle Transparent Gateway for DRDA to create a distributed database system, providing an easyEtoEuse transfer facility for moving data between the distributed databases. One possible use is to distribute the data in your corporate Oracle Database to departmental DRDA databases. You can also distribute data in your corporate DRDA database to departmental Oracle Databases.

Features

Following is a list of important features that characterize this release of the gateway.

Heterogeneous Services Architecture

This release of the Oracle Transparent Gateway for DRDA uses the Oracle Heterogeneous Services component within the Oracle Database 10g server. Heterogeneous Services is the building block for the next generation of Oracle Enterprise Integration Gateways.

For detailed information about Heterogeneous Services, refer to the Oracle Database Heterogeneous Connectivity Administrator's Guide.

Performance Enhancements

Oracle Transparent Gateway for DRDA contains several internal performance enhancements. This product has shown major improvements in response time and CPU utilization for all relevant address spaces for a variety of workloads compared to version 9 gateways. The actual performance improvement at your site might vary, depending on your installation type and workload.

Fetch Reblocking

The array size of the application for SELECT is effective between the application and the Oracle integrating server. However, the array block size and the block fetch between the Oracle integrating server and the gateway are controlled by two Heterogeneous Services initialization parameters, HS_RPC_FETCH_SIZE and HS_RPC_FETCH_REBLOCKING. These parameters are specified in the gateway initialization file. Refer to the Oracle Database Heterogeneous Connectivity Administrator's Guide for more information.

Oracle Database 10g Passthrough Supported

You can use the Oracle Database 10g DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE feature to pass commands or statements (that are available in the DRDA database) through the gateway.

Retrieving Result Sets Through Passthrough

Oracle Transparent Gateway for DRDA provides a facility to retrieve result sets from a select SQL statement that is run with passthrough. Refer to "Retrieving Result Sets Through Passthrough" for additional information.

Support for TCP/IP

This release of the gateway supports the TCP/IP communication protocol between the gateway and the DRDA Server. Refer to Chapter 8, "Configuring TCP/IP" for further information.

Native Semantics

This release of the gateway supports the ability to selectively enable or disable postEprocessing of various SQL functions by the DRDA Server. Refer to "Native Semantics" for further information.

Columns Supported in a Result Set

Oracle Transparent Gateway for DRDA supports up to 1000 columns in a result set.

EXPLAIN_PLAN Improvement

The EXPLAIN_PLAN table contains the actual SQL statements passed to the DRDA Server from the Oracle Database 10g server through the gateway.

Heterogeneous Database Integration

The gateway support for ANSIEstandard SQL enables read/write access to DRDA databases. Even if your data exists on different platforms in different applications, new applications can use all data, regardless of location.

Minimum Impact on Existing Systems

The gateway does not require installation of additional Oracle software on your OS/390 (MVS), AS/400, VM, UNIX or Microsoft Windows target system. The database interface that it uses is provided by IBM and is built into the DRDA database products and SNA or TCP/IP facilities that already exist on these platforms.

Configuring an IBM system for DRDA access typically consists of defining the SNA or TCP/IP resources involved and establishing access security definitions specific to the target database.

Large Base of Data Access

DRDA Application Server Function is supported by most IBM DB2 database products.

Application Portability

The ability of the gateway to interface with heterogeneous databases makes it possible to develop a single set of portable applications that can be used against both Oracle and IBM databases, and any other databases for which Oracle Corporation provides gateways.

Remote Data Access

Location flexibility is maximized because the gateway architecture permits network connections between each of the components. The application can use the Oracle clientEserver capability to connect to a remote Oracle integrating server through Oracle Net. The Oracle integrating server can connect to a remote gateway using a database link. The gateway connects to DRDA Servers through SNA or TCP/IP network facilities.

The benefits of remote access are that it:

- Provides a means to allocate the suitable resource to a given task
You can, for example, move application development off expensive processors and onto costEefficient workstations or microcomputers.

- Expands the number of available data sources
Without remote access, you are limited to the data that is available in the local environment. With remote access, your data sources are limited only by your networks.

- Provides a means to tailor an application environment to a given user
For example, some users prefer a blockEmode terminal environment, while others prefer a bitEmapped, graphics-driven terminal environment. Remote access can satisfy both because you are not constrained by the interface environment that is imposed by the location of your data.

Support for Distributed Applications

Because the gateway gives your application direct access to DRDA data, you eliminate the need to upload and download large quantities of database data to other processors. Instead, you can access data where it is, when you want it, without having to move the data between systems and thus risk unsynchronized and inconsistent data. Avoiding massive data replication can also reduce aggregate disk storage requirements over all of your systems.

However, if your system design requires moving data among the systems in a network, SQL*Plus and the gateway can simplify the data transfer. With a single SQL*Plus command, you can move entire sets of data from one node of the network to another and from one database to another.

You can pass commands and statements that are specific to your DRDA database through the gateway to be run by the DRDA database. For example, you can pass DB2/OS390 commands through the gateway for DB2 to run. You can also run stored procedures defined in nonEOracle databases.

Application Development and End User Tools

Through the gateway, Oracle extends the range of application development and user tools that you can use to access the IBM databases. These tools increase application development and user productivity by reducing prototype, development, and maintenance time. Current Oracle users do not have to learn a new set of tools to access data that is stored in DRDA databases. Instead, they can access Oracle and DRDA data with a single set of tools.

With the gateway and the application development tools that are available from Oracle, you can develop a single set of applications to access Oracle data and DRDA data. Users can use the decision support tools that are available from Oracle to access Oracle data and DRDA data. These tools can run on remote systems that are connected through Oracle Net to the Oracle integrating server.

When designing applications, keep in mind that the gateway is designed for retrieval and relatively light transaction loads. The gateway is not currently designed to be a heavy transaction processing system.

Password Encryption Utility

This release of the gateway includes a utility to support encryption of plainEtext passwords in the gateway initialization file. Refer to Chapter 13, "Security Considerations" for details.

Support for DB2/OS390 V6, V7, and V8 Stored Procedures

This release of the gateway supports the native stored procedure catalogs in DB2 V6, V7, and V8 (SYSIBM.SYSROUTINES and SYSIBM.SYSPARMS).

Codepage Map Facility

This release of the gateway supports external mapping of IBM CCSIDs to Oracle character sets. Refer to "Gateway Codepage Map Facility" in Appendix D, "National Language Support".

IBM DB2 Universal Database Support

This release supports IBM DB2 Universal Database.

IBM DB2 Version 5.1 ASCII Tables

IBM DB2 version 5.1 supports ASCII and EBCDIC character sets. The character set selection is defined during table creation. The Oracle Transparent Gateway for DRDA supports access to EBCDIC tables and ASCII tables. Refer to Appendix D, "National Language Support".

Read-Only Support

This release enables the gateway to be configured as a read-only gateway. In this mode, no modifying of user data is permitted. For more information, refer to "DRDA_READ_ONLY".

Support for Graphic and Multibyte Data

This release of the gateway adds support for DB2 GRAPHIC and VARGRAPHIC data types. Refer to Chapter 12, "Developing Applications".

Support for DB2/UDB on Intel Hardware

This release of the gateway adds support for DRDA Servers running on Microsoft Windows and Linux on Intel hardware.

Data Dictionary Support for DB2/UDB

This release of the gateway adds Oracle data dictionary support for DB2 UDB V7. Refer to "Sample SQL scripts" for more information.

2 Release Information

This chapter provides information specific to this release of the Oracle Transparent Gateway for DRDA. It includes the following sections:

- Product Set

- Changes and Enhancements

- Bugs Fixed in 10g Release 2 (10.2)

- Known Problems

- Known Restrictions

Product Set

The following is a list of the production components that are included in the product CDEROM:

- Oracle Transparent Gateway for DRDA, Release 10.1.0.2.0

- Oracle Net, release 10.2.1.0

Changes and Enhancements

Following is a list of changes and enhancements that are unique to this release of the gateway.

Gateway Password Encryption Tool

The Gateway Password Encryption tool (g4drpwd) has been replaced by a generic feature which is now part of Heterogenous Services. Refer to Chapter 13, "Security Considerations" for more information.

Product Migration

Refer Chapter 14, "Migration and Coexistence with Existing Gateways" for information about migrating product configurations from previous releases for additional changes or requirements.

Bugs Fixed in 10g Release 2 (10.2)

4013463

GARBAGES CONTAINED IN ERROR MESSAGE FROM TG4DRDA

3882675

TG4DRDA SELECT FOR UPDATE ERROR WITH G4DRSRVD

3650803

MEMORY LEAK IN G4DRSRV DOING SELECT STATEMENT

3640384

ORA-28500 ON SELECT FOR UPDATE FROM TG4DRDA

3610131

INDEX STATS MAY NOT BE QUERIED CORRECTLY

3514233

SETTING DRDA_OPTIMIZE_QUERY=TRUE DOES NOT GENERATE TABLE STATS

3429017

LINKING ERROR FOR G4DRSRV WHEN USING REDHAT AS V3

3421215

IU GUIDE DIDN'T SAY HOW TO CONFIG DRDA_CONNECT_PARM IN LINUX

3287626

ENGLISH NAME OF "TAIWAN" DOESN'T SEEM TO BE APPROPRIATE

3143686

QA - 10G - CAN NOT SELECT FROM DATA DICTIONARY TABLES

4218317

COUNT(COLNAME) NOT TRANSLATED TO COUNT(*)

4260112

ORA-1001 WITHOUT THE DETAIL RETURNS FROM TG4DRDA

4065600

GARBAGES CONTAINED IN ORA-1 ERROR MESSAGE FROM TG4DRDA

3965425

ORA-07445 [_MEMCPY()+772] REPEATABLE READ ISOLATION LEVEL IS NOT WORKING

3709345

PSR 9.2.0.5.0 BREAKS CALL DB2 STORED PROCEDURE WITH DECIMAL PARM. SQLCODE -310

3130329

TG4DRDA LOOPS IF QRWTSRVR JOB KILLED WHILE GATEWAY IS IN GDJCRCV

Known Problems

The problems that are documented in the following section are specific to the Oracle Transparent Gateway for DRDA and are known to exist in this release of the product. These problems will be fixed in a future gateway release. If you have any questions or concerns about these problems, then contact Oracle Support Services.

A current list of problems is available online. Contact your local Oracle office for information about accessing this online information.

Known Restrictions

The following restrictions are known to exist for the products in this release. Restrictions are not scheduled to change in future releases. Also refer to Chapter 12, "Developing Applications", for information about limitations when developing your applications.

Accessing DB2 Alias Objects

If you need to access DB2 alias objects on a remote DB2 system, then you must specify DRDA_DESCRIBE_TABLE=FALSE initialization parameter in the gateway initialization file.

Oracle SQL Command INSERT

When copying data from an Oracle server to a DRDA Server, the Oracle SQL command INSERT is not supported. The SQL*Plus COPY command must be used. Refer to Chapter 11, "Using the Gateway", for more information.

DB2 Considerations

DD Basic Tables and Views

The owner of DD basic tables and views is OTGDB2. This cannot be changed.

SUBSTR Function PostEProcessed

The SUBSTR function can be used with the Oracle Server in ways that are not compatible with a DRDA Server database such as DB2/OS390. Therefore, the SUBSTR function is postEprocessed. However, it is possible to enable the server to process it natively using the "Native Semantics" feature. Refer to Chapter 12, "Developing Applications", for details.

AVS Mapping User IDs (DB2/VM)

APPC VTAM Support (AVS) has problems mapping user IDs that are sent using lowercase letters or special characters. Contact your IBM representative for additional information about this problem.

Support for DRDA Server Character Sets

Support (for character sets that are used by a DRDA Server) is configurable through the gateway Codepage Map Facility. Refer to Appendix D, "National Language Support" for more information.

data type Limitations

Refer to "DRDA Data Type to Oracle Data Type Conversion" for detailed information about data types.

SAVEPOINT Command Is Not Supported

Oracle Transparent Gateway for DRDA does not support the Oracle command SAVEPOINT.

Null Values and Stored Procedures

Null values are not passed into, or returned from, calls to stored procedures through the gateway.

String Concatenation of Numbers

String concatenation of numbers is not permitted in DB2/400, DB2/UDB, and DB2/OS390. For example, 2││2 is not permitted.

GLOBAL_NAMES Initialization Parameter

If GLOBAL_NAMES is set to TRUE in the Oracle server INIT.ORA file, then to be able to connect to the gateway, you must specify the Heterogeneous Services (HS) initialization parameters, HS_DB_DOMAIN and HS_DB_NAME, in the Gateway Initialization Parameter file to match the value of the Oracle server DB_DOMAIN parameter. Refer to Chapter 10, "Configuring the Gateway", for more information.

Binding the DRDA Package on DB2/UDB

The DRDA gateway package must be bound on the DRDA Server before the gateway can perform any SQL operations. Because of a DB2/UDB restriction, the ORACLE2PC table must be created in the DB2/UDB database before the package can be bound. For details, refer to Chapter 10, "Configuring the Gateway".

Date Arithmetic

In general, the following types of SQL expression forms do not work correctly with the gateway because of DRDA Server limitations:

date + number
number + date
date - number
date1 - date2

DRDA Servers do not permit number addition or subtraction with date data types. The date and number addition and subtraction (date + number, number + date, date - number) forms are sent through to the DRDA Server where they are rejected.

Also, DRDA Servers do not perform date subtraction consistently. When you subtract two dates (date1 - date2), differing interpretations of date subtraction in the DRDA Servers cause the results to vary by server.

Note:
Avoid date arithmetic expressions in all gateway SQL until date arithmetic problems are resolved.

Row Length Limitation

Because of a restriction of the DRDA architecture, rows with aggregate length exceeding 32 K bytes in DRDA representation cannot be stored or retrieved.

LONG data type in SQL*Plus

SQL*Plus cannot fetch LONG columns from the Oracle Transparent Gateway for DRDA.

Dictionary Views Are Not Provided for DB2/VM

Currently, the Oracle Transparent Gateway for DRDA provides SQL for defining DB2/OS390, DB2/400, and DB2/UDB views that emulate parts of the Oracle Database dictionary. These are required for certain applications and tools that query dictionary tables. View definitions for DB2/VM are not provided in this release.

Single Gateway Instance per DRDA Network Interface

When installing the gateway, a proper DRDA network interface must be chosen. Only one DRDA network interface may be chosen and installed per gateway instance. If the gateway product is reinstalled, and if a network interface different from the previous installation is chosen, then the new choice will overlay the current installation. Reconfiguration of the gateway's initialization parameters must occur at this point to ensure proper gateway operation. If you want to have both SNA and TCP/IP DRDA Network Interfaces installed, then you must install two separate gateway homes.

Stored Procedures and transaction integrity

IBM DB2 has introduced a feature called Commit on Return for stored procedures. This feature enables DB2 to perform an automatic commit after a stored procedure runs successfully. This feature is enabled when the procedure is created. To ensure data integrity, this feature is not supported by the Oracle Transparent Gateway for DRDA in a heterogeneous environment. When attempting to call a stored procedure which has this feature enabled, through the gateway, the gateway will return an error message ORA-28526 or PLS-00201 (identifier must be declared).

Note:
This restriction applies to DB2 for MVS or z/OS as of v5.1 and DB2/UDB as of v8.1.

Stored Procedure and User Defined Function Support

The gateway supports processing of stored procedures and user defined functions through the following DRDA Servers:

DB2/OS390 V4.1 or later

DB2/400 V3.1 or later

DB2/UDB V7.1 or later

SQL Limitations

Oracle ROWID Column

The DB2 ROWID column is not compatible with the Oracle ROWID column. Because the ROWID column is not supported, the following restrictions apply:

- UPDATE and DELETE are not supported with the WHERE CURRENT OF CURSOR clause. To update or delete a specific row through the gateway, a condition style WHERE clause must be used. (Bug No. 205538)
When UPDATE and DELETE statements are used, in precompiler and PL/SQL programs, they rely internally on the Oracle ROWID function.

- Snapshots between Oracle servers and DB2 are not supported.
Snapshots rely internally on the Oracle ROWID column.

Oracle Bind Variables

Oracle bind variables become SQL parameter markers when used with the gateway. Therefore, the bind variables are subject to the same restrictions as SQL parameter markers.

For example, the following statements are not permitted:

WHERE :x IS NULL
WHERE :x = :y

CONNECT BY Is Not Supported

Oracle Transparent Gateway for DRDA does not support CONNECT BY in SELECT statements.

COUNT Function Compatibility

The following DRDA server releases do not support all forms of the COUNT function, specifically COUNT(colname) and COUNT(ALL colnames):

DB2 OS/390 V6,

DB2/VM V6 and V7

The default for all DRDA server platforms (except DB2/VM) is for all forms of COUNT to be passed to the DRDA server as it is. For DB2/VM, the forms COUNT(colname) and COUNT(ALL colname) have been disabled by default and will be post-processed.

If the gateway is to be used with one of the above releases of DRDA servers, then it may be necessary to disable the default usage of this form of COUNT.

Refer to Mapping the COUNT Function and Native Semantics for details on how to disable or enable compatibility for these forms of COUNT function.

3 System Requirements

This chapter provides information about hardware and software requirements that is specific to this release of the Oracle Transparent Gateway for DRDA. This chapter includes the following sections:

- Hardware Requirements

- Software Requirements

- Documentation Requirements

Hardware Requirements

The following are the minimum hardware requirements for the Oracle Transparent Gateway for DRDA on Microsoft Windows.

Processor

This gateway requires a host with an Intel or 100% compatible PC with a PentiumEbased processor that can run the required version of Microsoft Windows. Refer to the Oracle Database Installation Guide for Microsoft Windows (32-Bit) and to the certification matrix on Oracle MetaLink for the most up-to-date list of certified hardware platforms and operating system version requirements to operate the gateway for the system. The Oracle MetaLink web site can be found at the following URL:

http://metalink.oracle.com/

Memory

For this release, 64 MB of real memory is the recommended minimum for running one instance of the gateway. Running additional instances of the Oracle Transparent Gateway for DRDA might require additional real memory or increased swap space to achieve reasonable performance.

The total real memory requirement for each concurrent use of the gateway depends on the following factors:

- Number of concurrent APPC connections opened by each user

- Number of concurrent TCP/IP connections opened by each user

- Number of data items being transferred between the gateway and the remote transaction program

- Additional factors such as configured network buffer size

Network Attachment

The hardware requires any network attachment supported by either Microsoft SNA Server for SNA communication or Microsoft Windows Sockets for TCP/IP communication. The network attachment for SNA is typically a Token Ring or SDLC Coaxial attachment. The hardware must support independent LUs if you want concurrent SNA access. The network attachment for TCP/IP is typically an Ethernet attachment.

Disk Space

260 MB of disk space is required for installation.

Software Requirements

The system software configuration described in these requirements is supported by Oracle as long as the underlying system software products are supported by their respective vendors. Verify the latest support status with your system software vendors.

Operating System

The Oracle Transparent Gateway for DRDA will run on the following operating systems:

- Microsoft Windows NT Server, version 4.0 (with Service Pack 6 or later)

- Microsoft Windows NT Workstation, version 4.0 (with Service Pack 6 or later)

- Microsoft Windows 2000 Server (with Service Pack 2 or later)

- Microsoft Windows 2000 Professional (with Service Pack 2 or later)

- Microsoft Windows 2003 Server

- Microsoft Windows XP Professional

Refer to the certification matrix on Oracle MetaLink for the most up-to-date list of certified hardware platforms and operating system version requirements to operate the gateway for your system. The Oracle MetaLink Web site can be found at the following URL:

http://metalink.oracle.com/

DRDA Databases

You must have at least one of the following DRDA servers at a supported release level:

- DB2/OS390

- DB2/VM

- DB2/400

- DB2/Universal Database

Communications

Supported SNA network software are:

- Microsoft SNA Server or Client, version 3.0 or version 4.0, or Host Integration Server, Version 5.0

- IBM Communications Server, Version 5.0 or 6.0

Note:
Version 5.0 requires the following patches:

- JR12583 (Super fix)

- JR12539 (individual Local LUs fix)

Oracle Database server

The Oracle Database server which is to act as the Oracle integrating server requires the latest released patch set for Oracle Database 10g server release 10.2, 10.1, or Oracle9i server release 9.2.

Oracle Networking Products

If the Oracle integrating server is not on the same host as the gateway, then Oracle Net is required to support communication between the Pentium-based host and the Oracle integrating server.

The following Oracle networking products are required on the same system as the Oracle Database 10g server:

- Oracle Net Client 10.2.0.1.0

- an Oracle Adapter, version 10.2.0.1.0

Oracle Net software is included in this Oracle Transparent Gateway for DRDA release. Your gateway license includes a license for Oracle Net and an adapter of your choice. This license restricts the use of Oracle Net for gateway access.

Documentation Requirements

In addition to the documentation provided with the Oracle Transparent Gateway for DRDA distribution kit, the following Oracle documentation is recommended:

- Oracle Database Administrator's Guide

- Oracle Database Installation Guide for Microsoft Windows (32-Bit)

- Oracle Database Application Developer's Guide - Fundamentals

- Oracle Database Heterogeneous Connectivity Administrator's Guide

- Oracle Database Error Messages

- Oracle Database Advanced Security Administrator's Guide

- Oracle C++ Call Interface Programmer's Guide

- Oracle Call Interface Programmer's Guide

- SQL*Plus User's Guide and Reference

- Oracle Database PL/SQL User's Guide and Reference

- Oracle Database SQL Reference

- Oracle Database Net Services Administrator's Guide

- Oracle Database Net Services Reference

In addition to the Oracle documentation, ensure that you have the required documentation for the platform, for the operating system, and for theDRDA Server (DB2/OS390, DB2/400, DB2 Universal Database, or DB2 server for VM).

IBM publications that describe distributed relational databases might also be useful.

4 Installing the Gateway

This chapter provides general information about gateway installation that is specific to this release of the Oracle Transparent Gateway for DRDA for Microsoft Windows. This chapter includes the following sections:

- Introduction

- Before You Begin

- Checklist for Gateway Installation

- Installation Overview

- Preinstallation

- Installing the Gateway from the Installation Media

- Installation Complete

Introduction

The complete Oracle Transparent Gateway for DRDA for Microsoft Windows installation process is divided into installation and configuration tasks. This process is described in Chapters 4 through 8. If this is the first time the gateway has been installed on your Pentium-based host, then you must perform all the steps documented in these chapters.

The installation tasks include:

- Ensuring that your hardware and software requirements are met

- Loading and installing the gateway software from the distribution medium into your system

- Determining your gateway system identifier

- Reconfiguring your network

An installation checklist follows, which you can use to check off each completed step in the process.

Before You Begin

This chapter requires you to enter parameters that are unique to your system in order to properly configure the gateway. Refer to Appendix E, "Configuration Worksheet" for a worksheet listing all the installation parameters that you will need to know in order to complete the configuration process. Ask your network administrator to provide these parameters before you begin.

You will also need to confirm that all hardware and software requirements have been met. Refer to Chapter 3, "System Requirements" to verify these requirements.

Checklist for Gateway Installation

Use the following checklist for installing the gateway:

- Step 1: Log on to the host

- Step 2: Load the CD-ROM into the CD-ROM Drive

- Step 3: Start the Oracle Universal Installer on Microsoft Windows

- Step 4: Step through the Oracle Universal Installer

- Step 5: Verify Installation Success

Installation Overview

The primary installation tasks are presented with the assumption that you will configure the gateway with a single Oracle integrating server and a single DRDA database. The steps for expanding the configuration to multiple integrating servers and multiple DRDA databases are described in Chapter 10, "Configuring the Gateway".

For general information about installing Oracle products and how to use the Oracle Universal Installer, refer to the Oracle Database Installation Guide for Microsoft Windows (32-Bit).

Preinstallation

ORACLE_HOME is the root directory in which Oracle software is installed.

Throughout this book, ORACLE_HOME is used to refer to the home directory of the Oracle Transparent Gateway for DRDA for Microsoft Windows, unless specifically stated otherwise.

Installing the Gateway from the Installation Media

The Oracle Universal Installer for Microsoft Windows is provided on the installation media with the gateway.

Step 1: Log on to the host

Log on to your host computer as a member of the Administrators group.

Step 2: Load the CD-ROM into the CD-ROM Drive

Use any CDEROM drive that is attached to the Pentium-based host (either locally or as a shared resource) as a logical drive to install the gateway. If the CDEROM drive cannot copy files to your hard disk, then refer to your CDEROM documentation. The installation steps are presented with the assumption that the CDEROM drive is mapped to the G: drive.

To load the gateway distribution CDEROM:

1. Insert the gateway distribution CDEROM into the CDEROM drive.

2. Verify that the drive is assigned to the logical drive that you selected and that you can access files on the CDEROM.

Step 3: Start the Oracle Universal Installer on Microsoft Windows

If you previously installed another Oracle Microsoft Windows product, such as an earlier version of the Oracle server or the gateway, then Oracle Universal Installer has already been set up in the Microsoft Windows program menu.

Start the Oracle Universal Installer from the Start menu rather than by using Microsoft Windows Explorer.

1. From the Start menu, click Run.

2. Enter the path and executable file name:

G:\SETUP.EXE

3. Click OK.

Step 4: Step through the Oracle Universal Installer

The Oracle Universal Installer is a menuEdriven utility that guides you through installation of the gateway by prompting you with action items. The action items and the sequence in which they appear depend on your platform. Use the following table as a guide to the installation, following the instructions in the Response column.

Table 4-1 Steps to Install the Gateway Using the Oracle Universal Installer

Prompt

Response

Welcome

Click Next.

Specify Home Details

Check that the destination path points to your ORACLE_HOME. Click Next.

Available Product Components

Open the Oracle Transparent Gateways product group and select Oracle Transparent Gateway for DRDA. Open the Oracle Transparent Gateway for DRDA product group, if not already open, and select one protocol from the list of supported protocols. Remove selection from everything else for a standalone gateway installation. Click Next.

DRDA Network Interface Product Software

If the SNA protocol was selected, choose the network interface software suitable for this installation of the gateway. Click Next. If the SNA protocol was not selected, this panel does not appear.

Summary

Verify the products to be installed. Click Next.

Step 5: Verify Installation Success

After the Oracle Universal Installer confirms that the installation has ended, verify that the installation was successful. To do this, check the contents of the installation log file, which is located in the C:\Program Files\Oracle\Inventory\logs directory. The default file name is InstallActionsdate.LOG.

Installation Complete

Your gateway installation is now complete. Proceed with the configuration tasks that are described in Chapters 5 through 10.

Removing the Gateway

Removing the Oracle Transparent Gateway for DRDA requires the use of the Oracle Universal Installer. Follow the procedures below to remove the gateway:

1. To restart the Oracle Universal Installer, refer to the installation process found earlier in this chapter in "Installing the Gateway from the Installation Media", and repeat the following three steps (Steps 1, 2, and 3):

1. Step 1: Log on to the host

2. Step 2: Load the CD-ROM into the CD-ROM Drive

3. Step 3: Start the Oracle Universal Installer on Microsoft Windows

2. When the Welcome panel appears, select Advanced Installation and Click Next. Then, in the File Locations panel, click Installed Products.

3. In the list of installed products, select the Gateway product and any other products that you wish to remove, and click Remove.

5 Configuring the DRDA Server

The steps for configuring your remote DRDA Server apply to the following DRDA Servers:

- Checklists for Configuring the DRDA Server

- DB2/OS390

- DB2/400

- DB2/UDB (Universal Database)

- DB2/VM

Configuring a DRDA database to enable access by the gateway requires actions on the DRDA database and on certain components of the host operating system. Although no Oracle software is installed on the host system, access to, and some knowledge of, the host system and DRDA database are required during the configuration. Refer to the vendor documentation for complete information about your host system and DRDA database.

Checklists for Configuring the DRDA Server

Use the following checklists for configuring the DRDA Server.

DB2/OS390

- Step 1: Configure the Communications Server

- Step 2: Define the user ID that owns the package

- Step 3: Define the recovery user ID

- Step 4: Determine DRDA location name for DB2 instance

- Step 5: Configure DB2 Distributed Data Facility for Gateway

DB2/400

- Step 1: Configure the Communications Server

- Step 2: Define the user ID that owns the package

- Step 3: Define the recovery user ID

- Step 4: Determine DRDA location name for DB2/400 instance

DB2/UDB (Universal Database)

- Step 1: Configure the SNA Communications Server

- Step 2: Define the user ID that owns the package

- Step 3: Define the recovery user ID

- Step 4: Determine DRDA location name for DB2/UDB instance

DB2/VM

- Step 1: Configure the Communications Server

- Step 2: Define the user ID that owns the package

- Step 3: Define the recovery user ID

- Step 4: Determine DRDA location name for DB2/VM instance

DB2/OS390

Experience with OS/390 (MVS), OS/390, TSO, VTAM, and DB2 is required to perform the following steps:

Step 1: Configure the Communications Server

If you are using SNA, then configure OS/390 (MVS) VTAM for the SNA connection from the host. Configure DB2 Distributed Data Facility (DDF) for SNA using the Logical Unit (LU) defined. If you are using TCP/IP, then configure the TCP/IP subsystem. Configure DB2's DDF subsystem to use TCP/IP, and assign a primary and recovery port number for the DB2 server.

Step 2: Define the user ID that owns the package

During gateway configuration, you will need to run the Bind Package Stored Procedure to bind the gateway package on the DRDA Server. To properly bind the package, the user ID and password that are used when the procedure is run (either implied as the current Oracle user or explicitly defined in the CREATE DATABASE LINK command) must have proper authority on the DRDA Server to create the package. This same user ID should be used to create and to own the ORACLE2PC (twoEphase commit) table. The user ID that is used to bind or rebind the DRDA package must have one or more of the following privileges on the DRDA Server:

- Package privileges of BIND, COPY, and EXECUTE, for example:

GRANT BIND    ON PACKAGE drda1.* TO userid
GRANT COPY    ON PACKAGE drda1.* TO userid
GRANT EXECUTE ON PACKAGE drda1.* TO PUBLIC

- Collection privilege of CREATE IN, for example:

GRANT CREATE IN ON PACKAGE drda1 TO USER userid

- System privileges of BINDADD and BINDAGENT, for example:

GRANT BINDADD   TO USER userid
GRANT BINDAGENT TO USER userid

- Database privilege of CREATETAB, for example:

GRANT CREATETAB ON DATABASE database TO USER userid

Choose a user ID now that will own the package and the ORACLE2PC table. Ensure that this user ID is defined to both DB2 and OS/390 (MVS).

Step 3: Define the recovery user ID

During gateway configuration, the recovery user ID and password are specified in the gateway initialization file using the DRDA_RECOVERY_USERID and DRDA_RECOVERY_PASSWORD parameters. If a distributed transaction fails, then the recovery process connects to the remote database using the user ID and password that are defined in these parameters. This user ID must have execute privileges on the package and must be defined to the DRDA database. If the user ID is not specified in DRDA_RECOVER_USERID, then the gateway attempts to connect to a user ID of ORARECOV when a distributed transaction is in doubt.

Determine the user ID and password that you will use for recovery.

Step 4: Determine DRDA location name for DB2 instance

The DRDA location name is required as a gateway parameter. To determine the location name, run the SQL query from a DB2 SPUFI session:

SELECT CURRENT SERVER FROM any_table

where any_table is a valid table with one or more rows.

If the value returned by this query is blank or null, then the DRDA location name has not been established. Contact the system administrator to arrange to set a location name for the instance.

Step 5: Configure DB2 Distributed Data Facility for Gateway

DB2 DDF is the component of DB2 that manages all distributed database operations, both DRDA and nonEDRDA.

If your site uses DB2 distributed operations, then DDF is probably operational on the DB2 instance that you plan to access through the gateway. If DDF is not operational, then you must configure it and start it as described in the appropriate DB2 documentation.

Even if DDF is operational on the DB2 instance, it might be necessary to make changes to the DDF Communication Database (CDB) tables to specify the authorization conduct of DRDA sessions from the gateway. This can be done by properly authorized users with a utility such as the DB2 SPUFI utility. If you make changes to CDB tables, then you must stop and restart DDF for the changes to take effect. Refer to Chapter 13, "Security Considerations", for additional CDB tables and security information.

DB2/400

Experience with DB2/400 and AS/400 is required to perform the following steps:

Step 1: Configure the Communications Server

If you are using SNA, then configure AS/400 communications for the SNA connection from the host. Configure DB2/400 for SNA using the LU defined. If you are using TCP/IP, then configure the TCP/IP subsystem, configure DB2/400 to use TCP/IP, and assign a Primary and Recovery port number for the DB2 server.

Step 2: Define the user ID that owns the package

During gateway configuration, you will need to run the Bind Package Stored Procedure to bind the gateway package on the DRDA Server. To properly bind the package, the user ID and password that are used when the procedure is run (either implied as the current Oracle user or explicitly defined in the CREATE DATABASE LINK command) must have proper authority on the DRDA Server to create the package. This same user ID should be used to create and to own the ORACLE2PC (twoEphase commit) table. The user ID that is used to bind or rebind the DRDA package must have the following privileges on the DRDA Server:

- Use authority on the CRTSQLPKG command

- Change authority on the library in which the package will be created

Choose a user ID now that will own the package and the ORACLE2PC table. Ensure that this user ID is defined to DB2/400 and AS/400.

Step 3: Define the recovery user ID

During gateway configuration, the recovery user ID and password are specified in the gateway initialization file using the DRDA_RECOVERY_USERID and DRDA_RECOVERY_PASSWORD parameters. If a distributed transaction fails, then the recovery process connects to the remote database using the user ID and password that are defined in these parameters. This user ID must have execute privileges on the package and must be defined to the DRDA database. If the user ID is not specified in DRDA_RECOVER_USERID, then the gateway attempts to connect to a user ID of ORARECOV when a distributed transaction is in doubt.

Determine the user ID and password that you will use for recovery.

Step 4: Determine DRDA location name for DB2/400 instance

The DRDA location name is required as a gateway parameter. To determine the location name, run the following SQL query from a STRSQL session. If SQL is unavailable on the system, then use the AS/400 command DSPRDBDIRE to identify your "LOCAL" DRDA Server.

SELECT CURRENT SERVER FROM any_table

where any_table is a valid table with one or more rows.

If the value returned by this query is blank or null, then the DRDA location name has not been established. Contact the system administrator to arrange to set a location name for the instance.

DB2/UDB (Universal Database)

Experience with DB2/UDB, configuring the communication subsystem of DB2/UDB, and the host System Administration tools is required to perform the following steps.

Step 1: Configure the SNA Communications Server

If you are using SNA, then configure the communications server for the connection from the host. Configure DB2/UBD for SNA using the LU defined. If you are using TCP/IP, then configure the TCP/IP subsystem. Configure DB2/UDB to use TCP/IP, and assign a primary and recovery port number for the DB2 server.

Step 2: Define the user ID that owns the package

During gateway configuration, you will need to run the Bind Package Stored Procedure to bind the gateway package on the DRDA Server. To properly bind the package, the user ID and password that are used when the procedure is run (either implied as the current Oracle user or explicitly defined in the CREATE DATABASE LINK command) must have proper authority on the DRDA Server to create the package. This same user ID should be used to create and to own the ORACLE2PC (twoEphase commit) table. The user ID that is used to bind or rebind the DRDA package must have one or more of the following privileges on the DRDA Server:

- Package privileges of BIND and EXECUTE, for example:

GRANT BIND    ON PACKAGE drda1.g2drsql TO USER userid
GRANT EXECUTE ON PACKAGE drda1.g2drsql TO PUBLIC

- Schema privileges of CREATEIN, for example:

GRANT CREATEIN ON SCHEMA otgdb2 TO USER userid
GRANT CREATEIN ON SCHEMA drda1 TO USER userid

- Database authorities of CONNECT, BINDADD, and CREATETAB, for example:

GRANT CONNECT   ON DATABASE TO USER userid
GRANT BINDADD   ON DATABASE TO USER userid
GRANT CREATETAB ON DATABASE TO USER userid

Now choose a user ID that will own the package and ORACLE2PC table. Ensure that this user ID is defined to both the DB2 instance ID and the operating system.

Step 3: Define the recovery user ID

During gateway configuration, the recovery user ID and password are specified in the gateway initialization file using the DRDA_RECOVERY_USERID and DRDA_RECOVERY_PASSWORD parameters. If a distributed transaction fails, then the recovery process connects to the remote database using the user ID and password that are defined in these parameters. This user ID must have execute privileges on the package and must be defined to the DRDA database. If the user ID is not specified in DRDA_RECOVER_USERID, then the gateway attempts to connect to a user ID of ORARECOV when a distributed transaction is in doubt.

Determine the user ID and password that you will use for recovery.

Step 4: Determine DRDA location name for DB2/UDB instance

The DRDA location name is required as a gateway parameter. To determine the location name, run the SQL query from a DB2 CLI session:

SELECT CURRENT SERVER FROM any_table

where any_table is a valid table with one or more rows.

If the value returned by this query is blank or null, then the DRDA location name has not been established. Contact your system administrator to arrange to set a location name for the instance.

DB2/VM

Experience with VM, AVS, and DB2/VM is required to perform the following steps:

Step 1: Configure the Communications Server

If you are using SNA, then configure VM VTAM and AVS for the SNA connection from the host. If you are using TCP/IP, then configure the TCP/IP service.

Step 2: Define the user ID that owns the package

During gateway configuration, you will need to run the Bind Package Stored Procedure to bind the gateway package on the DRDA Server. To properly bind the package, the user ID and password that are used when the procedure is run (either implied as the current Oracle user or explicitly defined in the CREATE DATABASE LINK command) must have proper authority on the DRDA Server to create the package. This same user ID should be used to create and to own the ORACLE2PC (twoEphase commit) table. The user ID that is used to bind or rebind the DRDA package must have the following privileges on the DRDA Server:

- Package privileges of BIND, COPY, and EXECUTE

- Collection privilege of CREATE IN

- System privileges of BINDADD and BINDAGENT

Choose a user ID now that will own the package and ORACLE2PC table. Ensure that this user ID is defined to DB2/VM and VM.

Step 3: Define the recovery user ID

During gateway configuration, the recovery user ID and password are specified in the gateway initialization file using the DRDA_RECOVERY_USERID and DRDA_RECOVERY_PASSWORD parameters. If a distributed transaction fails, then the recovery process connects to the remote database using the user ID and password that are defined in these parameters. This user ID must have execute privileges on the package and must be defined to the DRDA database. If the user ID is not specified in DRDA_RECOVER_USERID, then the gateway attempts to connect to a user ID of ORARECOV when a distributed transaction is in doubt.

Determine the user ID and password that you will use for recovery.

Step 4: Determine DRDA location name for DB2/VM instance

The DRDA location name is required as a gateway parameter. To determine the location name, run the SQL query from an iSQL session:

SELECT CURRENT SERVER FROM any_table

where any_table is a valid table with one or more rows.

If the value returned by this query is blank or null, then the DRDA location name has not been established. Contact the system administrator to arrange to set a location name for the instance.

6 Configuring Microsoft SNA Server or Host Integration Server

This chapter describes configuration of the Microsoft SNA Server product on Microsoft Windows for use with the Oracle Transparent Gateway for DRDA. The SNA Server provides the SNA connectivity through the APPC/LU6.2 protocol between the PentiumEbased host and the remote DRDA Server. Microsoft Host Integration Server is the successor product to Microsoft SNA Server, but it retains the same configuration information as SNA Server and the steps for configuring SNA Server, therefore, also apply to Host Integration Server. Read this chapter to learn more about creating server profiles.

This chapter contains the following sections:

- Before You Begin

- Steps for Configuring the Communications Interfaces

- Creating SNA Server Profiles for the Gateway

- Creating SNA Definitions for the Gateway

- Testing the Connection

- Using SNA Session Security Validation

- SNA Conversation Security

Before You Begin

This chapter requires you to enter parameters unique to your system in order to properly configure the SNA Server. Refer to Appendix E for a worksheet listing all the installation parameters that you will need to know before you can complete the configuration process. Ask your network administrator to provide you with these parameters before you begin.

Steps for Configuring the Communications Interfaces

- Step 1: Creating SNA Server Profiles for the Gateway

- Step 2: Creating SNA Definitions for the Gateway

- Step 3: Testing the Connection

Creating SNA Server Profiles for the Gateway

The Oracle Transparent Gateway for DRDA requires a stored set of definitions, called Side Information Profiles, to support connections between the gateway and DRDA Servers. Each profile consists of a profile name and a profile type, a set of fields describing the profile. The fields in a given profile type are generally a mixture of operating parameter values and names of other SNA profiles relevant to the profile. Each functional part of APPC, such as the Mode, Remote Transaction Program name, and Logical Unit (LU), is described by a distinct profile type.

Independent Versus Dependent LUs

Oracle recommends independent LUs for the Oracle Transparent Gateway for DRDA, because they support multiple parallel sessions or conversations. This means the multiple Oracle client applications can be active simultaneously with the same DRDA Server through the independent LU.

Dependent LUs support only a single active session. The CP (SNA Server for Microsoft Windows, in this case) queues additional conversation requests from the gateway server behind an already active conversation. In other words, conversations are singleEthreaded for dependent LUs.

If a dependent LU is correctly defined, then no alterations to the Oracle Transparent Gateway for DRDA configuration are needed, nor should any changes be needed to the DRDA Server.

The operational impact of dependent LUs is that the first client application can start a conversation through the gateway with the DRDA Server. While that session is active (which could be seconds, minutes, or hours, depending on how the client application and transaction are designed), any other client application starting a session with the same DRDA Server appears to stop responding as it waits behind the previous session.

If a production application really uses only one conversation at any one time, then there should be no impact. However, additional concurrent conversations might be required for testing or other application development. Each requires that additional dependent LUs be defined on the remote host, plus additional SNA Server configuration entries which define the additional dependent LUs on the host.

Additional Side Information Profiles should be defined to use the new dependent LUs. New Oracle Transparent Gateway for DRDA instances should be created and configured to use these new Side Information Profiles.

Creating SNA Definitions for the Gateway

SNA Server definitions can be created and modified in two ways:

- Directly with the SNACFG command

- Using menus in SNA Server Manager

Maintenance of SNA definitions is normally done by a user with Administrator authority. This information is intended for the person creating SNA definitions for the gateway. You should have some knowledge of SNA before reading this section.

Sample SNA Server Definitions

The tg4drda\sna\mssna subdirectory contains a sample set of gateway SNA Server definitions created with the SNACFG command. The snacfg.ctl file contains sample definitions for SNA Server.

Before building the SNA Server definitions, examine the snacfg.ctl file to determine the definitions needed, their contents, and their interrelationships. The file format is textEoriented and each field of each definition is clearly labeled. You can print a copy of the file to use while working with your definitions in an SNA Server Admin or SNA Server Manager session.

You can create and modify these definitions in two ways:

- Install the definitions directly on the system using the SNACFG command.
For information on using the SNACFG command, refer to the SNA Server Administration Guide in the Microsoft SNA Server online documentation.

If you use this method, then you must use SNA Server Manager to review and modify the installed definitions. Because of configuration and naming differences, it is unlikely that they will work without modification.

- Create the definitions.
SNA Server Manager is the recommended method for creating the definitions. You should be able to accept most of the defaults. The default values assigned to many of the fields in a new set of definitions are acceptable for the gateway.

Definition Types

There are several types of SNA Server definitions relevant to gateway APPC/LU6.2 operation. Each definition can be created and edited using a corresponding SNA Server Manager menu.

The definitions relevant to the gateway are presented here in hierarchical order. Those definition types that are lowest in the hierarchy are discussed first. This matches the logical sequence in which to create the profiles.

Refer to the Microsoft SNA Server online documentation for a complete discussion of SNA Server definitions. This section is an overview of SNA Server definitions in relation to the Oracle Transparent Gateway for DRDA for Microsoft Windows.

Note:
Before beginning to create and edit profiles using SNA Server Admin, you must install the DLC protocol and create the link service. Prior to running SNA Server Admin, use the Microsoft Windows Control Panels Network Manager to install the DLC protocol.

SNA Server Definitions

This section describes the process of creating your SNA definitions for SNA Server version 3, using SNA Server Manager. All the tasks described in this section are performed from within SNA Server Manager. The other primary administration tool is the SNA Server Management Console. Both tools provide access to the same SNA definitions for the Node, but in slightly different views. The SNA Server Manager gives a localized view of the Node, while the SNA Server Management Console presents a more global view, where the local node may be one of many SNA Nodes in a network that is managed by this syatem. Later versions of SNA Server and Host Integration Server tools may reorganize the profiles placement within the definition tree, but the concepts remain the same. Some extrapolation by the user may be necessary.

Figure 6-1 SNA Server Manager Main Screen: Select a Server

Server Selection

The correct SNA Server must be selected to ensure that definitions created are for that server. Start the SNA Server Manager.

Click the SNA subdomain under your local system (in this example, ITDEV11) and then click to open the SNA Servers folder. From a list of services for that server, select the SNA Service of your choice (in this illustration, ITDEVENT11). Click to open it.

Figure 6-2 Server Properties Dialog Box

Service Properties

Each SNA Server must have a primary service definition. From the Service menu in the SNA Server Manager window, select Properties. In the Server Properties dialog box, under the General tab, change the Network Name and Control Point Name as needed. Click OK.

Figure 6-3 Insert Link Service

Link Service Definition

A link service must be installed and configured in order for SNA Server to use the network adapter installed in your workstation. From the Insert menu, select Link Service. In the Insert Link Service dialog box, select the desired Link Service from the selection list and click Add. In this example, DLC 802.2 Link Service is selected.

Figure 6-4 Select Link Service Properties

Now, the Link Service Properties dialog box is displayed. Note that the contents of this dialog box will vary, depending on which Link Service was selected. In this example, the DLC 802.2 Link Service Properties box dialog is used:

Select the suitable network adapter from the Adapter drop-down list and click OK. In the Insert Link Service dialog box, click OK. The system now updates the network bindings.

Figure 6-5 Connection Properties Menu

Connection Definition

You must create a connection definition to define the devices which SNA Server uses to perform SNA communication. From the Insert menu, select Connection and choose the connection type (802.2 is used in this example). The Connection Properties dialog box appears.

Figure 6-6 General Connection Properties

Select the General tab. Enter a Connection Name. This is the name used by SNA Server to name the connection. This example names the connection HQMVS2. From the Link Service drop-down list, select a link service for the connection. All other settings can be left set to their default values.

Figure 6-7 Enter Remote Addresses

Select the Address tab. Enter values for Remote Network Address and the Remote SAP address.

Figure 6-8 Enter System Identification

Now, select the System Identification tab. Under Local Node Name, enter the Network Name, Control Point Name, and Local Node ID. Under Remote Node Name, enter the Network Name, Control Point Name, and optionally, the Remote Node ID. The XID Type should be set to Format 3.

Figure 6-9 Enter DLC Values

Next, select the DLC tab. In this example, the 802.2 DLC (Token Ring) is being used. For the 802.2 DLC, all of the defaults are usually acceptable. If you need to change any values, then do so now. Now, all the connection properties are set. Click OK.

Figure 6-10 Local LU Properties Menu

Local LU Definition

You must create a local LU definition. The local LU definition describes the SNA LU through which the gateway communicates with DRDA Server systems.

From the Insert menu, select APPC Local LU. The Local APPC LU Properties dialog box appears.

Figure 6-11 Enter Local APPC LU Properties

Select the General tab. Enter LU Alias, Network Name, and LU Name. You should contact the person responsible for your SNA network to determine the correct LU and network names.

Figure 6-12 Set Up Parallel Session

Select the Advanced tab. Check the Member of Default Outgoing Local APPC LU Pool box. Set the LU 6.2 Type to Independent to enable parallel sessions. Ensure that the APPC Syncpoint Support box is not checked.

Now, the Local LU properties are all set. Click OK button to continue.

Figure 6-13 Select APPC Mode Definition

Mode Definition

This definition describes an SNA mode entry to be used when establishing sessions between LUs. The mode defined here must match a mode defined on the target system.

From the Insert menu, select APPC Mode Definition. The APPC Mode Properties dialog box appears.

Figure 6-14 APPC Mode General Properties Dialog Box

Select the General tab. Enter the Mode Name. The mode name that you specify must be defined to the DRDA Server communications software. Choose the mode name and other mode parameters after consulting the person responsible for configuring the DRDA Server communications software.

Figure 6-15 Enter the APPC Mode Limits

Next, select the Limits tab. Enter values for Parallel Session Limit, Minimum Contention Winner Limit, Partner Min Contention Winner Limit, and Automatic Activation Limit. The Parallel Session limit determines the maximum number of concurrent conversations permitted between the gateway instance and the DRDA Server. This equates to the maximum number of concurrently active remote sessions through the gateway instance.

Figure 6-16 Set APPC Mode Characteristics

Now, select the Characteristics tab. Enter the Pacing Send Count, Pacing Receive Count, Max Send RU Size, and Max Receive RU size. For optimal performance, check the High Priority Mode box. The pacing and RU size parameters are performanceErelated and should be tuned to suit your application. For most installations, the values set in the example will be sufficient.

Now, all the APPC mode properties are set. Click OK to continue.

Figure 6-17 APPC Remote LU Menu

Remote LU Definition

This definition describes the SNA LU of the DRDA Server system with which the gateway communicates. You must create a remote LU definition for the remote DRDA Server system. From the Insert menu, select APPC Remote LU. The Remote APPC LU Properties dialog box appears.

Figure 6-18 Enter General Remote APPC LU Properties

Select the General tab. Determine the link with which to associate the LU (in the example, HQMVS2). Use the Connection drop-down list to select the connection used to access this LU. Enter the LU Alias, Network Name, LU Name, and Uninterpreted LU Name. You should contact the person responsible for your SNA network to determine the correct LU and network names. Note that you can use the LU Alias to define a name known only to SNA Server, and that name can remain the same even if the remote LU name changes. This helps to reduce the amount of maintenance required when network changes occur.

Figure 6-19 Remote APPC LU Properties Options

Now, select the Options tab. Check the Supports Parallel Sessions check box. Use the Implicit Incoming Mode drop-down listto select the mode. Set any security options you need.

The remote APPC LU properties are now set. Click OK to continue.

Figure 6-20 CPIEC Symbolic Destination Name Window

CPIEC Symbolic Destination Names

Once the Local and Remote Partner definitions and Mode definitions have been created, you can create CPIEC Symbolic Destination Names, also called Side Information Profiles. The Side Information Profiles are used to identify target DRDA Server systems to be accessed through the gateway. From the Insert menu, select APPC CPIEC Symbolic Name. The CPIEC Name Properties dialog box appears.

Figure 6-21 Enter General CPIEC Name Properties

Select the General tab. Enter a Name for Side Information. From the Mode Name drop-down list, select the correct mode.

Note:
The DRDA_CONNECT_PARM should be assigned the name of the CPIEC Side Information Name entered earlier.

Figure 6-22 Enter CPIEC Name Properties Partner Information

Now, select the Partner Information tab. Select Application TP and enter the TP name. Enter the Partner LU Name alias. Click OK to save the Side Information.

Testing the Connection

Before proceeding with the gateway configuration tasks in Chapter 10, "Configuring the Gateway", ensure that your connection is working. This can be done using SNA Server Manager.

Figure 6-23, "Relationship Between SNA Server Definitions and Host VTAM Definitions" shows the relationship between SNA Server definitions and the VTAM definitions on the host.

Figure 6-23 Relationship Between SNA Server Definitions and Host VTAM Definitions

Using SNA Session Security Validation

When the database link request for the gateway begins, the gateway attempts to start an APPC conversation with the DRDA Server. Before the conversation can begin, a session must start between the host Logical Unit (LU) and the DRDA Server LU.

SNA and its various access method implementations (including Microsoft SNA Server) provide security validation at session initiation time, enabling each LU to authenticate its partner. This is carried out entirely by network software before the gateway and server application programs begin their conversation and process conversationElevel security data. If sessionElevel security is used, then correct password information must be established in the Pentium-based host Connection Profile and in similar parameter structures in the DRDA Server system that is to be accessed. Refer to Microsoft SNA Server and IBM Communication Server product documentation for detailed information.

SNA Conversation Security

SNA conversation security is determined by the setting of the gateway initialization parameter, DRDA_SECURITY_TYPE. This parameter determines whether SNA security option SECURITY is set to PROGRAM or to SAME. Generally, the gateway operates under SNA option SECURITY=PROGRAM, but it can also be set to operate under SNA option SECURITY=SAME.

SNA Security Option SECURITY=PROGRAM

If DRDA_SECURITY_TYPE=PROGRAM is specified, then the gateway allocates the conversation with SNA option SECURITY=PROGRAM and sends this information to the DRDA Server:

- If the database link has explicit CONNECT information, then the specified user ID and password are sent.

- If the database link has no CONNECT clause and if the application has logged in to the Oracle integrating server with an explicit user ID and password, then the Oracle user ID and password are sent.

- If the application logs in to the Oracle integrating server with operating system authentication, and if the database link lacks explicit CONNECT information, then no user ID and password are sent. If no user ID and password are sent, and if the DRDA Server is not configured to assign a default user ID, then the connection fails.

In general, SECURITY=PROGRAM tells the DRDA Server to authenticate the user ID/password combination using whatever authentication mechanisms are available. For example, if DB2/OS390 is the DRDA Server, then RACF can be used. This is not always the case, however, because each of the IBM DRDA Servers can be configured to process inbound user IDs in other ways.

SNA Security Option SECURITY=SAME

The SECURITY=SAME option is not directly supported by Microsoft SNA Server. SECURITY=SAME implicitly validates security using the user account under which the TNS Listener was started. Microsoft SNA Server, however, does not support this type of validation.

7 Configuring IBM Communication Server

This chapter describes configuration of the IBM Communication Server product on MS Windows for use with the Oracle Transparent Gateway for DRDA. IBM Communication Server provides SNA connectivity through the APPC/LU6.2 protocol between the host and the remote DRDA Server. Read this chapter to learn more about creating Communication Server profiles.

This chapter contains the following sections:

- Before You Begin

- Checklist for Configuring the Communications Interfaces

- Creating IBM Communication Server Profiles for the Gateway

- Definition Types

- Testing the Connection

- Using SNA Session Security Validation

- SNA Conversation Security

Before You Begin

This chapter requires you to enterparameters unique to your system in order to properly configure the IBM Communication Server. Refer to Appendix E for a worksheet listing all the installation parameters that you will need to know before you can complete the configuration process. Ask your network administrator to provide you with these parameters before you begin.

Checklist for Configuring the Communications Interfaces

- Step 1: Creating IBM Communication Server Profiles for the Gateway

- Step 2: Definition Types

- Step 3: Testing the Connection

Creating IBM Communication Server Profiles for the Gateway

The Oracle Transparent Gateway for DRDA requires a stored set of definitions, called Side Information Profiles, to support connections between the gateway and DRDA Servers. Each profile consists of a profile name and a profile type, a set of fields describing the profile. The fields in a given profile type are generally a mixture of operating parameter values and names of other SNA profiles relevant to the profile. Each functional part of APPC, such as the Mode, Remote Transaction Program (RTP) name, and Logical Unit (LU), is described by a distinct profile type.

Independent Versus Dependent LUs

Oracle recommends independent LUs for the Oracle Transparent Gateway for DRDA, because they support multiple parallel sessions or conversations. This means multiple Oracle client applications can be active simultaneously with the same DRDA Server through the independent LU.

Dependent LUs support only one active session. The CP (IBM Communication Server, in this case) queues additional conversation requests from the gateway server behind an already active conversation. In other words, conversations are singleEthreaded for dependent LUs.

If a dependent LU is correctly defined, then no alterations to the Oracle Transparent Gateway for DRDA configuration are needed, nor should any changes be needed to the DRDA Server.

The operational impact of dependent LUs is that the first client application can start a conversation through the gateway with the DRDA Server. While that session is active (which could be seconds, minutes, or hours, depending on how the client application and transaction are designed), any other client application starting a session with the same DRDA Server appears to stop responding as it waits behind the previous session.

If a production application really uses only one conversation at any one time, then there should be no impact. However, additional concurrent conversations might be required for testing or other application development. Each requires that additional dependent LUs be defined on the remote host, plus additional IBM Communication Server configuration entries which define the additional dependent LUs on the host.

Additional Side Information Profiles should be defined to use the new dependent LUs. New Transparent Gateway for DRDA instances should be created and configured to use these new Side Information Profiles.

Creating SNA Definitions for the Gateway

IBM Communication Server definitions are created using the SNA Node Configuration tool, while the actual operation of the server is done using the SNA Node Operations tool, both of which are provided with IBM Communication Server. Maintenance of SNA definitions is normally done by a user with Administrator authority.

Sample IBM Communication Server Definitions

The tg4drda\sna\commsvr subdirectory contains a sample set of IBM Communication Server definitions created with the SNA Node Configuration tool. The oracle.acg file contains sample definitions for IBM Communication Server.

Before building the IBM Communication Server definitions, examine the oracle.acg file to determine the definitions needed, their contents, and their interrelationships. The file format is textEoriented and each field of each definition is clearly labeled. You can print a copy of the file to use while working with your definitions in an SNA Node Configuration session.

Definition Types

There are several types of IBM Communication Server definitions relevant to gateway APPC/LU6.2 operation. Each definition can be created and edited using a corresponding SNA Node Configuration menu.

The definitions relevant to the gateway are presented here in hierarchical order. Those definition types that are lowest in the hierarchy are discussed first. This matches the logical sequence in which to create the profiles.

Refer to the IBM Communication Server online documentation for a complete discussion of IBM Communication Server definitions. This section is an overview of IBM Communication Server definitions in relation to the Oracle Transparent Gateway for DRDA.

IBM Communication Server Definitions

This section describes the process of creating SNA definitions for IBM Communication Server using the SNA Node Configuration tool. All the tasks described in this section are performed within SNA Node Configuration.

Figure 7-1 Choosing a Configuration Scenario

Creating the Configuration

SNA Node Configuration will first ask if you are creating a new configuration or loading an existing configuration. The following example is presented with the assumption that a new configuration is being created.

SNA Node Configuration will next prompt you for a configuration scenario. Our example is made assuming that a CPIEC or APPC scenario is being chosen.

Figure 7-2 Creating the Node Configuration

Defining the Node

Each SNA Server must have a Control Point defined. This is typically called the Node definition. Click Node and click Create.

Figure 7-3 Node Definition

In the Define the Node dialog box, in the Basic tab, enter the Control Point, Local Node ID, and Node Type information. You can also select option in the Advanced tab depending on your SNA network configuration. Click OK.

Figure 7-4 Creating Devices

Communication devices should be configured next. Select Devices, and click Create.

Figure 7-5 Choosing the Device Type

Select the type of device to use for communication. The LAN type is typical for either Ethernet or TokenEring attached network devices.

Figure 7-6 Configuring a LAN Device

In the Basic tab, select the adapter to use and the local SAP. The other tabs may be explored for network tuning parameters. Click OK.

Figure 7-7 Creating Peer Connections

Peer connections should be configured next. Select Peer Connections, and click Create.

Figure 7-8 Defining the Link station

In the Basic tab, enter a link station name for this connection. Choose the Device for the connection, and enter the destination address and remote SAP.

Figure 7-9 Defining the Adjacent Node

Select the Adjacent Node tab. Enter the Adjacent CP name of the remote system and pick its CP Type. You may have to choose a different Transmission Group (TG) as the default. Consult your SNA Network Administrator for details. The other tabs may be explored for tuning and link reactivation options. Click OK.

Figure 7-10 Create Local LUs

Next, define the local LUs for this Node. Select Local LU 6.2 LUs, and click Create.

Figure 7-11 Defining Local LUs

In the Basic tab, enter the name of the local LU and an alias, if desired. The name must match the Local LU definition of the remote host for this node. The Advancedtab may be explored for Synchronization support and for LU session limits. Click OK.

Figure 7-12 Create Partner LUs

Next, define remote Partner LUs for this Node to connect to. Select Partner LU 6.2 LUs and click Create.

Figure 7-13 Defining Partner LUs

In the Basic tab, enter the name of the remote or partner LU and an alias, if desired. Seclect Fully Qualified CP from the existing list. The Advanced tab may be explored for logical record limits and security support. Click OK.

Figure 7-14 Creating the IBMRDB Mode

Next, define the IBMRDB mode, which will be used for DRDA connections. Select Modes and click Create.

Figure 7-15 Define the IBMRDB Mode

In the Basic tab, enter the name IBMRDB and the mode session limits. Consult your SNA Network Administrator for details. The Advanced tab may be explored for pacing and autoactivation session options. Click OK.

Figure 7-16 Create the CPIEC Side Information Profile

Next, define the CPIEC profile that will be use dby the gateway. Select CPIEC side information definitions and click Create.

Figure 7-17 Define the CPIEC Side Information Profile

In the Basic tab, enter the Symbolic Destination name. Select IBMRDB for the Mode name drop-down list, and select the Partner LU either by name or by alias. Enter the TP name for the remote DRDA Server. Mode DRDA Servers use the default Service TP name X'07F6C4C2' or '076DB'. Consult your DRDA Server Administrator for the correct TP name. The Advancedtab may be explored for security options.

Note:
The DRDA_CONNECT_PARM should be assigned the name of the Symbolic Destination name as entered in Figure 7-16, "Create the CPIEC Side Information Profile".

Testing the Connection

Before proceeding with the gateway configuration tasks in Chapter 10, "Configuring the Gateway", ensure that your connection is working. This can be done by using the SNA Node Operations tool.

Figure 7-18, "Relationship Between IBM Communication Server Definitions and Host VTAM Definitions" shows the relationship between IBM Communication Server definitions and the VTAM definitions on the host.

Figure 7-18 Relationship Between IBM Communication Server Definitions and Host VTAM Definitions

Using SNA Session Security Validation

When the database link request for the gateway begins, the gateway attempts to start an APPC conversation with the DRDA Server. Before the conversation can begin, a session must start between the host LU and the DRDA Server LU.

SNA and its various access method implementations (including IBM Communication Server) provide security validation at session initiation time, enabling each LU to authenticate its partner. This is carried out entirely by network software before the gateway and server application programs begin their conversation and process conversationElevel security data. If sessionElevel security is used, then correct password information must be established in the Pentium-based host Connection Profile and in similar parameter structures in the DRDA Server system that is to be accessed. Refer to Microsoft SNA Server and IBM Communication Server product documentation for detailed information.

SNA Conversation Security

SNA conversation security is determined by the setting of the gateway initialization parameter, DRDA_SECURITY_TYPE. This parameter determines whether SNA security option SECURITY is set to PROGRAM or to SAME. Generally, the gateway operates under SNA option SECURITY=PROGRAM, but it can also be set to operate under SNA option SECURITY=SAME.

SNA Security Option SECURITY=PROGRAM

If DRDA_SECURITY_TYPE=PROGRAM is specified, then the gateway allocates the conversation with SNA option SECURITY=PROGRAM and sends this information to the DRDA Server:

- If the database link has explicit CONNECT information, then the specified user ID and password are sent.

- If the database link has no CONNECT clause and if the application has logged in to the Oracle integrating server with an explicit user ID and password, then the Oracle user ID and password are sent.

- If the application logs in to the Oracle integrating server with operating system authentication and if the database link lacks explicit CONNECT information, then no user ID and password are sent. If no user ID and password are sent and if the DRDA Server is not configured to assign a default user ID, then the connection fails.

In general, SECURITY=PROGRAM tells the DRDA Server to authenticate the user ID/password combination using whatever authentication mechanisms are available. For example, if DB2/OS390 is the DRDA Server, then RACF can be used. This is not always the case, however, because each of the IBM DRDA Servers can be configured to process inbound user IDs in other ways.

SNA Security Option SECURITY=SAME

The SECURITY=SAME option is not directly supported by IBM Communication Server. SECURITY=SAME implicitly validates security by using the user account under which the TNS listener was started. IBM Communication Server, however, does not support this type of validation.

8 Configuring TCP/IP

This chapter describes configuring TCP/IP for the Microsoft Windows platforms that are supported by the Oracle Transparent Gateway for DRDA. TCP/IP is a communications facility that is already part of the operating system. No thirdEparty protocol software is required. Read this chapter to learn more about configuring TCP/IP.

This chapter contains the following sections:

- Before You Begin

- Configuring TCP/IP

Before You Begin

This chapter requires you to enter parameters that are unique to your system in order to properly configure TCP/IP. Refer to Appendix E for a worksheet listing all of the installation parameters that you will need to know about before you complete the configuration process. Ask your network administrator to provide you with these parameters before you begin.

Port Number

The DRDA standard specifies that port 446 be used for DRDA services. However, if several DRDA Servers are operating on the same system, then they will need to provide service on different ports. Therefore, the port number that is used by each DRDA Server will need to be extracted from the configuration of each individual DRDA Server. DB2 for OS/390 and DB2/400 typically use the DRDA standard port number, 446, whereas DB2/UDB typically uses 50000 as the port number. Refer to IBM DB2 Administrator and Installation guides for locating and changing these port numbers for the DRDA Server. For additional information, consult your DB2 DBA or system administrator.

Configuring TCP/IP

The following configuration example is for Microsoft Windows NT 4.0. Other Microsoft Windows operating systems may have these panels in a different location or may present them differently, but the required contents will be essentially the same.

You configure TCP/IP from the network configuration tool in the Microsoft Windows Control Panel.

Select the Protocol tab and select TCP/IP Protocol. Then, click Properties to display the Properties panel.

Figure 8-1 Network Configuration Tool

If the TCP/IP Protocol is not already installed, then click Add and then select the TCP/IP Protocol.

Configuration consists of assigning a host name, an IP address, and a network mask to a given network interface.

In the IP Address tab, use the drop-down list to select the adapter you will use. Your network administrator can tell you whether you will be using DHCP or a static IP address. If using a static IP, then you must enter the correct values for IP address, subnet mask, and default gateway.

Figure 8-2 TCP/IP Properties Panel

Additional configuration consists of defining a name server IP address or creating entries in the hosts file on the local system. Name server translate host names into IP Addresses when queried on a particular host name. The hosts file provides this same functionality, but in a nonEnetwork participating manner.

The Hosts file may be edited with a text editor of your choice. For example, in Microsoft Windows NT, the file is located in:

C:\winnt\system32\drivers\etc\hosts

where C:\winnt is the Windows NT system root.

To use a name server, you must configure the TCP/IP to use DNS. Select the DNS tab and enter a host name and domain name. Your network administrator will provide these values. Click Add below the Domain Suffix Search Order box and enter the IP Address of the name server. You may enter up to three name servers. Click OK.

Figure 8-3 Define a Name Server

For local configuration (in other words, the gateway and the DRDA Server are on the same system), it may be desirable to use the loopEback address. The IP address is 127.0.0.1 and is typically given the local name ("localhost" or "loopback") in the Hosts file. Using the loopEback address reduces the amount of network overhead by handling the traffic internally without actually talking to the network.

The gateway is configured for TCP/IP using the DRDA_CONNECT_PARM initialization file parameter. In an SNA configuration, this parameter would be set to the Side Information Profile name (name set in Figure 6-21 or Figure 7-17). In a TCP/IP configuration, this parameter should be set to the IP address or Host name of the DRDA Server, which should be followed by the Service Port number of that server. For more information about the port number, refer to "Port Number".

Note:
When installing the gateway, you must choose either SNA or TCP/IP for the networking interface. The DRDA_CONNECT_PARM must be configured correctly for the chosen networking interface.

The rest of the DRDAEspecific parameters are unrelated to the communications protocol and may be set the same for either SNA or TCP/IP installations.

Example #1: Configuration for a DRDA Server on a host named 'mvs01.domain.com' (or IP address of 192.168.1.2) with a Service Port number of 446.

DRDA_CONNECT_PARM=mvs01.domain.com:446

or

DRDA_CONNECT_PARM=192.168.1.2:446

Example #2: Configuration for a DRDA Server on the same host as the gateway with a Service Port number of 446.

DRDA_CONNECT_PARM=localhost:446

or

DRDA_CONNECT_PARM=127.0.0.1:446

For additional information on configuring TCP/IP, refer to the Microsoft Windows installation and configuration guides.

9 Oracle Net

Oracle Net is an Oracle product providing network communication between Oracle applications, Oracle Servers, and Oracle Gateways across different systems.

This chapter contains the following sections:

- Checklists for Oracle Net

- Oracle Net and SQL*Net Introduction

- Oracle Net Overview

- Configuring Oracle Net

- Advanced Security Encryption

- Setting Up Advanced Security Encryption for Test

- Testing Advanced Security Encryptions

Checklists for Oracle Net

Use the following checklists when you are installing and configuring Oracle Net.

Configuring Oracle Net

- Step 1: Modify the listener.ora file

- Step 2: Modify the tnsnames.ora file

Advanced Security Encryption

Use the following checklists for encryption.

Setting Up Advanced Security Encryption for Test

- Step 1: Set Advanced Security Encryption Parameters for the Gateway

- Step 2: Set Advanced Security Encryption Parameters

Testing Advanced Security Encryptions

- Step 1: Connect the Gateway and Oracle the Integrating Server

- Step 2: Reset Configuration Parameters on the Gateway

Oracle Net and SQL*Net Introduction

Oracle Net provides connectivity to the Gateway through the use of Protocol Adapters, SQL*Net, and the TNS Listener. Configuration of Oracle Net is backward compatible with past versions of SQL*Net. A new facility called Heterogeneous Services (HS) has been added to both Oracle Net and the Gateway to improve the throughput of SQL*Net data. For additional information, refer to Oracle Database Net Services Administrator's Guide and Oracle Database Heterogeneous Connectivity Administrator's Guide.

Oracle Net Overview

Oracle Net is a required Oracle product supporting network communications between Oracle applications, Oracle servers, and Oracle gateways across different CPUs or operating systems. It also supports communication across different Oracle databases and CPUs providing distributed database and distributed processing capabilities.

Oracle Net also enables applications to connect to multiple Oracle servers or gateways across a network, selecting from a variety of communications protocols and application program interfaces (APIs) to establish a distributed processing and distributed database environment.

A communications protocol is a set of implemented standards or rules governing data transmission across a network. An API is a set of subroutines providing an interface for application processes to the network environment.

Distributed Processing

Dividing processing between a frontEend computer running an application and a backEend computer used by the application is known as distributed processing. Oracle Net enables an Oracle tool or application to connect to a remote computer containing an Oracle server or Oracle gateway.

Distributed Database

Several databases linked through a network, appearing as a single logical database, are known as a distributed database. An Oracle tool running on a client computer or on an Oracle server running on a host computer can share and obtain information retrieved from other remote Oracle servers. Regardless of the number of database information sources, you might be aware of only one logical database.

Terminology for Oracle Net

The following terms are used to explain the architecture of Oracle Net for Microsoft Windows:

host is the computer the database resides on and that runs the Oracle server or gateway.

client (task) is the application using an Oracle Net driver to communicate with the Oracle server or gateway.

protocol is a set of standards or rules governing the operation of a communication link.

driver is the part of Oracle Net supporting a given network protocol or communication method.

network is a configuration of devices and software connected for information interchange.

Configuring Oracle Net

The gateway must be defined to the TNS listener, and a service name must be defined for accessing the gateway.

Step 1: Modify the listener.ora file

Add an entry for the gateway to the listener.ora file. For example:

(SID_DESC=
(SID_NAME=sidname)
(ORACLE_HOME=C:\oracle\GTWHome)
(PROGRAM=g4drsrv))

Refer to Appendix B, "Sample Files", for a sample listener.ora file.

Note:
The PROGRAM=g4drsrv parameter is required. It specifies to the listener the name of the gateway executable.

Step 2: Modify the tnsnames.ora file

Add a gateway service name to the tnsnames.ora file on the system where your Oracle integrating server resides. Specify the service name in the USING parameter of the database link defined for accessing the gateway from the Oracle Database 10g server.

You can use the IPC protocol only if the Oracle integrating server and the gateway reside on the same system. If you use the IPC protocol adapter, then add an entry like this to tnsnames.ora:

linkname1 = (DESCRIPTION=
(ADDRESS=
(PROTOCOL=IPC)
(KEY=ORAIPC))
(CONNECT_DATA=(SID=sidname))
(HS=)
)

where:

linkname1  is the name used to define the database link referencing the gateway.

ORAIPC  is the IPC key defined in the listener.ora file for the IPC protocol

sidname  is the gateway SID, the same SID that you used for the entry in the listener.ora file.

If you are using the TCP/IP protocol adapter, then add this entry to tnsnames.ora:

linkname2 = (DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(PORT=port)
(HOST=hostname))
(CONNECT_DATA=(SID=sidname))
(HS=)
)

where:

linkname2  is the name used to define the database link referencing the gateway

port  is the default Oracle TCP/IP port number (1541)

hostname  is the name of your host system

sidname  is the gateway SID

Refer to "Sample Oracle Net tnsnames.ora File" for a sample tnsnames.ora file. For more information about configuring Oracle Net, refer to the Oracle Database Net Services Reference and Oracle Database Net Services Administrator's Guide.

Advanced Security Encryption

Oracle Net supports the CHECKSUM command and the Export encryption algorithms. The following sections describe a basic method of verifying this feature if it is used at your site. The easiest way to determine if Advanced Security encryption is attempting to work is to deliberately set wrong configuration parameters and attempt a connection between the server and client. Incorrect parameters cause the connection to fail.

After receiving the expected failure message, set the configuration parameters to the correct settings and try the connection again. Encryption is working properly if you receive no further error messages.

Setting Up Advanced Security Encryption for Test

The following procedures test Advance Security encryption by the method explained earlier. The incorrect parameter settings produce error 12660

1. Set Advanced Security encryption parameters for the gateway

2. Set Advanced Security encryption parameters for the Oracle integrating server

Note:
The international or export version of Advanced Security encryption supports the following encryption types:

- des40

- rc4_40

Step 1: Set Advanced Security Encryption Parameters for the Gateway

Edit the Oracle Net configuration file on the Microsoft Windows system (gateway system) to add the following parameters and values:

SQLNET.CRYPTO_CHECKSUM_SERVER = REJECTED
SQLNET.ENCRYPTION_SERVER = REJECTED
SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER = (SHA1)
SQLNET.ENCRYPTION_TYPES_SERVER = (DES40,RC4_40)
SQLNET.CRYPTO_SEED = "abcdefg123456789"

The value shown for SQLNET.CRYPTO_SEED is only an example. Set it to the value you want. Refer to the Oracle Database Advanced Security Administrator's Guide for more information.

Step 2: Set Advanced Security Encryption Parameters

Set Advanced Security Encryption parameters for the Oracle integrating server. Edit the Oracle Net configuration file on the Oracle integrating server system to add the following parameters:

SQLNET.CRYPTO_CHECKSUM_CLIENT = REQUIRED
SQLNET.ENCRYPTION_CLIENT = REQUIRED
SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT = (SHA1)
SQLNET.ENCRYPTION_TYPES_CLIENT = (DES40,RC4_40)
SQLNET.CRYPTO_SEED = "abcdefg123456789"

The value shown for SQLNET.CRYPTO_SEED is only an example.

Testing Advanced Security Encryptions

After completing Steps 1 and 2 to set up Advanced Security encryption, you are ready to test the operation of the Advanced Security encryption by using the following steps:

1. Connect the gateway and the Oracle integrating server.

2. Reset configuration parameters on the gateway.

Step 1: Connect the Gateway and Oracle the Integrating Server

Use SQL*Plus to log on to the Oracle integrating server. Access the gateway through a database link. You should receive the following error:

ORA-12660: Encryption or crypto-checksumming

Step 2: Reset Configuration Parameters on the Gateway

Change the following Advanced Security encryption parameters on the gateway to:

SQLNET.CRYPTO_CHECKSUM_SERVER = REQUIRED
SQLNET.ENCRYPTION_SERVER = REQUIRED

Attempt the connection between the gateway and the Oracle integrating server again. If no error message is returned and the connection completes, then you can assume that Advanced Security encryption is working properly.

10 Configuring the Gateway

After you have installed the gateway, configured your DRDA Server, and configured your SNA or TCP/IP software, you must configure the gateway.

This chapter contains the following sections:

- Configuration Checklist

- Choosing a Gateway System Identifier (SID)

- Gateway Configuration

- Configuring the Host

- DRDA Gateway Package Considerations

- Backup and Recovery of Gateway Configuration

- Configuring the Oracle Integrating Server

- Accessing the Gateway from Other Oracle Servers

- Accessing Other DRDA Servers

- Gateway Installation and Configuration Complete

Configuration Checklist

Choosing a Gateway System Identifier (SID)

- Enter the SID on the Worksheet

Configuring the Host

- Step 1: Copy the gateway initialization

- Step 2: Determine settings for gateway initialization parameters

- Step 3: Tailor the initsid.ora File

Binding the DRDA Gateway Package

- Step 1: Log on to an Oracle integrating server

- Step 2: Create a database link

- Step 3: Run the stored procedure GTW$_BIND_PKG

Binding Packages on DB2/Universal Database (DB2/UDB)

- Step 1: Log in to the system where DB2/UDB is running.

- Step 2: Copy the following files.

- Step 3: Connect to the database.

- Step 4: Create the ORACLE2PC table:

- Step 5: Commit the transaction:

- Step 6: Optionally, verify that the table was created under the correct user ID:

- Step 7: Disconnect from the session:

Before Binding the DRDA Gateway Package

- Step 1: Check all DRDA parameter settings

- Step 2: If using DB2/UDB, then create ORACLE2PC table

Sample SQL scripts

- Step 1:  Run Data Dictionary scripts

- Step 1a:  Upgrading from a previous gateway version

- Step 1b: Creating the Data Dictionary tables and views

- Step 2: DB2/UDB or other server

- Step 2a: If server is DB2/UDB, then grant authority to package

- Step 2b: If server is not DB2/UDB, then create the ORACLE2PC table

Configuring the Oracle Integrating Server

- Step 1: Create a database link

- Step 2: Create synonyms and views

Accessing the Gateway from Other Oracle Servers

- Step 1. Create a database link with which to access the gateway.

- Step 2. Define synonyms and views for tables.

- Step 3. Perform GRANT statements.

Accessing Other DRDA Servers

- Step 1: Configure another APPC profile set for the DRDA Server.

- Step 2: Configure additional DRDA Server instances.

- Step 3: Bind the DRDA package to the DRDA Server.

Choosing a Gateway System Identifier (SID)

The gateway SID is a string of alphabetic and numeric characters that identifies a gateway instance. The SID is used in the file names of gateway parameter files and in the connection information that is associated with the Oracle server database links that access the gateway.

Enter the SID on the Worksheet

Enter the SID in Appendix E, "Configuration Worksheet".

A separate SID is required for each DRDA Server to be accessed. You might also have multiple SIDs for one DRDA Server to use different gateway parameter settings with that server. For information on configuring additional SIDs, refer to "Accessing Other DRDA Servers".

Gateway Configuration

The information in this chapter describes the configuration process for the gateway. All gateway parameters are kept in the initsid.ora gateway initialization file, which is stored in the gateway admin/ directory.

Configuring the Host

The data in this chapter describes the configuration process for the gateway. You should notice that most, if not all, gateway parameters have been moved into the initsid.ora initialization file. To configure the host for the Oracle Transparent Gateway for IBM DRDA, you tailor the parameter files for your installation.

To start with one of the provided sample configuration files, proceed to Step 1 below. To create entirely new configuration files, proceed to Step 2.

Note:
In previous versions of the gateway, the initialization parameters were stored in the files named initsid.ora and initsid.gtwboot in the gateway instance directories. With Release 10.1.0.2.0 of the gateway, most parameters that were in 'initsid.gtwboot' have been moved to initsid.ora. The syntax of the initsid.ora has been simplified. Refer to Appendix C for details.
When migrating from previous releases of TG4DRDA, please be aware of these differences.

Step 1: Copy the gateway initialization

Sample gateway initialization files (initsid.ora) are shipped on the distribution CDEROM. These files are in the ORACLE_HOME\tg4drda\admin directory:

- initDB2.ora, for DB2/OS390 remote servers

- initDB2VM.ora, for DB2/VM remote servers

- initAS400.ora, for DB2/400 remote servers

- initDB2UDB.ora, for DB2/UDB remote servers

Copy one of these sample files into the same directory, renaming it with the name of your gateway SID. For example, if you chose your SID to be DRD1 in "Choosing a Gateway System Identifier (SID)", and if your remote server is DB2, then copy the initDB2.ora file and rename it initDRD1.ora.

Step 2: Determine settings for gateway initialization parameters

Your Configuration Worksheet in Appendix E should be complete. If not, review the incomplete entries and refer to the sections listed for more information. You need this information to tailor the gateway initialization file, initsid.ora.

Refer to Appendix C, "DRDAESpecific Parameters" for information on the DRDAEspecific initsid.ora parameters.

Required Parameters

When you edit your initsid.ora file, you must change the values of all the parameters listed in the Configuration Worksheet in Appendix E, using the values in the rightEhand column of the worksheet.

You will also need to set certain NLS gateway parameters. For more information on setting these parameters, refer to Appendix D, "National Language Support".

Optional Parameters

Several DRDAEspecific parameters are not required, but you might want to change them. Unless otherwise indicated, these parameters are described in Appendix C.

Table 10-1 Optional DRDAESpecific Parameters

DRDA parameters

Description

DRDA_DISABLE_CALL

Used to disable stored procedure support for DRDA Servers on which the gateway does not support stored procedures

DRDA_ISOLATION_LEVEL

Defines the package Isolation Level

HS_DB_NAME

Specifies the database SID name and must be set to the gateway SID

DRDA_OPTIMIZE_QUERY

Used for data query optimization

DRDA_PACKAGE_COLLID

Defines the package collection ID

DRDA_PACKAGE_NAME

Defines the name of the package

DRDA_PACKAGE_OWNER

Defines the owner of the package. By default, the owner is the user ID that is used when you run the g4drutl bind utility. This parameter is not valid for SQL/DS.

DRDA_PACKAGE_SECTIONS

Defines the maximum number of concurrent OPEN cursors at the remote server

HS_DB_DOMAIN

Specifies the gateway database domain

The values that are set in your initsid.ora file should work for most installations. Edit the values if changes are needed. For information on NLSErelated initsid.ora parameters, refer to "NLS Parameters in the Gateway Initialization File".

Step 3: Tailor the initsid.ora File

After you have copied the sample initialization file, you will need to tailor it to your installation. While many parameters can be left to their defaults, some parameters must be changed for correct operation of the gateway. Give attention to the following DRDA and HS parameters. Also, give attention to the security aspects of the initialization file. Chapter 13, "Security Considerations", contains details on encryption of passwords that would otherwise be embedded in the initialization file. See Appendix C for a description of each parameter:

- DRDA_CONNECT_PARM

- DRDA_PACKAGE_COLLID

- DRDA_PACKAGE_NAME

- DRDA_PACKAGE_OWNER

- DRDA_REMOTE_DB_NAME

- FDS_CLASS

- HS_DB_NAME

- HS_DB_DOMAIN

Binding the DRDA Gateway Package

The product requires a package to be bound on the DRDA Server. The gateway has an internal, stored procedure that must be used to create this package. The internal stored procedure is called from an Oracle integrating server. (Refer to "Configuring Oracle Net" of Chapter 9, "Oracle Net". Also refer to "Configuring the Oracle Integrating Server" of this chapter.) Before this package can be bound on the DRDA Server, the gateway initialization file must be correctly configured. Refer to Appendix C.

1. Log on to an Oracle integrating server

Use either SQL*Plus or Server Manager:

> sqlplus system/manager

2. Create a database link

Create a database link with a user ID and with a password that has proper authority on the DRDA Server to create packages.

SQL> CREATE PUBLIC DATABASE LINK dblink
2 CONNECT TO userid IDENTIFIED BY password
3 USING 'tns_name_entry'

Note:
The user ID that is creating the public database link must have the "CREATE PUBLIC DATABASE LINK" privilege.

Refer to "Configuring the Oracle Integrating Server" later in this chapter.

3. Run the stored procedure GTW$_BIND_PKG

SQL> exec GTW$_BIND_PKG@dblink;
SQL> COMMIT;

This creates and commits the package. If any errors are reported, then correct the gateway initialization file parameters as needed.

Binding Packages on DB2/Universal Database (DB2/UDB)

If you are connecting to a DB2/UDB DRDA Server, then DB2/UDB requires that you create the ORACLE2PC table before binding the DRDA package. Other DRDA Servers enable you to bind the package before the ORACLE2PC table exists.

To create the ORACLE2PC table:

1. Log in to the system where DB2/UDB is running.
Check that you have the ability to address the DB2/UDB instance where the ORACLE2PC table will reside.

2. Copy the following files.

Copy from the ORACLE_HOME\tg4drda\install\db2udb directory:

- o2pc.sql  (SQL script for creating the table)

- o2pcg.sql (SQL script for granting package access to PUBLIC)

3. Connect to the database.

Use the user ID that you will use for binding the package:

$ db2 'CONNECT TO database USER userid USING password'

Note:
The user ID must have CONNECT, CREATETAB, and BINDADD authority to be able to connect to the database, to create the table, and to create the package.

For more information, refer to "DB2/UDB (Universal Database)".

4. Create the ORACLE2PC table:

$ db2 -tf o2pc.sql

5. Commit the transaction:

$ db2 'COMMIT'

6. Optionally, verify that the table was created under the correct user ID:

$ db2 'LIST TABLES FOR USER'
$ db2 'COMMIT'

7. Disconnect from the session:

$ db2 'DISCONNECT CURRENT'

DRDA Gateway Package Considerations

The DRDA package must be bound with the internal stored procedure GTW$_BIND_PKG. You must perform this bind step if this release is the first time the gateway has been installed on the system. If you are upgrading from version 9 of the gateway, then a rebind is not necessary unless the initialization parameters have been changed.

The user ID used to bind or rebind the DRDA package must have the suitable privileges on the remote database, as described in Chapter 5, "Configuring the DRDA Server".

Before Binding the DRDA Gateway Package

Check DRDA parameter settings and create your ORACLE2PC table before binding the DRDA gateway package.

Step 1: Check all DRDA parameter settings

Check all DRDA parameter settings to be sure that they are set correctly before you start the bind. For example, the default for DRDA_DISABLE_CALL works only if your DRDA database supports stored procedures. If not, then you must change the setting. Also, the value for DRDA_PACKAGE_NAME must be unique if you have any older versions of the gateway installed. New packages replace any old packages with the same name, causing versions of the gateway that use the old package to fail. Refer to Appendix C for information on the parameters and their settings.

Step 2: If using DB2/UDB, then create ORACLE2PC table

If your DRDA Server is DB2/UDB, then create the ORACLE2PC table. Refer to "Binding Packages on DB2/Universal Database (DB2/UDB)" for information on creating the table.

Sample SQL scripts

SQL scripts are provided to perform steps such as creating the ORACLE2PC table, removing obsolete tables and views, using previous releases, and creating tables and views to provide data dictionary support. Use the correct subdirectory for your DRDA Server platform:

tg4drda\install\db2 for DB2/OS390

tg4drda\install\as400 for DB2/400

tg4drda\install\db2vm for DB2/VM

tg4drda\install\db2udb for DB2/UDB

These scripts must be run on the DRDA Server platform using a database native tool (such as SPUFI on DB2/OS390), because no tool is provided with the gateway to run these scripts. Note that when running these scripts, the user ID used must be suitably authorized.

Step 1:  Run Data Dictionary scripts

If your DRDA Server is DB2/OS390, DB2/400, or DB2/UDB, then run the following scripts to create the Data Dictionary tables and view.

Step 1a:  Upgrading from a previous gateway version

If you are upgrading from a previous version of the gateway then run the dropold.sql script to drop the old data dictionary definitions.

Step 1b: Creating the Data Dictionary tables and views

Run the g4ddtab.sql and g4ddvwXX.sql scripts to create the Data Dictionary tables and views:

g4ddvwr7.sql DB2/OS390 V7 (RACF security)

g4ddvws7.sql DB2/OS390 V7 (DB2 security)

g4ddvwr8.sql DB2/OS390 V8 (RACF security)

g4ddvws8.sql DB2/OS390 V8 (DB2 security)

g4ddvw51.sql DB2/400 V5.1

g4ddvw52.sql DB2/400 V5.2

g4ddvwu7.sql DB2/UDB V7

g4ddvwu8.sql DB2/UDB V8

Step 2: DB2/UDB or other server

Depending on the DRDA Server, perform one of the following steps:

Step 2a: If server is DB2/UDB, then grant authority to package

If your DRDA Server is DB2/UDB, then the ORACLE2PC table has already been created (see the previous sections). For all users to be able to use the table, run o2pcg.sql granting authority to all users.

Step 2b: If server is not DB2/UDB, then create the ORACLE2PC table

If your DRDA Server is not DB2/UDB, then the ORACLE2PC table must be created. Run o2pc.sql.

Backup and Recovery of Gateway Configuration

The configuration of the gateway is stored in the gateway initialization file. These files are stored in ORACLE_HOME\tg4drda\admin. Becausee they are simple text files, you may back them up using an archiving tool of your choice.

Configuring the Oracle Integrating Server

Configure the Oracle integrating server, regardless of the platform on which it is installed. It can be on the host, but this is not required.

Step 1: Create a database link

To access the DRDA Server, you must create a public database link. A public database link is the most common of database links. Refer to "Processing a Database Link" for information about creating database links. In the following example, the Oracle Database server and the gateway are on the same host.

CREATE PUBLIC DATABASE LINK DB2 USING 'tns_name_entry'

Note:
The user ID that is creating the public database link must have the "CREATE PUBLIC DATABASE LINK" privilege.

Step 2: Create synonyms and views

To facilitate accessing data using the gateway, define synonyms and views for the DRDA data tables. If needed, then perform GRANT statements to ensure that the synonyms and views are accessible to the correct groups of users. For more information, refer to "Using the Synonym Feature".

Accessing the Gateway from Other Oracle Servers

Perform the following steps for each of the Oracle integrating servers from which you want to access the gateway:

1. Create a database link with which to access the gateway.

2. Define synonyms and views for tables.

These are for tables that are accessed through the gateway, if needed.

3. Perform GRANT statements.

These statements are for the synonyms and views that you create.

Provide local or Oracle Net access from the Oracle servers to the gateway.

Accessing Other DRDA Servers

To access other DRDA Servers from the Oracle integrating server, use the following steps:

1. Configure another APPC profile set for the DRDA Server.
Only Side Information and Partner LU Profiles must be new. You can point to existing configuration information for other profiles unless you need to modify other aspects of the connection. For example, if you are using a different network adapter, then you must configure an entire APPC profile set. No additional profiles need to be configured for TCP/IP.

2. Configure additional DRDA Server instances.

To configure an additional instance, create new gateway initialization files. If you are using Oracle Net, then add entries to the listener.ora file and the tnsnames.ora file with the new SIDs.

Other components, including the gateway ORACLE_HOME directory structure, can be shared among multiple gateway instances.

3. Bind the DRDA package to the DRDA Server.

Gateway Installation and Configuration Complete

The Oracle Transparent Gateway for DRDA installation and configuration process is now complete. The gateway is ready for use.

11 Using the Gateway

Using the gateway involves connecting to the gateway system and the remote DRDA database that is associated with it. Understanding how to process and how to use database links is important. Database links are discussed in detail in the Oracle Database Administrator's Guide. Read the database link information in that guide to understand database link processing. Then, read this chapter to understand how to set up a database link to a remote DRDA database.

This chapter contains the following sections:

- Processing a Database Link

- Accessing the Gateway

- Accessing AS/400 File Members

- Using the Synonym Feature

- Performing Distributed Queries

- ReadEOnly Gateway

- Replicating in a Heterogeneous Environment

- Copying Data from the Oracle Server to the DRDA Server

- Copying Data from the DRDA Server to the Oracle Server

- Tracing SQL Statements

Processing a Database Link

The database and application administrators of a distributed database system are responsible for managing the necessary database links that define paths to the DRDA database.

Creating Database Links

To create a database link and define a path to a remote database, use the CREATE DATABASE LINK statement. The CONNECT TO clause specifies the remote user ID and password to use when creating a session in the remote database. The USING clause points to a tnsnames.ora connect descriptor.

Note:
If you do not specify a user ID and a password in the CONNECT TO clause, then the Oracle server user ID and password are used. For additional information, refer to Chapter 13, "Security Considerations".

The following syntax creates a database link to access information in the DRDA Server database:

CREATE PUBLIC DATABASE LINK dblink
CONNECT TO userid IDENTIFIED BY password
USING 'tns_name_entry';

where:

dblink is the complete database link name.

userid is the user ID that is used to establish a session in the remote database. This user ID must be a valid DRDA Server user ID. It must be authorized to any table or file on the DRDA Server that is referenced in the SQL commands. The user ID cannot be longer than eight characters.

password is the password that is used to establish a session in the remote database. This must be a valid DRDA Server password. The password cannot be longer than eight characters.

tns_name_entry specifies the Oracle Net TNS connect descriptor that is used to identify the gateway.

Guidelines for Database Links

Database links are active for the duration of a gateway session. If you want to close a database link during a session, then use the ALTER session statement.

Dropping Database Links

You can drop a database link with the DROP DATABASE LINK statement. For example, to drop the public database link named dblink, enter the statement:

DROP PUBLIC DATABASE LINK dblink;

Attention:
A database link should not be dropped if it is required to resolve an inEdoubt distributed transaction. Refer to the Oracle Database Administrator's Guide for additional information about dropping database links.

Examining Available Database Links

The data dictionary of each database stores the definitions of all the database links in that database. Your USER_DB_LINKS data dictionary view shows your defined database links. The ALL_DB_LINKS data dictionary views show all defined database links.

Limiting the Number of Active Database Links

You can limit the number of connections from a user process to remote databases by using the parameter OPEN_LINKS. This parameter controls the number of remote connections that any single user process can use concurrently with a single SQL statement. Refer to the Oracle Database Administrator's Guide for additional information about limiting the number of active database links.

Accessing the Gateway

To access the gateway, complete the following steps on the Oracle integrating server.

Step 1: Log in to the Oracle integrating server

This is the first step to accessing the gateway.

Step 2: Create a database link to the DRDA database

For example, use:

CREATE PUBLIC DATABASE LINK DRDA
CONNECT TO user id IDENTIFIED BY password
USING 'tns_name_entry'

Step 3: Retrieve data from the DRDA database

This query fetches the TABLE file in the library SECURE, using the name ORACLE as the DRDA Server user profile. The ORACLE user profile must have the suitable privilege on the DRDA Server to access the SECURE.TABLE files:

SELECT * FROM SECURE.TABLE@DRDA

The following messages are displayed if insufficient privileges were granted to the ORACLE user profile:

ORA-1031:   insufficient privileges
TG4DRDA V10.2.0.1.0 grc=0, drc=-777 (83TC,0000), errp=ARIXO,
sqlcode=-551, sqlstate=42501, errd=FFFFFF9C,0,0,0,0,0
errmc=USER SELECT SECURE.TABLE

Accessing AS/400 File Members

There is nothing specific to DRDA or to the gateway that enables or does not enables access to AS/400 files and file members. However, DB2/400 uses a naming convention that implies that the file member name is the same as the name of the file being addressed. For example, accessing schema.table implies that table is the file name and also that table is the file member name being accessed.

To access file members with names that differ from the associated file name, you must create a view within the file so that DB2/400 can reference the correct file member.

The method involves running the console command Create Logical File (CRTLF). This action creates a logical association between the file name and the file member name.

For additional information, refer to the AS/400 Command documentation or to the DB2/400 SQL reference.

Using the Synonym Feature

You can provide complete data, location, and network transparency by using the synonym feature of the Oracle server. When a synonym is defined, the user need not know the underlying table or network protocol being used. A synonym can be public, available to all Oracle users. A synonym can also be defined as private, available only to the user who created it. Refer to the Oracle Database Administrator's Guide for details on the synonym feature.

The following statement creates a systemwide synonym for the EMP file in the DRDA Server with ownership of Oracle:

CREATE PUBLIC SYNONYM EMP FOR ORACLE.EMP@DRDA

Performing Distributed Queries

The Oracle Transparent Gateway technology enables the processing of distributed queries that join Oracle servers and DRDA Servers, and any other data store for which Oracle Corporation provides a gateway. These complex operations can be completely transparent to the users requesting the data.

The distributed query optimizer (DQO) capability can provide better performance of distributed queries. Statistical data regarding tables from DRDA Servers is retrieved and passed to the Oracle integrating server. The DQO capability is turned on and off by the DRDA_OPTIMIZE_QUERY parameter. Refer to "DRDA_OPTIMIZE_QUERY" of Appendix C, "DRDAESpecific Parameters".

Example of a Distributed Query

The following example joins data between an Oracle server, DB2/OS390, and a DRDA Server:

SELECT o.custname, p.projno, e.ename, sum(e.rate*p.hours)
FROM orders@DB2 o, EMP@ORACLE7 e, projects@DRDA p
WHERE o.projno = p.projno
AND p.empno = e.empno
GROUP BY o.custname, p.projno, e.ename

A combination of views and synonyms, using the following SQL statements, keeps the process of distributed queries transparent to the user:

CREATE SYNONYM orders for orders@DB2;
CREATE SYNONYM PROJECTS for PROJECTS@DRDA;
CREATE VIEW details (custname,projno,ename,spend)
AS
SELECT o.custname, p.projno, e.ename, sum(e.rate*p.hours)
FROM orders o, EMP e, projects p
WHERE o.projno = p.projno
AND p.empno = e.empno
GROUP BY o.custname, p.projno, e.ename;

This SQL statement retrieves information from these three data stores in one command:

SELECT * FROM DETAILS;

The results of this command are:

CUSTNAME   PROJNO     ENAME     SPEND
---------  ---------  --------  --------
ABC Co.    1          Jones     400
ABC Co.    1          Smith     180
XYZ Inc.   2          Jones     400
XYZ Inc.   2          Smith     180

TwoEPhase Commit Processing

To fully participate in a twoEphase commit transaction, a server must support the PREPARE TRANSACTION statement. The PREPARE TRANSACTION statement ensures that all participating databases are prepared to COMMIT or ROLLBACK a specific unit of work.

The Oracle server supports the PREPARE TRANSACTION statement. Any number of Oracle servers can participate in a distributed twoEphase commit transaction. The PREPARE TRANSACTION statement is performed automatically when a COMMIT transaction is run explicitly by an application or implicitly at the normal end of the application. No other action is needed.

The gateway does not support the PREPARE TRANSACTION statement limiting the twoEphase commit protocol when the gateway participates in a distributed transaction. The gateway becomes the commit focal point site of a distributed transaction. Because the gateway is configured as commit/confirm, it is always the commit point site, regardless of the commit point strength setting. The gateway commits the unit of work after verifying that all Oracle databases in the transaction have successfully committed their work. Because the gateway must coordinate the distributed transaction, only one gateway can participate in an Oracle twoEphase commit transaction.

TwoEphase commit transactions are recorded in the ORADRDA.ORACLE2PC table, which is created during installation. This table is created when the o2pc.sql script is run. The owner of this table also owns the package. Refer to "DRDA Gateway Package Considerations" for more information.

Distributed DRDA Transactions

Because the ORACLE2PC table is used to record the status of a gateway transaction, the table must reside at the database where the DRDA update takes place. Therefore, all updates that take place over the gateway must be local to the IBM database.

Note:
Updates to the ORACLE2PC table cannot be part of an IBM distributed transaction.

For additional information about the twoEphase commit process, refer to the Oracle Database Administrator's Guide.

ReadEOnly Gateway

The readEonly option can provide improved performance and security. This improved performance depends on your configuration and parameter selections. A gateway initialization parameter, DRDA_READ_ONLY, is used to control whether the gateway is enabled in this mode.

If you enable the readEonly feature, then only queries (SELECT statements) are permitted by the gateway. The capabilities that control whether updates are permitted through the gateway are not enabled. These capabilities include INSERT, UPDATE, DELETE, and storedEprocedure support (passEthrough SQL and DB2 stored procedures). Statements attempting to modify records on the DRDA Server are rejected.

Oracle recommends that you do not routinely switch between settings of the DRDA_READ_ONLY parameter. If you need both update and DRDA_READ_ONLY functionality, then you should create two separate instances of the gateway with different readEonly settings.

Replicating in a Heterogeneous Environment

Oracle Transparent Gateway for DRDA provides a number of options for replicating Oracle and nonEOracle data throughout the enterprise.

Oracle Database 10g Server Triggers

When updates are made to the Oracle Database server, synchronous copies of Oracle and nonEOracle data can be maintained automatically by using Oracle Database 10g server triggers.

Oracle Snapshots

Oracle Transparent Gateway for DRDA can use the Oracle snapshot feature to automatically replicate nonEOracle data into the Oracle Database server. The complete refresh capability of Oracle Snapshot can be used to propagate a complete copy or a subset of the nonEOracle data into the Oracle Database server at userEdefined intervals.

Copying Data from the Oracle Server to the DRDA Server

The COPY command enables you to copy data from an Oracle Database server to a DRDA Server database. The Oracle SQL command INSERT is not supported. If you use the INSERT command:

INSERT INTO DRDA_table SELECT * FROM local_table

then the following message is displayed:

ORA-2025:All tables in the SQL statement must be at the remote database

To copy data from your local database to the DRDA Server, use:

COPY FROM user id/password@dblink-
INSERT destination_table -
USING query

For example, to select all rows from the local Oracle EMP table, to insert them into the EMP table on the DRDA Server, and to commit the transaction, use:

COPY FROM scott/tiger@Oracle -
INSERT scott.EMP@DRDA -
USING SELECT * FROM EMP

The SQL*Plus COPY command supports APPEND, CREATE, INSERT, and REPLACE options. However, INSERT is the only option supported when copying to the DRDA Server. For more information about the COPY command, refer to the SQL*Plus User's Guide and Reference.

Copying Data from the DRDA Server to the Oracle Server

The CREATE TABLE command enables you to copy data from a DRDA Server database to an Oracle Database server. To create a table on your local database and to insert rows from a DRDA Server table, use:

CREATE TABLE table_name
AS query

The following example creates the table EMP in your local Oracle database and inserts the rows from the EMP table on the DRDA Server:

CREATE TABLE EMP
AS SELECT * FROM scott.EMP@DRDA

Alternatively, you can use the SQL*Plus COPY command to copy data from a DRDA Server to an Oracle Database server. For more information about the COPY command, refer to the SQL*Plus User's Guide and Reference.

Tracing SQL Statements

SQL statements run through the gateway can be changed before reaching the DRDA database. These changes are made to make the format acceptable to the gateway or to make Oracle SQL compatible with DRDA Server SQL. The Oracle integrating server and the gateway can change the statements depending upon the situation.

For various reasons, you might need to assess whether the gateway altered the statement correctly or whether the statement could be rewritten to improve performance. SQL tracing is a feature that enables you to see the changes made to a SQL statement by the Oracle integrating server or the gateway.

SQL tracing reduces gateway performance. Use tracing only while testing and debugging the application. Do not enable SQL tracing when the application is running in a production environment. For more information about enabling SQL tracing, refer to the section on "SQL Tracing and the Gateway" in Chapter 15, " Error Messages, Diagnosis, and Reporting".

12 Developing Applications

The Oracle Transparent Gateway for DRDA enables applications written for the Oracle server to access tables in a DRDA database. This access can be virtually transparent by using synonyms or views of the DRDA tables accessed by a database link. However, there are fundamental SQL, data type, and semantic differences between the Oracle server and DRDA databases. Read this chapter to learn about these differences.

This chapter provides information that is specific to this release of the Oracle Transparent Gateway for DRDA, including the following sections:

- Gateway Appearance to Application Programs

- Using Oracle Stored Procedures with the Gateway

- Using DRDA Server Stored Procedures with the Gateway

- Database Link Behavior

- Oracle Server SQL Construct Processing

- Native Semantics

- DRDA Data Type to Oracle Data Type Conversion

- Passing Native SQL Statements through the Gateway

- Oracle Data Dictionary Emulation on a DRDA Server

- Defining the Number of DRDA Cursors

Gateway Appearance to Application Programs

An application written to access information in a DRDA database interfaces with an Oracle integrating server. When developing applications, keep the following information in mind:

- You must define the DRDA database to the application by the use of a database link defined at the Oracle integrating server. Your application specifies tables that exist on a DRDA database using the name defined in the database link. For example, assume that a database link is defined so that it names the DRDA database link DRDA, and also assume that an application needs to retrieve data from an Oracle database and from the DRDA database. Use the following SQL statement in your application:

SELECT EMPNO, SALARY
FROM EMP, EMPS@DRDA
WHERE

In this example, EMP is a table on an Oracle server, and EMPS is a table on a DRDA Server. You can also define a synonym or a view on the DRDA Server table, and access the information without the database link suffix.

- You can perform reads and writes of data to a defined DRDA database. SELECT, INSERT, UPDATE, and DELETE are all valid operations.

- A single transaction can write to one DRDA database and to multiple Oracle databases.

- Single SQL statements, using JOIN, can refer to tables in multiple Oracle databases or in multiple DRDA databases, or in both.

Fetch Reblocking

The gateway supports fetch reblocking with the HS_RPC_FETCH_REBLOCKING parameter.

When the value of this parameter is set to ON (the default), the array size for SELECT statements is determined by the HS_RPC_FETCH_SIZE value. The HS_RPC_FETCH_SIZE parameter defines the number of bytes sent with each buffer from the gateway to the Oracle Database 10g server. The buffer might contain one or more qualified rows from the DRDA Server. This feature can provide significant performance enhancements, depending on your application design, installation type, and workload.

The array size between the client and the Oracle Database 10g server is still determined by the Oracle application.

Refer to Chapter 10, "Configuring the Gateway" for more information.

Using Oracle Stored Procedures with the Gateway

The gateway stored procedure support is an extension of Oracle stored procedures. An Oracle stored procedure is a schema object that logically groups a set of SQL and other PL/SQL programming language statements together to perform a specific task. Oracle stored procedures are stored in the database for continued use. Applications use standard Oracle PL/SQL to call stored procedures.

Oracle stored procedures can be located in a local instance of the Oracle Database 10g server and a remote instance. The following example shows two stored procedures, oraproc1 and oraproc2. While oraproc1 is a procedure stored in the ORA1 Oracle instance, oraproc2 is a procedure stored in the ORA2 Oracle instance.

Figure 12-1 Calling Oracle Stored Procedures in a Distributed Oracle Environment

To maintain location transparency in the application, a synonym can be created:

CREATE SYNONYM oraproc2 FOR oraproc2@ora2;

After this synonym is created, the application no longer needs to use the database link specification to call the stored procedure at the remote Oracle instance.

In Figure 12-1, the second statement in oraproc1 is used to access a table in the ORA2 instance. In the same way, Oracle stored procedures can be used to access DB2 tables through the gateway.

Using DRDA Server Stored Procedures with the Gateway

The procedural feature of the gateway enables calling of native DRDA Server stored procedures. In other words, the stored procedure is no longer defined in the Oracle Database 10g server, but instead, is defined to the DRDA Server (for example, DB2/OS390). Again, standard Oracle PL/SQL is used by the Oracle application to run the stored procedure.

The gateway does not require special definitions to call the DB2 stored procedure. Once the stored procedure is defined to the DRDA Server (e.g., DB2/OS390), the gateway will be able to use the existing DRDA Server definition to run the procedure.

In Figure 12-2, an Oracle application calls the empproc stored procedure defined to the DRDA Server (for example, DB2/OS390).

Figure 12-2 Running DRDA Server Stored Procedures

From the perspective of the application, running the DB2 stored procedure is no different than calling a stored procedure at a remote Oracle instance.

Oracle Application and DRDA Server Stored Procedure Completion

As an example, suppose an Oracle application attempts to call a stored procedure in a DB2/OS390 database. In order for an Oracle application to call a DB2 stored procedure, the DB2 stored procedure must first be created on the DB2 system by using the procedures documented in the IBM reference document for DB2 for OS/390 SQL.

After the stored procedure is defined to DB2, the gateway will be able to access the data using a standard PL/SQL call. For example, an employee name, JOHN SMYTHE, is passed to the DB2 stored procedure REVISE_SALARY. The DB2 stored procedure retrieves the salary value from the DB2 database to calculate a new yearly salary for JOHN SMYTHE. The revised salary returned in RESULT is used to update the EMP table of an Oracle database server:

DECLARE
INPUT VARCHAR2(15);
RESULT NUMBER(8,2);
BEGIN
INPUT := 'JOHN SMYTHE';
REVISE_SALARY@DB2(INPUT, RESULT);
UPDATE EMP SET SAL = RESULT WHERE ENAME = INPUT;
END;

When the gateway receives a call to run a stored procedure on the DRDA Server (for example, DB2/OS390), it first does a lookup of the procedure name in the server catalog. The information that defines a stored procedure is stored in different forms on each DRDA Server. For example, DB2/OS390 V5.0 uses the table SYSIBM.SYSPROCEDURES, while DB2/OS390 V6.1 uses the tables SYSIBM.SYSROUTINES and SYSIBM.SYSPARMS, and DB2/400 uses the tables QSYS2.SYSPROCS and QSYS2.SYSPARMS. The gateway has a list of known catalogs to search, depending on the DRDA Server being accessed.

The search order of the catalogs is dependent on whether the catalogs support location designators (such as LUNAME in SYSIBM.SYSPROCEDURES), and Authorization or Owner IDs (such as AUTHID in SYSIBM.SYSPROCEDURES or OWNER in SYSIBM.SYSROUTINES).

Some DRDA Servers enable blank or public Authorization qualifiers. If the currently connected DRDA Server supports this form of qualification, then the gateway will apply those naming rules when searching for a procedure name in the catalog.

The matching rules will first search for a Public definition, and then an owner-qualified procedure name. For more detailed information, refer to the IBM reference document for DB2 for OS/390 SQL for the underlying database of the DRDA Server.

Procedural Feature Considerations with DB2

The following are special considerations for using the procedural feature with the gateway:

- DB2 stored procedures do not have the ability to coordinate, commit, and rollback activity on recoverable resources such as IMS or CICS transactions. Therefore, if the DB2 stored procedure calls a CICS or IMS transaction, then it is considered a separate unit of work and does not affect the completion of the stored procedure. This means that if you are running a DB2 stored procedure from an Oracle application, and if this procedure calls a CICS or IMS transaction, then the gateway cannot recover from any activity that occurred within the CICS or IMS transaction.
For example, the CICS transaction could roll back a unit of work, but this does not prevent the gateway from committing other DB2 work contained within the DB2 stored procedure.

Likewise, if the DB2 stored procedure updated an irrecoverable resource such as a VSAM file, then the gateway considers this activity separate from its own recoverable unit of work.

- PL/SQL records cannot be passed as parameters when calling a DB2 stored procedure.

- The gateway supports the SIMPLE linkage convention of DB2 stored procedures.
The SIMPLE linkage convention means that the parameters that are passed to and from the DB2 stored procedure cannot be null.

Database Link Behavior

A connection to the gateway is established through a database link when it is first used in an Oracle session. In this context, connection refers to both the connection between the Oracle integrating server and the gateway, and to the DRDA network connection between the gateway and the target DRDA database. The connection remains established until the Oracle session ends. Another session or user can access the same database link and get a distinct connection to the gateway and DRDA database.

Connections to the DRDA database can be limited in an APPC configuration in a parallel session limit, or by other factors, such as memory, gateway parameters, or DRDA Server resources. In a TCP/IP configuration, only resource limits (such as memory) or limits on the number of connections by the DRDA Server will limit the number of connections between the gateway and the DRDA Server.

Oracle Server SQL Construct Processing

One of the most important features of the Oracle Enterprise Integration Gateways family of products is their ability to provide SQL transparency to the user and to the application programmer. Foreign SQL constructs can be categorized into four areas:

- Compatible

- Translated

- Compensated

- Native semantics

Compatible SQL Functions

The Oracle integrating server automatically forwards to the DRDA database compatible SQL functions, that is, SQL constructs with the same syntax and meaning on both the Oracle server and DRDA database. These SQL constructs are forwarded unmodified. All of the compatible functions are column functions. Functions that are not compatible are either translated to an equivalent DRDA SQL function or are compensated by the Oracle server after the data is returned from the DRDA database.

Translated SQL Functions

Translated functions have the same meaning but different names between the Oracle integrating server and the DRDA database, but all applications must use the Oracle function name. These SQL constructs that are supported with different syntax (such as different function names) by the DRDA database, are automatically translated by the Oracle server and then forwarded to the DRDA database. The Oracle integrating server, transparent to your application, changes the function name before sending it to the DRDA database.

Compensated SQL Functions

Some advanced SQL constructs that are supported by the Oracle server may not be supported in the same manner, if at all, by the DRDA database. Compensated functions are those SQL functions that are not recognized by the DRDA Server. If a SELECT statement containing one of these functions is passed from the Oracle integrating server to the gateway, then the gateway removes the function before passing the SQL statement to the DRDA Server. The gateway passes the selected DRDA database rows to the Oracle integrating server. The Oracle integrating server then applies the function.

The Oracle server can compensate for the missing or incompatible function by automatically excluding the incompatible SQL construct from the SQL request that is forwarded to the DRDA database. The Oracle server then retrieves the necessary data from the DRDA database and applies the function. This activity is known as postprocessing.

The gateway attempts to pass all SQL functions to DRDA databases. But when a DRDA database does not support a function represented in the computation, then the gateway changes that function. For example, if a program requests:

SELECT COS(X_COOR) FROM TABLE_X;

from a DB2/OS390 database, which does not support the meaning of COS, then the gateway changes the SELECT statement to:

SELECT X_COOR FROM TABLE_X;

All data in the X_COOR column of TABLE_X is passed from the DB2/OS390 database to the Oracle integrating server. After the data is moved to the Oracle integrating server, the COS function is performed.

If you are performing operations on large amounts of data stored in a DRDA database, then keep in mind that some functions require postprocessing.

Native Semantic SQL Functions

Some SQL functions that are normally compensated may also be overridden, through the Native Semantics facility. If a SQL function has been enabled for Native Semantics, then the function may be passed on to the DRDA database for processing, instead of being compensated (postEprocessed). Refer to Native Semantics.

DB2/OS390 SQL Compatibility

The ways that the Oracle Database server and gateway handle SQL functions for a DB2/OS390 database are shown in Table 12-1.

Table 12-1 DB2/OS390 SQL Compatibility, by Oracle SQL Function

Oracle SQL Function

Compatible

Translated

Compensated

Native Semantics Candidate

ABS

Yes

Yes

ACOS

Yes

Yes

ADD_MONTHS

Yes

ASCII

Yes

Yes

ASIN

Yes

Yes

ATAN

Yes

Yes

ATAN2

Yes

Yes

AVG

Yes

BITAND

Yes

Yes

CAST

Yes

Yes

CEIL

CEILING

Yes

CHARTOROWID

Yes

CHR

Yes

Yes

CONCAT

Yes

CONVERT

Yes

Yes

COS

Yes

Yes

COSH

Yes

Yes

COUNT(*)

Yes

COUNT (DISTINCT colname)

Yes

COUNT (ALL colname)

Yes

COUNTCOL

COUNT (column)

Yes

COUNTCOL

DECODE

Yes

Yes

DUMP

Yes

Yes

EXP

Yes

Yes

FLOOR

Yes

Yes

GREATEST

Yes

Yes

HEXTORAW

Yes

Yes

INITCAP

Yes

Yes

INSTR

Yes

Yes

INSTRB

Yes

Yes

LAST_DAY

Yes

LEAST

Yes

Yes

LENGTH

Yes

Yes

LENGTHB

Yes

Yes

LN

Yes

Yes

LOG

Yes

Yes

LOWER

Yes

Yes

LPAD

Yes

Yes

LTRIM

Yes

Yes

MAX

Yes

MIN

Yes

MOD

Yes

Yes

MONTHS_BETWEEN

Yes

NEW_TIME

Yes

NEXT_DAY

Yes

NLS_INITCAP

Yes

Yes

NLS_LOWER

Yes

Yes

NLS_UPPER

Yes

Yes

NLSSORT

Yes

Yes

NVL

VALUE

NVL2

Yes

Yes

POWER

Yes

Yes

RAWTOHEX

Yes

Yes

REPLACE

Yes

Yes

REVERSE

Yes

Yes

ROUND

Yes

Yes

ROWIDTOCHAR

Yes

RPAD

Yes

Yes

RTRIM

Yes

Yes

SIGN

Yes

Yes

SIN

Yes

Yes

SINH

Yes

Yes

SOUNDEX

Yes

SQRT

Yes

Yes

STDDEV

Yes

Yes

SUBSTR

Yes

Yes

SUBSTRB

Yes

Yes

SUM

Yes

SYSDATE

Yes

TAN

Yes

Yes

TANH

Yes

Yes

TO_CHAR

Yes

TO_DATE

Yes

TO_MULTI_BYTE

Yes

TO_NUMBER

DECIMAL

Yes

TO_SINGLE_BYTE

Yes

TRANSLATE

Yes

Yes

TRIM

STRIP

Yes

Yes

TRUNC

Yes

Yes

UID

Yes

UPPER

Yes

Yes

USER

Yes

USERENV

Yes

VARIANCE

Yes

Yes

VSIZE

Yes

Yes

DB2/Universal Database SQL Compatibility

The ways that the Oracle Database server and gateway handle SQL functions for a DB2/UDB database are shown in the following table:

Table 12-2 DB2/Universal Database SQL Compatibility, by Oracle SQL Function

Oracle SQL Function

Compatible

Translated

Compensated

Native Semantics Candidate

ABS

Yes

Yes

ACOS

Yes

Yes

ADD_MONTHS

Yes

ASCII

Yes

Yes

ASIN

Yes

Yes

ATAN

Yes

Yes

ATAN2

Yes

Yes

AVG

Yes

BITAND

Yes

Yes

CAST

Yes

Yes

CEIL

CEILING

Yes

CHARTOROWID

Yes

CHR

Yes

Yes

CONCAT

Yes

CONVERT

Yes

Yes

COS

Yes

Yes

COSH

Yes

Yes

COUNT(*)

Yes

COUNT (DISTINCT colname)

Yes

COUNT (ALL colname)

Yes

COUNTCOL

COUNT (column)

Yes

COUNTCOL

DECODE

Yes

Yes

DUMP

Yes

Yes

EXP

Yes

Yes

FLOOR

Yes

Yes

GREATEST

Yes

Yes

HEXTORAW

Yes

Yes

INITCAP

Yes

Yes

INSTR

Yes

Yes

INSTRB

Yes

Yes

LAST_DAY

Yes

LEAST

Yes

Yes

LENGTH

Yes

Yes

LENGTHB

Yes

Yes

LN

Yes

Yes

LOG

Yes

Yes

LOWER

LCASE

Yes

LPAD

Yes

Yes

LTRIM

Yes

Yes

MAX

Yes

MIN

Yes

MOD

Yes

Yes

MONTHS_BETWEEN

Yes

NEW_TIME

Yes

NEXT_DAY

Yes

Yes

NLS_INITCAP

Yes

Yes

NLS_LOWER

Yes

Yes

NLS_UPPER

Yes

Yes

NLSSORT

Yes

Yes

NVL

VALUE

NVL2

Yes

Yes

POWER

Yes

Yes

RAWTOHEX

Yes

Yes

REPLACE

Yes

Yes

REVERSE

Yes

Yes

ROUND

Yes

Yes

ROWIDTOCHAR

Yes

RPAD

Yes

Yes

RTRIM

Yes

Yes

SIGN

Yes

Yes

SIN

Yes

Yes

SINH

Yes

Yes

SOUNDEX

Yes

SQRT

Yes

Yes

STDDEV

Yes

Yes

SUBSTR

Yes

Yes

SUBSTRB

Yes

Yes

SUM

Yes

SYSDATE

Yes

TAN

Yes

Yes

TANH

Yes

Yes

TO_CHAR

Yes

TO_DATE

Yes

TO_MULTI_BYTE

Yes

TO_NUMBER

DECIMAL

Yes

TO_SINGLE_BYTE

Yes

TRANSLATE

Yes

Yes

TRIM

Yes

Yes

TRUNC

Yes

Yes

UID

Yes

UPPER

UCASE

Yes

USER

Yes

USERENV

Yes

VARIANCE

Yes

Yes

VSIZE

Yes

Yes

DB2/400 SQL Compatibility

The ways that the Oracle Database server and gateway handle SQL functions for a DB2/400 database are shown in the following table:

Table 12-3 DB2/400 SQL Compatibility, by Oracle SQL Function

Oracle SQL Function

Compatible

Translated

Compensated

Native Semantics Candidate

ABS

ABSVAL

Yes

ACOS

Yes

Yes

ADD_MONTHS

Yes

ASCII

Yes

Yes

ASIN

Yes

Yes

ATAN

Yes

Yes

ATAN2

Yes

Yes

AVG

Yes

BITAND

Yes

Yes

CAST

Yes

Yes

CEIL

CEILING

Yes

CHARTOROWID

Yes

CHR

Yes

Yes

CONCAT

Yes

CONVERT

Yes

Yes

COS

Yes

Yes

COSH

Yes

Yes

COUNT(*)

Yes

COUNT (DISTINCT colname)

Yes

COUNT (ALL colname)

Yes

COUNTCOL

COUNT (column)

Yes

COUNTCOL

DECODE

Yes

Yes

DUMP

Yes

Yes

EXP

Yes

Yes

FLOOR

Yes

Yes

GREATEST

Yes

Yes

HEXTORAW

Yes

Yes

INITCAP

Yes

Yes

INSTR

Yes

Yes

INSTRB

Yes

Yes

LAST_DAY

Yes

LEAST

Yes

Yes

LENGTH

Yes

Yes

LENGTHB

Yes

Yes

LN

Yes

Yes

LOG

Yes

Yes

LOWER

Yes

Yes

LPAD

Yes

Yes

LTRIM

Yes

Yes

MAX

Yes

MIN

Yes

MOD

Yes

Yes

MONTHS_BETWEEN

Yes

NEW_TIME

Yes

NEXT_DAX

Yes

NLS_INITCAP

Yes

Yes

NLS_LOWER

Yes

Yes

NLS_UPPER

Yes

Yes

NLSSORT

Yes

Yes

NVL

VALUE

NVL2

Yes

Yes

POWER

Yes

Yes

RAWTOHEX

Yes

Yes

REPLACE

Yes

Yes

REVERSE

Yes

Yes

ROUND

Yes

Yes

ROWIDTOCHAR

Yes

RPAD

Yes

Yes

RTRIM

Yes

Yes

SIGN

Yes

Yes

SIN

Yes

Yes

SINH

Yes

Yes

SOUNDEX

Yes

SQRT

Yes

Yes

STDDEV

Yes

Yes

SUBSTR

Yes

Yes

SUBSTRB

Yes

Yes

SUM

Yes

SYSDATE

Yes

TAN

Yes

Yes

TANH

Yes

Yes

TO_CHAR

Yes

TO_DATE

Yes

TO_MULTI_BYTE

Yes

TO_NUMBER

DECIMAL

Yes

TO_SINGLE_BYTE

Yes

TRANSLATE

Yes

Yes

TRIM

Yes

Yes

TRUNC

Yes

Yes

UID

Yes

UPPER

TRANSLATE

Yes

USER

Yes

USERENV

Yes

VARIANCE

VAR

Yes

VSIZE

Yes

Yes

DB2/VM SQL Compatibility

The ways that the Oracle Database server and gateway handle SQL functions for a DB2/VM database are shown in the following table:

Table 12-4 DB2/VM SQL Compatibility, by Oracle SQL Function

Oracle SQL Function

Compatible

Translated

Compensated

Native Semantics Candidate

ABS

Yes

Yes

ACOS

Yes

Yes

ADD_MONTHS

Yes

ASCII

Yes

Yes

ASIN

Yes

Yes

ATAN

Yes

Yes

ATAN2

Yes

Yes

AVG

Yes

BITAND

Yes

Yes

CAST

Yes

Yes

CEIL

Yes

CHARTOROWID

Yes

CHR

Yes

Yes

CONCAT

Yes

CONVERT

Yes

Yes

COS

Yes

Yes

COSH

Yes

Yes

COUNT(*)

Yes

COUNT (DISTINCT colname)

Yes

COUNT (ALL colname)

Yes

COUNT (COLUMN)

Yes

DECODE

Yes

Yes

DUMP

Yes

Yes

EXP

Yes

Yes

FLOOR

Yes

GREATEST

Yes

Yes

HEXTORAW

Yes

Yes

INITCAP

Yes

Yes

INSTR

Yes

Yes

INSTRB

Yes

Yes

LAST_DAY

Yes

LEAST

Yes

Yes

LENGTH

Yes

Yes

LENGTHB

Yes

Yes

LN

Yes

Yes

LOG

Yes

Yes

LOWER

Yes

Yes

LPAD

Yes

Yes

LTRIM

Yes

Yes

MAX

Yes

MIN

Yes

MOD

Yes

Yes

MONTHS_BETWEEN

Yes

NEW_TIME

Yes

NEXT_DAY

Yes

NLS_INITCAP

Yes

Yes

NLS_LOWER

Yes

Yes

NLS_UPPER

Yes

Yes

NLSSORT

Yes

Yes

NVL

VALUE

NVL2

Yes

Yes

POWER

Yes

Yes

RAWTOHEX

Yes

Yes

REPLACE

Yes

Yes

REVERSE

Yes

Yes

ROUND

Yes

Yes

ROWIDTOCHAR

Yes

RPAD

Yes

Yes

RTRIM

Yes

Yes

SIGN

Yes

Yes

SIN

Yes

Yes

SINH

Yes

Yes

SOUNDEX

Yes

SQRT

Yes

Yes

STDDEV

Yes

Yes

SUBSTR

Yes

Yes

SUBSTRB

Yes

Yes

SUM

Yes

SYSDATE

Yes

TAN

Yes

Yes

TANH

Yes

Yes

TO_CHAR

Yes

TO_DATE

Yes

TO_MULTI_BYTE

Yes

TO_NUMBER

Yes

Yes

TO_SINGLE_BYTE

Yes

TRANSLATE

Yes

Yes

TRIM

Yes

Yes

TRUNC

Yes

Yes

UID

Yes

UPPER

Yes

Yes

USER

Yes

USERENV

Yes

VARIANCE

Yes

Yes

VSIZE

Yes

Yes

Native Semantics

Because some of the advanced SQL constructs that are supported by the Oracle server may not be supported in the same manner (if at all) by the DRDA database, the Oracle server compensates for the missing or incompatible functionality by postprocessing the DRDA database data with Oracle (refer to the previous section, "Oracle Server SQL Construct Processing",). This feature provides maximum transparency, but may impact performance. In addition, new versions of a particular DRDA database may implement previously unsupported functions or capabilities, or they may change the supported semantics in such a manner as to make them more compatible with Oracle functions.

Some of the DRDA Servers also provide support for userEdefined functions. The user may choose to implement Oracle functions natively, thus enabling the DRDA Server to pass the function on to the underlying database implementation (for example, DB2). Native Semantics provides a method of enabling specific capabilities to be processed natively by the DRDA Server.

Various considerations must be taken into account when enabling the Native Semantic feature of a particular function, because Native Semantics has advantages and disadvantages. For example, a tradeEoff typically exists between transparency and performance. One such consideration is transparency of data coercion. Oracle provides coercion (implicit data conversion) for many SQL functions. This means that if the supplied value for a particular function is not correct, then Oracle will coerce the value to the correct type before processing it. However, with the Native Semantic feature enabled, the value (exactly as provided) will be passed through to the DRDA Server for processing. In many cases, the DRDA Server will not be able to coerce the value to the correct type and will therefore generate an error.

Another consideration involves the compatibility of parameters to a particular SQL function. For instance, the Oracle implementation of SUBSTR permits negative values for the string index, whereas most DRDA Server implementations of SUBSTR do not permit negative values for the string index. However, if the application is implemented to call SUBSTR in a manner that is compatible with the DRDA Server, then the function will act the same in either Oracle or the DRDA Server.

Another consideration is that the processing of a function at the DRDA Server may not be desirable due to resource constraints in that environment. Refer to the DRDA_CAPABILITY parameter of Appendix C for details on enabling or disabling these capabilities. Refer as well, to the SQL*Plus User's Guide and Reference and Oracle Database PL/SQL User's Guide and Reference for the Oracle format of the following capabilities:

SQL Functions That Can Be Enabled

The following list contains SQL functions that are not enabled by default. They can be enabled as an option:

Table 12-5 List of SQL Functions That Can Be Enabled

Functions

ABS

ACOS

ASCII

ASIN

ATAN

ATAN2

BITAND

CAST

CEIL

CHR

CONVERT

COS

COSH

COUNTCOL

DECODE

DUMP

EXP

FLOOR

GREATEST

HEXOTRAW

INITCAP

INSTR

INSTRB

LEAST

LENGTH

LENGTHB

LN

LOG

LOWER

LPAD

LTRIM

MOD

NLS_INITCAP

NLS_UPPER

NLS_LOWER

NLSSORT

NVL2

POWER

RAWTOHEX

REPLACE

REVERSE

ROUND

RPAD

RTRIM

SIGN

SIN

SINH

SQRT

STDDEV

SUBSTR

SUBSTRB

TAN

TANH

TO_NUMBER

TRANSLATE

TRIM

TRUNC

UPPER

VARIANCE

VSIZE

SQL Functions That Can Be Disabled

The following SQL functions are enabled (ON) by default. They can be disabled as an option:

- COUNTCOL, to control SQL COUNT(column) function

- GROUPBY, to control SQL GROUP BY clause

- HAVING, to control SQL HAVING clause

- ORDERBY, to control SQL ORDER BY clause

- WHERE, to control SQL WHERE clause

ORDERBY controls sort order, which may differ at various sort locations. For example, with ORDERBY ON, a DB2 sort would be based on EBCDIC sorting order, whereas with ORDERBY OFF, an Oracle sort would be based on ASCII sorting order.

Three other functions, GROUPBY, HAVING, and WHERE, can take additional processing time. If you need to minimize the use of expensive resources, then you should choose the settings of these functions so that the processing is performed on the cheaper resource.

SQL Set Operators and Clauses

The clauses WHERE and HAVING are compatible for all versions of the DRDA Server, meaning that they are passed unchanged to the DRDA Server for processing. Whether clauses GROUP BY and ORDER BY are passed to the DRDA Server or compensated by the Oracle server is determined by the Native Semantics parameters (refer to the previous section).

The set operators UNION and UNION ALL are compatible for all versions of the DRDA Server, meaning that they are passed unchanged to the DRDA Server for processing. The set operators INTERSECT and MINUS are compensated on all versions of the DRDA Server except DB2/UDB. For DB2/UDB, INTERSECT is compatible, and MINUS is translated to EXCEPT.

DRDA Data Type to Oracle Data Type Conversion

To move data between applications and the database, the gateway binds data values from a host variable or literal of a specific data type to a data type interpretable by the database. Therefore, the gateway maps values from any version of the DRDA Server into correct Oracle data types before passing these values back to the application or Oracle tool.

The table lists the data type mapping and restrictions. The DRDA Server data types listed below are general. Refer to documentation for your DRDA database for restrictions on data type size and value limitations.

Table 12-6 Data Type Mapping and Restrictions

DRDA Server

Oracle External

Criteria

CHAR(N)

CHAR(N)

N < =  255

VARCHAR (N)

VARCHAR2(N)

LONG

N < = 2000

2000 < N < = 32740

LONG VARCHAR(N)

VARCHAR2(N)

N < = 2000

LONG VARCHAR(N)

LONG

2000 < N < = 32740

CHAR(N) FOR BIT DATA

RAW(N)

N < = 255

VARCHAR(N) FOR BIT DATA

RAW(N)

1  < =  N < =  255

VARCHAR(N) FOR BIT DATA

LONG RAW(N)

255 < N < =  32740

LONG VARCHAR(N) FOR BIT DATA

RAW(N

1  < =  N < =  255

LONG VARCHAR(N) FOR BIT DATA

LONG RAW(N)

255 < N < =  32740

DATE

DATE

Refer to "Performing Date and Time Operations"

TIME

CHAR(8)

Refer to "Performing Date and Time Operations"

TIMESTAMP

CHAR(26)

Refer to "Performing Date and Time Operations"

GRAPHIC

CHAR(2N)

N <= 127

VARGRAPHIC

VARCHAR2(2N)

LONG

N <= 1000

1000 <= N <= 16370

LONG VARGRAPHIC

VARCHAR2(2N)

LONG

N <= 1000

1000 <= N <= 16370

Floating Point Single

FLOAT(21)

n/a

Floating Point Double

FLOAT(53)

n/a

Decimal (P, S)

NUMBER(P,S)

n/a

Performing Character String Operations

The gateway performs all character string comparisons, concatenations, and sorts using the data type of the referenced columns, and determines the validity of character string values passed by applications using the gateway. The gateway automatically converts character strings from one data type to another and converts between character strings and dates when needed.

Frequently, DRDA databases are designed to hold noncharacter binary data in character columns. Applications run on DRDA systems can generally store and retrieve data as though it contained character data. However, when an application accessing this data runs in an environment that uses a different character set, inaccurate data might be returned.

With the gateway running on the host, character data retrieved from a DB2/400, DB2/OS390, or DB2/VM host is translated from EBCDIC to ASCII. When character data is sent to DB2/400, DB2/OS390, or DB2/VM from the host, ASCII data is translated to EBCDIC. When the characters are binary data in a character column, this translation causes the application to receive incorrect information or errors. To resolve these errors, character columns on DB2/400, DB2/OS390, or DB2/VM that hold noncharacter data must be created with the FOR BIT DATA option. In the application, the character columns holding noncharacter data should be processed using the Oracle data types RAW and LONG RAW. The DESCRIBE information for a character column defined with FOR BIT DATA on the host always indicates RAW or LONG RAW.

Converting Character String data types

The gateway binds character string data values from host variables as fixedElength character strings. The bind length is the length of the character string data value. The gateway performs this conversion on every bind.

The DRDA VARCHAR data type can be from 1 to 32740 bytes in length. This data type is converted to an Oracle VARCHAR2 data type if it is between 1 and 2000 characters in length. If it is between 2000 and 32740 characters in length, then it is converted to an Oracle LONG data type.

The DRDA VARCHAR data type can be no longer than 32740 bytes, which is much shorter than the maximum size for the Oracle LONG data type. If you define an Oracle LONG data type larger than 32740 bytes in length, then you will receive an error message when it is mapped to the DRDA VARCHAR data type.

Performing Graphic String Operations

DB2 GRAPHIC data types store only doubleEbyte string data. Sizes for DB2 GRAPHIC data types typically have maximum sizes which are half that of their character counterparts. For example, the maximum size of a CHAR data type may be 255 characters, whereas the maximum size of a GRAPHIC data type may be 127 characters.

Oracle does not have a direct matching data type, and the gateway therefore converts between Oracle character data types and DB2 Graphic data types. Oracle character data types may contain single, mixed, or doubleEbyte character data. The gateway converts the string data into suitable doubleEbyteEonly format depending upon whether the target DB2 column is a graphic type and whether gateway initialization parameters are set to perform this conversion. For more configuration information, refer to Appendix C, "DRDAESpecific Parameters" and Appendix D, "National Language Support".

Performing Date and Time Operations

The implementation of date and time data differs significantly in IBM DRDA databases and in the Oracle server. The Oracle server has a single date data type, DATE, that can contain both calendar date and time of day information.

IBM DRDA databases support the following three distinct date and time data types:

- DATE is the calendar date only.

- TIME is the time of day only.

- TIMESTAMP is a numerical value combining calendar data and time of day.

Processing TIME and TIMESTAMP Data

There is no builtEin mechanism that translates the IBM TIME and TIMESTAMP data to Oracle DATE data. An application must process TIME data types to the Oracle CHAR format with a length of eight bytes. An application must process the TIMESTAMP data type in the Oracle CHAR format with a length of 26 bytes.

An application reads TIME and TIMESTAMP functions as character strings and converts or subsets portions of the string to perform numerical operations. TIME and TIMESTAMP values can be sent to an IBM DRDA database as character literals or bind variables of the correct length and format.

Processing DATE Data

Oracle and IBM DATE data types are mapped to each other. If an IBM DATE is queried, then it is converted to an Oracle DATE with a zero (midnight) time of day. If an Oracle DATE is processed against an IBM DATE column, then the date value is converted to the IBM DATE format, and any time value is discarded.

Character representations of dates are different in Oracle format and IBM DRDA format. When an Oracle application SQL statement contains a date literal, or conveys a date using a character bind variable, the gateway must convert the date to an IBM DRDA-compatible format.

The gateway does not automatically recognize when a character value is going to be processed against an IBM DATE column. Applications are required to distinguish character date values by enclosing them with the Oracle TO_DATE function notation.

For example, if EMP is a synonym or view that accesses data on an IBM DRDA database, then instead of this SQL statement:

SELECT * FROM EMP WHERE HIREDATE = '03-MAR-81'

you must use:

SELECT * FROM EMP WHERE HIREDATE = TO_DATE('03-MAR-81')

In a programmatic interface program that uses a character bind variable for the qualifying date value, you must use this SQL statement:

SELECT * FROM EMP WHERE HIREDATE = TO_DATE(:1)

The above SQL notation does not affect SQL statement semantics when the statement is run against an Oracle table. The statement remains portable across Oracle and IBM DRDAEaccessed data stores.

The TO_DATE function is not required for dates in any of the following formats:

- YYYYEMMEDD (ISO/JIS)

- DD.MM.YYYY (European)

- MM/DD/YYYY (USA)

For example:

SELECT * FROM EMP WHERE HIREDATE = '1981-03-03'

The TO_DATE requirement also does not pertain to input bind variables that are in Oracle date 7Ebyte binary format. The gateway recognizes such values as dates.

Performing Date Arithmetic

The following forms of SQL expression generally do not work correctly with the gateway:

date + number

number + date

date - number

date1 - date2

The date and number addition and subtraction (date + number, number + date, date - number) forms are sent to the DRDA Server, where they are rejected. The supported servers do not permit number addition or subtraction with dates.

Because of differing interpretations of date subtraction in the supported servers, subtracting two dates (date1 - date2) gives results that vary by server.

Note:
Avoid date arithmetic expressions in all gateway SQL until date arithmetic problems are resolved.

Dates

Date handling has two categories, twoEdigit year dates, which are treated as occurring 50 years before or 50 years after the year 2000, and fourEdigit year dates, which are not ambiguous with regard to the year 2000. Oracle recommends that you set the Oracle Database 10g server and gateway default HS_NLS_DATE_FORMAT parameter to a format including a fourEdigit year.

Use one of the following methods to enter twentyEfirst century dates:

- The TO_DATE function
Use any date format including a four character year field. Refer to the Oracle Database SQL Reference for the available date format string options.

For example, TO_DATE('2008E07E23', 'YYYYEMMEDD') can be used in any SELECT, INSERT, UPDATE, or DELETE statement.

- The HS_NLS_DATE_FORMAT parameter
The HS_NLS_DATE_FORMAT parameter defines a default format for the Oracle database server explicit TO_DATE functions without a pattern and for implicit string to date conversions.

For example, with HS_NLS_DATE_FORMAT defined as 'YYYYEMMEDD,' '2008E07E23' can be used in any SELECT, INSERT, UPDATE, or DELETE statement.

HS_NLS_DATE_FORMAT Support

The following patterns can be used for the HS_NLS_DATE_FORMAT:

Table 12-7 HS_NLS_DATE_FORMAT Patterns

DB2 Date Format

Pattern

Example

EUR

DD.MM.YYYY

30.10.1994

ISO

YYYY-MM-DD

1994-10-30

JIS

YYYY-MM-DD

1994-10-30

USA

MM/DD/YYYY

10/30/1994

The Oracle default format of 'DDEMONEYY' is not permitted with DB2. As a result, the gateway local date exit is provided to change the Oracle default date format of 'DDEMONEYY' or 'DDEMONERR' to the DB2 ISO format of 'YYYYEMMEDD' before passing the date to DB2.

The following example demonstrates the most efficient way to enter and select date values in the twentyEfirst century:

ALTER SESSION SET HS_NLS_DATE_FORMAT = 'YYYY-MM-DD';
INSERT INTO EMP (HIREDATE) VALUES ('2008-07-23');
SELECT * FROM EMP WHERE HIREDATE = '2008-07-23';
UPDATE EMP SET HIREDATE = '2008-07-24'
WHERE HIREDATE = '2008-07-23';
DELETE FROM EMP WHERE HIREDATE = '2008-07-24';

Oracle TO_DATE Function

The Oracle TO_DATE function is preprocessed in SQL INSERT, UPDATE, DELETE, and SELECT WHERE clauses. TO_DATE functions in SELECT result lists are not preprocessed.

The TO_DATE function is often needed to provide values to update or compare with date columns. Therefore, the gateway replaces the information included in the TO_DATE clause with an acceptable value before the SQL statement is sent to DB2.

Except for the SELECT result list, all TO_DATE functions are preprocessed and turned into values that are the result of the TO_DATE function. Only TO_DATE(literal) or TO_DATE(:bind_variable) is permitted. Except in SELECT result lists, the TO_DATE(column_name) function format is not supported.

The preprocessing of the Oracle TO_DATE functions into simple values is useful in an INSERT VALUES clause because DB2 does not permit functions in the VALUES clause. In this case, DB2 receives a simple value in the VALUES list. All forms of the TO_DATE function (with one, two, or three operands) are supported.

Performing Numeric Data Type Operations

IBM versions of the DRDA Server perform automatic conversions to the numeric data type of the destination column (such as integer, doubleEprecision floating point, or decimal). The user has no control over the data type conversion, and this conversion can be independent of the data type of the destination column in the database.

For example, if PRICE is an integer column of the PRODUCT table in an IBM DRDA database, then the update shown in the following example inaccurately sets the price of an ice cream cone to $1.00 because the IBM DRDA Server automatically converts a floating point to an integer:

UPDATE PRODUCT
SET PRICE = 1.50
WHERE PRODUCT_NAME = 'ICE CREAM CONE    ';

Because PRICE is an integer, the IBM DRDA Server automatically converts the decimal data value of 1.50 to 1.

Mapping the COUNT Function

The Oracle Database server supports the following four operands for the COUNT function:

- COUNT(*)

- COUNT(DISTINCT colname)

- COUNT(ALL colname)

- COUNT(colname)

Some DRDA servers do not support all forms of COUNT, specifically COUNT(colname) and COUNT(ALL colname). In those cases, the COUNT function and its arguments are translated into COUNT(*). This may not yield the desired results, especially if the column being counted contains NULL values.

For those DRDA servers that do not support the above forms, it may be possible to achieve equivalent functionality by adding a WHERE clause.

SELECT COUNT(colname) FROM table@dblink WHERE colname IS NOT NULL

or

SELECT COUNT(ALL colname) FROM table@dblink WHERE colname IS NOT NULL

Refer to Chapter 2, "SQL Limitations" for known DRDA servers which do not support all forms of COUNT.

Performing Zoned Decimal Operations

A zoned decimal field is described as packed decimal on an Oracle server. However, an Oracle application such as a Pro*C program can insert into a zoned decimal column using any supported Oracle numeric data type. The gateway converts this number into the most suitable data type. Data can be fetched from a DRDA database into any Oracle data type, provided that it does not result in loss of information.

Passing Native SQL Statements through the Gateway

The passthrough SQL feature enables an application developer to send a SQL statement directly to the DRDA Server without the statement being interpreted by the Oracle database server. DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE SQL passthrough statements that are supported by the gateway are limited to nonqueries (INSERT, UPDATE, DELETE, and DDL statements) and cannot contain bind variables. The gateway can run native SQL statements using DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE.

DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE is a builtEin gateway function. This function receives one input argument and returns the number of rows affected by the SQL statement. For DDL statements, the function returns zero.

DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE is a reserved name of the gateway and is used specifically for running native SQL.

This release of Oracle Transparent Gateway for DRDA enables retrieval of result sets from queries run with passthrough. The syntax is different from the DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE function. Refer to "Retrieving Result Sets Through Passthrough" for more information.

Processing DDL Statements through Passthrough

As noted above, SQL statements which are processed through the DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE function are not interpreted by the Oracle database server. As a result, the Oracle database server will not know if such statements are making any modifications to the DRDA Server. This means that unless you keep the Oracle database's cached information up to date after changes to the DRDA Server, the database may continue to rely upon inaccurate or outdated information in subsequent queries within the same session.

An example of this occurs when you alter the structure of a table by either adding or removing a column. When an application references a table through the gateway (for example, when you perform a query on it), the Oracle database server caches the table definition. Now, suppose that (within the same session) the application subsequently alters the table's form, by using DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE to add a column. Then, the next reference to the table (by the application) will return the old column definitions of the table and will ignore the table's new column. This is because the Oracle database server did not process the statement and, so, has no knowledge of the alteration. Because the database does not know of the alteration, it has no reason to requery the table form, and, so, it will use the alreadyEcached form to handle any new queries.

In order for the Oracle database server to acquire the new form of the table, the existing session with the gateway must be closed and a new session must be opened. This can be accomplished in either of two ways:

- By ending the application session with the Oracle database server and starting a new session after modifications have been made to the DRDA Server; or

- By running the ALTER SESSION CLOSE DATABASE LINK command after making any modifications to the DRDA Server.

Either of the above actions will void the cached table definitions and will force the Oracle database server to acquire new definitions on the next reference.

Using the DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE Function

To run a passthrough SQL statement using DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE, use the following syntax:

number_of_rows = DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE@dblink ('native_DRDA_sql');

where:

number_of_rows is a variable that is assigned the number of rows that are affected by the passthrough SQL completion. For DDL statements, a zero is returned for the number of rows affected.

dblink is the name of the database link that is used to access the gateway.

native_DRDA_sql is a valid nonquery SQL statement (except CONNECT, COMMIT, and ROLLBACK). The statement cannot contain bind variables. Native SQL statements that cannot be dynamically prepared are rejected by the DRDA Server. The SQL statement that is passed by the DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE function must be a character string. For more information regarding valid SQL statements, refer to the SQL Reference for the particular DRDA Server.

Examples

1. Insert a row into a DB2 table using DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE:

DECLARE
num_rows integer;
BEGIN
num_rows:=DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE@dblink
('INSERT INTO SCOTT.DEPT VALUES (10,''PURCHASING'',''PHOENIX'')');
END
/

2. Create a table in DB2 using DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE:

DECLARE
num_rows integer;
BEGIN
num_rows:=DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE@dblink
('CREATE TABLE MYTABLE (COL1 INTEGER, COL2 INTEGER, COL3 CHAR(14),
COL4 VARCHAR(13))');
END;
/

Retrieving Result Sets Through Passthrough

Oracle Transparent Gateway for DRDA provides a facility to retrieve results sets from a SELECT SQL statement entered through passthrough.

Example

DECLARE
CRS binary_integer;
RET binary_integer;
VAL VARCHAR2(10)
BEGIN
CRS:=DBMS_HS_PASSTHROUGH.OPEN_CURSOR@gtwlink;
DBMS_HS_PASSTHROUGH.PARSE@gtwlink(CRS,'SELECT NAME FROM PT_TABLE');
RET:=0;
WHILE (TRUE)
LOOP
RET:=DBMS_HS_PASSTHROUGH.FETCH_ROW@gtwlink(CRS,FALSE);
DBMS_HS_PASSTHROUGH.GET_VALUE@gtwlink(CRS,1,VAL);
INSERT INTO PT_TABLE_LOCAL VALUES(VAL);
END LOOP;
EXCEPTION
WHEN NO_DATA_FOUND THEN
BEGIN
DBMS_OUTPUT.PUT_LINE('END OF FETCH');
DBMS_HS_PASSTHROUGH.CLOSE_CURSOR@gtwlink(CRS);
END;
END;
END;
/

Oracle Data Dictionary Emulation on a DRDA Server

The gateway optionally augments the DRDA database catalogs with data dictionary views modeled after the Oracle data dictionary. These views are based on the dictionary tables in the DRDA database, presenting that catalog information in views familiar to Oracle users. The views created during the installation of the gateway automatically limit the data dictionary information presented to each user based on the privileges of that user.

Using the Gateway Data Dictionary

The gateway data dictionary views provide users with an OracleElike interface to the contents and use of the DRDA database. Some of these views are required by Oracle products. The gateway supports the DB2/OS390, DB2/400, and DB2/UDB catalog views. DB2/VM catalog views are not available.

You can query the gateway data dictionary views to see the objects in the DRDA database and to determine the authorized users of the DRDA database. Many Oracle catalog views are supported by the Oracle Transparent Gateway for DRDA. Refer to Appendix A for descriptions of Oracle DB2 catalog views. These views are completely compatible with the gateway.

Using the DRDA Catalog

Each DRDA database has its own catalog tables and views, which you might find useful. Refer to IBM documentation for descriptions of these catalogs.

Defining the Number of DRDA Cursors

You can define any number of cursors depending on your application requirements. Oracle recommends that you use the default value of 100. However, if the default is not correct for your application, there are two points to consider when defining the number of cursors for your installation:

1. Each cursor requires an additional amount of storage and additional management.

2. If you change DRDA_PACKAGE_SECTIONS, then you must rebind the package.

The parameter DRDA_PACKAGE_SECTIONS is specific to the DRDA package. This parameter defines the number of sections (open cursors at the IBM database). For more information about setting the DRDA_PACKAGE_SECTIONS parameter, refer to Appendix C, "DRDAESpecific Parameters".

13 Security Considerations

The gateway architecture involves multiple computer systems that have distinct security capabilities and limitations. This chapter provides information for planning and implementing the security system.

This chapter includes the following sections:

- Security Overview

- Authenticating Application Logons

- Defining and Controlling Database Links

- TCP/IP Security

- Processing Inbound Connections

- Passwords in the Gateway Initialization File

Security Overview

When you connect several systems, generally, the system with the strictest security requirements dictates and rules the system.

Gateway security involves two groups:

- Users and applications that are permitted access to a given gateway instance and DRDA database server

- Server database objects that users and applications are able to query and update

You can control access in the gateway architecture at several points. Control over database object access is provided by each DRDA database server with GRANTs and related native authorization mechanisms based on user ID.

When the gateway is involved in a SQL request, security mechanisms are in effect for each DRDA system component encountered by the gateway. The first system component encountered is the application tool or 3GL program. The last system component encountered is the DRDA database.

Authenticating Application Logons

An application must connect to an Oracle integrating server before using the gateway. The type of logon authentication that you use determines the resulting Oracle user ID and can affect gateway operation. There are two basic types of authentication:

- Oracle authentication
With Oracle authentication, each Oracle user ID has a password known to the Oracle server. When an application connects to the server, it supplies a user ID and password. The Oracle server confirms that the user ID exists and that the password matches the one kept in the database.

- Operating system authentication
With operating system authentication, the server's underlying operating system is responsible for authentication. An Oracle user ID that is created with the IDENTIFIED EXTERNALLY attribute, instead of a password, is accessed with operating system authentication. To log in to such a user ID, the application supplies a slash ( / ) for a user ID and does not supply a password.

To perform operating system authentication, the server determines the requester's operating system user ID, optionally adds a fixed prefix to it, and uses the result as the Oracle user ID. The server confirms that the user ID exists and is identified externally, but no password checking is done. The underlying assumption is that users were authenticated when they logged in to the operating system.

Operating system authentication is not available on all platforms and is not available in some Oracle Net (client/server) and multithreaded server configurations. Refer to the Oracle Database Installation Guide for Microsoft Windows (32-Bit) and Oracle Net documentation to determine the availability of this feature in Microsoft Windows.

For more information about authenticating application logons, refer to the Oracle Database Reference.

Defining and Controlling Database Links

The information here is specific to the gateway. For additional information on database links, refer to the Oracle Database Administrator's Guide.

Link Accessibility

The first point of control for a database link is whether it is accessible to a given user. A public database link can be used by any user ID. A private database link is usable only by the user who created it. The server makes no distinction regarding the type of use (such as readEonly and update or write) or which remote objects can be accessed. These distinctions are the responsibility of the DRDA database that is accessed.

Links and CONNECT Clauses

The CONNECT clause is another securityErelated attribute of a database link. You can use the CONNECT clause to specify an explicit user ID and password, which can differ from the user's Oracle user ID and password. This CONNECT user ID and password combination is sent to the gateway when the database link connection is first opened. Depending on gateway options, the gateway might send that user ID and password to the DRDA Server for it to validate.

If a database link is created without a CONNECT clause, then the user's Oracle user ID and password are sent to the gateway when the connection is opened. If the user logs in to the Oracle integrating server with operating system authentication, then the gateway receives no user ID or password from the Oracle integrating server. In this case, user ID mapping facilities at the DRDA Server can be used to make such a connection possible if all users on the same Pentium-based host can use the same DRDA database user ID.

TCP/IP Security

TCP/IP does not have any additional configurable security mechanism. The gateway supports a validation mechanism which requires a user ID and a valid password. The security information is passed to the DRDA Server for validation. This type of validation is equivalent to the "SNA Security Option SECURITY=PROGRAM" or "SNA Security Option SECURITY=PROGRAM", which is discussed in Chapter 6, "Configuring Microsoft SNA Server or Host Integration Server" and Chapter 7, " Configuring IBM Communication Server". The difference between the two methods is that in the SNA configuration, the security validation is performed by the SNA network facilities, while in the TCP/IP configuration, the DRDA Server manually performs the validation.

Processing Inbound Connections

Current DRDA Servers provide options for manipulating the security conduct of an inbound (client) DRDA session request. Refer to IBM documentation for detailed information about the security options discussed in this section. Refer to the section, "Documentation Requirements", for a list of IBM documentation.

User ID Mapping

User ID mapping is the most useful DRDA Server security capability. User ID mapping refers to changing the user ID associated with an incoming DRDA request to some other user ID known to that server. This is a useful feature if your installation does not have a uniform user ID structure across all systems and databases.

DB2/OS390

The DB2 DDF Communication Database (CDB) stores inbound DRDA session security options. These tables, pertinent to inbound sessions, have a role in security processing:

- SYSIBM.LUNAMES table
The SYSIBM.LUNAMES table controls inbound security conduct on an SNA LU basis, affecting all DRDA connections from a particular host system. This table also controls whether inbound connection user IDs are subject to translation or mapping.

- SYSIBM.USERNAMES table
When translation is used, rows in the SYSIBM.USERNAMES table specify translated user IDs by LU name and inbound user ID. Default entries that pertain to all LUs and to all inbound user IDs can be made in both tables. The mapping table can also be used to indicate which inbound user IDs are permitted, from a particular LU or from all LUs, whether or not they are mapped.

This implementation provides a flexible mapping structure. You can specify that all connections from a particular LU use a single DB2 user ID, or that a particular inbound user ID always be mapped to a particular DB2 user ID regardless of origin. A USERNAMES entry with blank LU name and inbound user ID can designate a single default DB2 user ID for all connections unless a more specific entry, by LU name, user ID, or both, exists.

The CDB tables can be updated by a user with update authority using a SQL tool such as the DB2 SPUFI utility. For example, most database administrators, systems programmers, and security officers can update CDB tables. The DB2 DDF component must be stopped and restarted for CDB changes to take effect.

The DB2 nonEDRDAEspecific security features are also involved in DRDA connections. User IDs are subject to normal DB2 or SAF/RACF validation in addition to connection or signEon exit processing. Passwords are also subject to validation. Once the connection is established, all normal authorizations or GRANTs associated with the user ID are in effect. The user ID must have execute authority on the gateway DRDA package to process SQL statements.

DB2/VM

Under VM, DRDA sessions are managed by APPC VTAM Support (AVS), which runs as a disconnected GCS virtual machine. AVS receives incoming APPC connection requests (both DRDA and nonEDRDA) and routes the connection to a suitable server virtual machine.

AVS user ID mapping is controlled by internal AVS data structures that are updated with the AGW ADD USERID and AGW DELETE USERID commands.

A user ID mapping entry converts the inbound user ID before making the DB2/VM connection. The user ID mapping consists of:

- Originating LU name

- Inbound user ID

- The new user ID

You can create default entries that apply to any LU name and to any inbound user ID, and an entry can indicate that the inbound user ID is to be used without mapping.

AVS user ID mapping is functionally similar to the DB2 user ID translation mechanism and can be used to work around a variety of incongruities among user IDs on different systems and databases.

Once any indicated user ID mapping has been done, inbound DRDA connection requests are forwarded to the specified DB2/VM server system. DB2/VM confirms only if the user ID has CONNECT authority and, if so, that the connection is complete. At this point, the application's access to DB2/VM objects is controlled by the normal authorities and GRANTs for the connected user ID. The user ID must have execute authority on the gateway DRDA package to process SQL statements.

DB2/400

DB2/400 does not provide a user ID mapping capability comparable to that in DB2/OS390 and DB2/VM. Normally, the user ID in an incoming DRDA connection request must be a valid user ID on that AS/400 subsystem.

The AS/400 subsystem communications entry for the gateway should specify that the gateway is not a secure location and should include a default user ID of *NONE.

Once the application has completed the DRDA connection to the AS/400 subsystem, it is subject to all authorities and GRANTs associated with the user ID in use. The user ID must have execute authority on the gateway DRDA package to run SQL statements.

DB2/Universal Database

DB2/Universal Database (DB2/UDB) does not provide a user ID mapping capability comparable to that in DB2/OS390 and DB2/VM. Normally, the user ID in an incoming DRDA connection request must be a valid user ID on that host.

Once the gateway has completed the DRDA connection to the host, it is subject to all authorities and GRANTs associated with the user ID in use. The user ID must have execute authority on the gateway DRDA package to run SQL statements.

Passwords in the Gateway Initialization File

The gateway uses user IDs and passwords to access the information in the remote database on the DRDA Server. Some user IDs and passwords must be defined in the gateway initialization file to handle functions such as resource recovery. In today's security-conscious environment, having plainEtext passwords that are accessible in the Initialization File is deemed insecure. An encryption feature has been added as part of Hetergeneous Services' generic connectivity to help make this more secure. This feature is accessible by this gateway. With it initialization parameters which contain sensitive values might be stored in an encrypted form. Refer to the manual Oracle Database Heterogeneous Connectivity Administrator's Guide, Chapter 4, "Encrypting Initialization Parameters" for information about how to use the feature.

See Also:
The parameters DRDA_RECOVERY_USERID and DRDA_RECOVERY_PASSWORD in Appendix C as examples, for more information

14 Migration and Coexistence with Existing Gateways

Migration to new instances of Oracle Transparent Gateway for DRDA from an existing installation is straightforward, provided some guidelines are followed.

This chapter provides information that is specific to this release of the Oracle Transparent Gateway for DRDA and includes the following sections:

- Migrating Existing V4, V8, or V9 Gateway Instances to New Release

- Backout Considerations When Migrating to New Releases

- New and Changed Parameters When Migrating to Release 10

- DRDA Server Considerations

- Oracle Net Considerations

Migrating Existing V4, V8, or V9 Gateway Instances to New Release

Migration is the process of transforming an installed version of an Oracle database into a later version (compare this with upgrading). For example, transforming an Oracle8i database into an Oracle9i database is migrating the database. This transformation generally involves running the Oracle migrate (MIG) utility to modify Oracle database control file structures from the format of one version to the format of another version.

Upgrading is the process of transforming an Oracle database from an installed release into a later release of the same version. For example, transforming patch release 8.0.3 into patch release 8.0.4 is upgrading.

Step 1: Install the new Release

Install the new release of the gateway in a separate directory, as outlined in Chapter 4, "Installing the Gateway".

Caution:
Do not install the gateway over a previously existing Gateway installation. Doing so will corrupt the existing installation.

Step 2: Transferring initsid.gtwboot Gateway Boot Initialization parameters.

In previous releases, the gateway used two gateway initialization files (initsid.gtwboot and initsid.ora), or it used a Startup Shell Script (drdaDB2.sh) and one initialization file (initsid.ora). In this release, all parameters have been migrated into a single gateway initialization file, initsid.ora. Migrating a previous release involves copying the parameters from the initsid.gtwboot or Startup Shell Script into initsid.ora. The format of the parameters can be found in Appendix C, "DRDAESpecific Parameters".

Step 3: Transferring initsid.ora gateway initialization file parameters.

Copy the initsid.ora from the old Gateway instance to the new instance. The parameters in the initsid.ora gateway initialization file have changed format. Refer to "Gateway Initialization File Parameters" in Appendix C, "DRDAESpecific Parameters".

Backout Considerations When Migrating to New Releases

During the migration from older version 4, version 8, or version 9 gateway instances to the latest Oracle Database 10g release, if problems are encountered, then it is always possible to revert to the previous version. Assuming a working version 4 gateway instance exists, change the TNSNAMES.ORA entries from using the Oracle Database 10g gateway instance to the older version 4 instance. Remember to remove the "(HS=)" entry from the Oracle Net connect definition.

Oracle recommends that when you are installing a new release of the gateway and upgrading existing instances, you keep the old gateway home and instance configurations intact and operational, in case there are problems with the upgrade. This will help ensure minimal downtime between changes to different gateway instances.

New and Changed Parameters When Migrating to Release 10

This release of the Oracle Transparent Gateway for DRDA introduces new and changed initialization parameters if you are migrating from a version 4, version 8, or version 9 gateway to the Oracle Database 10g gateway.

New Parameters

The following section lists new parameters relevant to migration from version 4 gateways.

New Gateway Initialization File Parameters

Parameters introduced in this release of the gateway, listed in the following table, may be added to the gateway initialization file:

- DRDA_CACHE_TABLE_DESC

- DRDA_GRAPHIC_LIT_CHECK

- DRDA_GRAPHIC_PAD_SIZE

- DRDA_GRAPHIC_TO_MBCS

- DRDA_MBCS_TO_GRAPHIC

- DRDA_PROCDESC_STMT

- DRDA_PROCDESCPARMS_STMT

- DRDA_PROCCALL_MASK

- DRDA_FUNCDESC_STMT

- DRDA_FUNCDESCPARMS_STMT

- DRDA_FUNCCALL_MASK

- DRDA_GRAPHIC_CHAR_SIZE

Parameters That Have Been Changed in Usage

The usage of the following parameters has changed with version 9 of the gateway:

- DRDA_CONNECT_PARM

Parameters That Have Been Renamed

The following table presents a list of parameters that have been renamed with version 9 of the gateway, and their corresponding old names. Refer to Oracle Database Heterogeneous Connectivity Administrator's Guide for more detailed information about these parameters.

Table 14-1 Parameters That Have Been Renamed

New Name

Old Name

HS_COMMIT_STRENGTH_POINT

COMMIT_STRENGTH_POINT

HS_DB_DOMAIN

DB_DOMAIN

HS_DB_INTERNAL_NAME

DB_INTERNAL_NAME

HS_DB_NAME

DB_NAME

HS_DESCRIBE_CACHE_HWM

DESCRIBE_CACHE_HWM

HS_LANGUAGE

LANGUAGE

HS_NLS_DATE_FORMAT

NLS_DATE_FORMAT

HS_NLS_DATE_LANGUAGE

NLS_DATE_LANGUAGE

HS_OPEN_CURSORS

OPEN_CURSORS

HS_ROWID_CACHE_SIZE

ROWID_CACHE_SIZE

Obsolete Parameters

The following parameters are now obsolete. Please remove them from your configuration files:

- MODE

- SERVER_PATH

- DRDA_OVERRIDE_FROM_CODEPAGE

- DRDA_OVERRIDE_TO_CODEPAGE

- ERROR_LOGGING

- ERROR_REPORTING

- ERRORTAG

- GATEWAY_SID

- GROUP_BY_OFF

- GTWDEBUG

- INCREMENT_CURSORS

- DRDA_CALLDESC_STMT

- DRDA_CALLDESC_PROC

DRDA Server Considerations

Part of the normal installation for the gateway involves binding a package and (as an option) installing data dictionary views on the DRDA Server. This release of the gateway (10.2.0.1.0) is compatible with version 4, version 8, and version 9 packages that have been previously bound. The data dictionary views, however, have changed with this release. If you plan to use the data dictionary views that are provided by the gateway, then you must migrate to the new views. Oracle recommends that you install the new views as outlined in Chapter 10, "Configuring the Gateway". If you have changed certain DRDA parameters of the gateway initialization parameters as a result of the migration, then a rebind of the package will be required.

Oracle Net Considerations

The gateway uses the Heterogeneous Services (HS) facilities of Oracle and Oracle Net. As such, gateway service name entries in tnsnames.ora need a slight modification to tell Oracle Net that the gateway will be using the HS facilities. Refer to "Configuring Oracle Net" for detailed information.

15 Error Messages, Diagnosis, and Reporting

This chapter provides information about error messages and error codes. This chapter is specific to this release of the Oracle Transparent Gateway for DRDA, and it includes the following sections:

- Interpreting Gateway Error Messages

- Mapped Errors

- Gateway Error Codes

- SQL Tracing and the Gateway

Interpreting Gateway Error Messages

The gateway architecture involves a number of separate components. Any component might detect and report an error condition while processing SQL statements that refer to one or more DRDA database tables. This means that error situations can be complex, involving error codes and supporting data from multiple components. In all cases, however, the application ultimately receives a single Oracle error number or return code on which to act.

Because most gateway messages exceed the 70-character message area in the Oracle SQLCA, the programmatic interfaces and Oracle Call Interfaces that you use to access data through the gateway should use SQLGLM or OERHMS to view the entire text of messages. Refer to the programmer's guide to the Oracle precompilers for additional information about SQLGLM, and refer to the Oracle Call Interface Programmer's Guide for additional information about OERHMS.

Error conditions encountered when using the gateway can originate from many sources:

- Errors detected by the Oracle integrating server

- Errors detected by the gateway

- Errors detected in the DRDA software, either on the requestor or server side

- Communication errors

- Errors detected by the server database

Errors Detected by the Oracle Integrating Server

Errors detected by the Oracle integrating server are reported back to the application or tool with the standard ORA- type message. Refer to the Oracle Database Error Messages for descriptions of these errors. For example, the following error message occurs when an undefined database link name is specified:

ORA-02019:  connection description for remote database not found

Errors in the ORAE9100 to ORAE9199 range are reserved for the generic gateway layer (components of the gateway that are not specific to DRDA). Messages in this range are documented in Oracle Database Error Messages.

Errors Detected by the Gateway

Errors detected by the generic gateway are prefixed with HGO- and are documented in the Oracle Database Error Messages.

An example of an error message is:

HGOE00706:  HGO:  Missing equal sign for parameter in initialization file.

Errors Detected in the DRDA Software

Errors detected in the DRDA gateway, on the requestor or server side, are usually reported with error code ORAE28500, followed by a gatewayEspecific expanded error message. There are two return codes reported in the expanded message:

- drc specifies DRDAEspecific errors which are documented in "Gateway Error Codes".

- grc specifies generic gateway errors detected in the DRDA layer. These errors are documented in the Oracle Database Heterogeneous Connectivity Administrator's Guide.

Note:
Error code ORAE28500 was error code ORAE09100 prior to gateway version 8. Error code ORAE28501 was error code ORAE09101 prior to gateway version 8.

The values in parentheses that follow the drc values are used for debugging by Oracle Support Services. The errp field indicates the program (requestor or server) that detected the error. If errmc is present, it lists any error tokens.

For example, the following error message is returned when the database name specified (XNAME) with the DRDA_REMOTE_NAME parameter in the initsid.ora file is not defined at the DRDA Server:

ORA-28500: connection from ORACLE to a non-Oracle system returned the message:
TG4DRDA v10.2.0.1.0 grc=0, drc=-30061 (839C,0000), errp=GDJRFS2E
errmc=XNAME

Communication Errors

Communication errors are reported with an ORAE28501 followed by a gatewayEspecific expanded error message with drc=-30080 (SNA CPIEC error) or drc=-30081 (lost session). errmc indicates which CPIEC routine encounters the error, followed by the CPIEC error code and error number.

For example, the following error message is returned when there is a failure to establish a session because DRDA_CONNECT_PARM in the initsid.ora file specifies a Side Information Profile that is not defined:

ORA-28501:  Target system communication error.
TG4DRDA v10.2.0.1.0 grc=0, drc=-30081  (839C,0001), errp=GDJICRD
errmc=Initialize_Conversation (CMINIT)  24  0

Refer to the appropriate Microsoft Windows or IBM Communication Server documentation for more information.

Errors Detected by the Server Database

Errors detected by the server database are reported with an ORAE28500 Oracle Error followed by a gatewayEspecific expanded error message with drc=-777 (sqlcode follows). This is followed by another error message line that contains the sqlcode, sqlstate, errd (error array), and errmc (error tokens) returned from the DRDA Server database. Refer to IBM documentation for the specific database being used. Also refer to "Mapped Errors" for some SQL errors that get translated.

Note:
Error code ORAE28500 was error code ORAE09100 prior to gateway version 8. Error code ORAE28501 was error code ORAE09101 prior to gateway version 8.

For example, the following error message indicates that the DRDA Server database did not recognize the collection ID or package name specified with the DRDA_PACKAGE_COLLID or DRDA_PACKAGE_NAME parameters in the initsid.ora file:

ORA-28500:  Target system returned following message:
TG4DRDA v10.2.0.1.0 grc=0, drc=-777 (839C,0000), errp=DSNXEPM
sqlcode=-805, sqlstate=51002, errd=FFFFFF9C,0,0,FFFFFFFF,0,0
errmc=XB2V2R3..GSQL.A92617CB3FE5470DISTSERV

Mapped Errors

Some SQL errors are returned from the DRDA Server database and are translated to an Oracle error code. This is needed when the Oracle instance or gateway provides special handling of an error condition. The mapped sqlstate errors are:

Table 15-1 Mapped sqlstate Errors

Description

sqlstate error

Oracle error

No rows selected

02000

0

Unique index constraint violated

23505

ORA-00001

Object does not exist

52004 or 42704

ORA-00942

Object name too long (more than 18 characters), and therefore object does not exist

54003 or 42622

ORA-00942

Insufficient privileges

42501

ORA-01031

Invalid CCSID (unimplemented character set conversion)

22522

ORA-01460

Invalid user name/password; logon denied

N/A

ORA-01017

Divide by zero error

01519 or 01564

ORA-01476

The following is an example of a translated "object does not exist” error:

ORA-00942: table or view does not exist
TG4DRDA v10.2.0.1.0 grc=0, drc=-942 (839C,0001), errp=DSNXEDST
sqlcode=-204, sqlstate=52004, errd=32,0,0,FFFFFFFF,0,0
errmc=AJONES.CXDCX

Gateway Error Codes

Listed below are the common Oracle Transparent Gateway for DRDA error codesthat appear in the drc= field of the expanded error messages. If you get a drc value that does not appear here, contact Oracle Support Services.

-700 Invalid ORA_MAX_DATE specified

Cause: An invalid value was specified for ORA_MAX_DATE in the initsid.ora file.

Action: Correct the value of ORA_MAX_DATE. Correct format is ORA_MAX_DATE=YYYYEMMEDD, where MM is in the range of 1 to 12, and DD is in the range of 1 to 31 (and must be valid for the month).

-701 Default CCSID value not supported

Cause: The value specified for DRDA_DEFAULT_CCSID in the initsid.ora file is not supported by the Oracle Transparent Gateway for DRDA.

Action: Refer to Appendix D, "National Language Support", for a list of supported DRDA Server character sets.

-702 Application Host (bind) variable exceeds 32K

Cause: An application program specified a host variable with length greater than the DRDA permitted maximum of 32 K.

Action: The application must be modified to take into account DRDA limits.

-703 Local Character set not supported

Cause: The character set specified for the LANGUAGE parameter in the initsid.ora file is not supported.

Action: Refer to Appendix D, "National Language Support", for a list of supported character sets.

-704 User ID length greater than maximum

Cause: The user ID being used for the allocation of an APPC conversion by the gateway is longer than eight characters.

Action: A user ID of length of 8 or less must be used. Refer to Chapter 13, "Security Considerations", for a discussion of user IDs.

-705 Password length greater than maximum

Cause: The password being used for the allocation of an APPC conversion by the gateway is longer than eight characters.

Action: A password of length of 8 or less must be used. Refer to Chapter 13, "Security Considerations", for a discussion of passwords.

-777 DRDA Server RDBMS (SQL) Error

Cause: Server database detected an applicationElevel SQL error.

Action: Refer to "Interpreting Gateway Error Messages". sqlcode and sqlstate indicate host database error. Use this information to fix your application.

-30060 Invalid User ID/Password (DRDA Server RDBMS Authorization)

Cause: You have used a user ID/password that is not acceptable to the DRDA Server database.

Action: Refer to Chapter 13, "Security Considerations", for user ID/password considerations.

-30061 RDB not found

Cause: The remote database specified with the DRDA_REMOTE_DB_NAME parameter is not a valid database at the DRDA Server.

Action: Correct the value of the DRDA_REMOTE_DB_NAME parameter in the initsid.ora file.

-30080 Communication Error

Cause: The gateway encountered a CPIEC communication error.

Action: Retry processing that received error. If it persists, then refer to "Interpreting Gateway Error Messages" and report to your system administrator.

-30081 Communication Error - lost session

Cause: The current DRDA CPIEC session was disconnected.

Action: Retry processing that received error. If it persists, then refer to "Interpreting Gateway Error Messages" and report it to your system administrator.

SQL Tracing and the Gateway

When developing applications, it is often useful to be able to see the exact SQL statements that are being passed through the gateway. This section describes setting correct trace parameters and setting up the debug gateway.

SQL Tracing in the Oracle Database

The Oracle server has a command for capturing the SQL query which is actually sent to the gateway. This command is called EXPLAIN PLAN. EXPLAIN PLAN is used to determine the execution plan that Oracle follows to run a specified SQL statement. This command inserts a row (describing each step of the execution plan) into a specified table.

If you are using costEbased optimization, then this command also determines the cost of running the statement. The syntax of the command is:

EXPLAIN PLAN [ SET STATEMENT_ID = 'text' ]
[ INTO [schema.]table [@dblink] ] FOR statement

For detailed information on this command, refer to the Oracle Database SQL Reference.

Note:
In most cases, EXPLAIN PLAN should be sufficient to extract the SQL query which is actually sent to the gateway, and thus sent to the DRDA Server. However, certain SQL statement forms have postprocessing performed on them in the gateway. The next section will describe setting up SQL tracing in the gateway.

SQL Tracing in the Gateway

To enhance speed of the gateway, tracing was not built into the production gateway.

The product ships with a debug version of the gateway for the purposes of tracing and debugging applications.

This process entails changing the listener.ora file to use the debug gateway:

1. Log in as the Administrator user ID of the gateway and set up the environment.

2. Stop the Oracle Net Listener:

> lsnrctl stop

3. Edit the listener.ora with any text editor:

> notepad C:\Oracle\GTWHome\network\admin\listener.ora

4. Find the TNS entry for the gateway and change the program this way:

PROGRAM=g4drsrvd

5. Save the file and exit. Next, restart the Oracle Net Listener:

> lsnrctl start

6. Edit the gateway's initsid.ora file with any text editor:

> notepad C:\Oracle\GTWHome\tg4drda\admin\initsid.ora

7. Set the following parameters:

TRACE_LEVEL=255
ORACLE_DRDA_TCTL=debug.tctl

Note:
Refer to Appendix C, "DRDAESpecific Parameters" for descriptions of those parameters.

You may, as an option, add the LOG_DESTINATION parameter, but it is not required. If you specify a LOG_DESTINATION, then you may specify just the file name (for example, drda.trc), or you may specify a fully qualified path name. If you specify a LOG_DESTINATION with just the file name, then the log will be written to the log directory (ORACLE_HOME\tg4drda\trace) of the gateway. If you do not specify a LOG_DESTINATION, then a unique log file in a default format will be generated. The log file name will be of the form:

gatewaysid_tid.trc

Where:

gateway sid is the SID of the gateway.

tid is the thread identifier (TID) of the gateway service.

An example log file name would be:

drdahoa1_3875.trc

When searching for the SQL statements which are passed to the DRDA Server, look for the strings '*** HGAPARS ***' and '*** HGAXMSQL ***'. The string after HGAPARS will be the incoming statement from the Oracle Database 10g RDBMS. The string after HGAXMSQL will be the outgoing statement after any date substitution is done. This is the actual SQL statement which will be given to the DRDA Server.

When you have finished developing your application, revert the PROGRAM= value in the listener.ora file to its previous value and reload the listener to use the production gateway again. You should also comment out the trace parameters in the gateway initialization files.

A Oracle DB2 Data Dictionary Views

This appendix includes the Oracle Transparent Gateway for DRDA data dictionary views accessible to all users of an Oracle server. Most views can be accessed by any user with SELECT privileges for DB2 catalog tables.

N/A is used in the following tables to mean that the column is not valid for the gateway.

This appendix contains the following sections:

- Supported Views

- Data Dictionary View Tables

Supported Views

The following is a list of Oracle data dictionary views that are supported by the gateway for DB2/OS390, DB2/400, and DB2/UDB DRDA Servers. This release of the gateway does not have data dictionary view support for DB2/VM servers.

- ALL_CATALOG

- ALL_COL_COMMENTS

- ALL_CONS_COLUMNS

- ALL_CONSTRAINTS

- ALL_INDEXES

- ALL_IND_COLUMNS

- ALL_OBJECTS

- ALL_SYNONYMS

- ALL_TAB_COMMENTS

- ALL_TABLES

- ALL_TAB_COLUMNS

- ALL_USERS

- ALL_VIEWS

- COL_PRIVILEGES

- DICTIONARY

- DUAL

- TABLE_PRIVILEGES

- USER_CATALOG

- USER_COL_COMMENTS

- USER_CONSTRAINTS

- USER_CONS_COLUMNS

- USER_INDEXES

- USER_OBJECTS

- USER_SYNONYMS

- USER_TABLES

- USER_TAB_COLUMNS

- USER_TAB_COMMENTS

- USER_USERS

- USER_VIEWS

Data Dictionary View Tables

The remainder of this chapter contains tables describing data dictionary views. In the following descriptions, all are supported for DB2/OS390 and DB2/400.

ALL_CATALOG

All tables, views, synonyms, and sequences accessible to the user:

Column Name

Description

OWNER

Owner of the object

TABLE_NAME

Name of the object

TABLE_TYPE

Type of object

ALL_COL_COMMENTS

Comments on columns of accessible tables and views:

Column Name

Description

OWNER

Owner of the object

TABLE_NAME

Object name

COLUMN_NAME

Column name

COMMENTS

Comments on column

ALL_CONS_COLUMNS

Information about accessible columns in constraint definitions:

Column Name

Description

OWNER

Owner of the constraint definition

CONSTRAINT_NAME

Name associated with the constraint definition

TABLE_NAME

Name associated with table with constraint definition

COLUMN_NAME

Name associated with column specified in the constraint definition

POSITION

Original position of column in definition

ALL_CONSTRAINTS

Constraint definitions on accessible tables:

Column Name

Description

OWNER

Owner of the constraint definition

CONSTRAINT_NAME

Name associated with the constraint definition

CONSTRAINT_TYPE

Type of constraint definition

TABLE_NAME

Name associated with table with constraint definition

SEARCH_CONDITION

Text of search condition for table check

R_OWNER

Owner of table used in referential constraint

R_CONSTRAINT_NAME

Name of unique constraint definition for referenced table

DELETE_RULE

Delete rule for referential constraint

STATUS

Status of constraint

DEFERRABLE

Whether the constraint is deferrable

DEFERRED

Whether the constraint was initially deferred

VALIDATED

Whether all data obeys the constraint

GENERATED

Whether the name of the constraint is user or system generated

BAD

Constraint specifies a century in an ambiguous manner

RELY

Whether an enabled constraint is enforced or unenforced

LAST_CHANGE

When the constraint was last enabled or disabled

INDEX_OWNER

N/A

INDEX_NAME

N/A

ALL_INDEXES

Description of indexes on tables accessible to the user:

Column Name

Description

OWNER

Owner of the index

INDEX_NAME

Name of the index

INDEX_TYPE

Type of index

TABLE_OWNER

Owner of the indexed object

TABLE_NAME

Name of the indexed object

TABLE_TYPE

Type of the indexed object

UNIQUENESS

Uniqueness status of the index

COMPRESSION

N/A

PREFIX_LENGTH

0

TABLESPACE_NAME

Name of the tablespace containing the index

INI_TRANS

N/A

MAX_TRANS

N/A

INITIAL_EXTENT

N/A

NEXT_EXTENT

N/A

MIN_EXTENTS

N/A

MAX_EXTENTS

N/A

PCT_INCREASE

N/A

PCT_THRESHOLD

Threshold percentage of block space permitted per index entry

INCLUDE_COLUMN

Column ID of the last column to be included in index-organized table

FREELISTS

Number of process free lists allocated to this segment

FREELIST_GROUPS

Number of free list groups allocated to this segment

PCT_FREE

N/A

LOGGING

Logging information

BLEVEL

Depth of the index from its root block to its leaf blocks. A depth of 1 indicates that the root block and the leaf block are the same.

LEAF_BLOCKS

Number of leaf blocks in the index

DISTINCT_KEYS

Number of distinct indexed values. For indexes that enforce UNIQUE and PRIMARY KEY constraints, this value is the same as the number of rows in the table.

AVG_LEAF_BLOCKS_PER_KEY

N/A

AVG_DATA_BLOCKS_PER_KEY

N/A

CLUSTERING_FACTOR

N/A

STATUS

State of the index: VALID

NUM_ROWS

Number of rows in the index

SAMPLE_SIZE

Size of the sample used to analyze the index

LAST_ANALYZED

Date on which this index was most recently analyzed

DEGREE

Number of threads per instance for scanning the index

INSTANCES

Number of instances across which the index is to be scanned

PARTITIONED

Whether this index is partitioned

TEMPORARY

Whether the index is on a temporary table

GENERATED

Whether the name of the index is system generated

SECONDARY

N/A

BUFFER_POOL

Whether the index is a secondary object

USER_STATS

N/A

DURATION

N/A

PCT_DIRECT_ACCESS

N/A

ITYP_OWNER

N/A

ITYP_NAME

N/A

PARAMETERS

N/A

GLOBAL_STATS

N/A

DOMIDX_STATUS

N/A

DOMIDX_OPSTATUS

N/A

FUNCIDX_STATUS

N/A

JOIN_INDEX

N/A

IOT_REDUNDANT_PKEY_ELIM

N/A

ALL_IND_COLUMNS

ALL_IND_COLUMNS describes the columns of indexes on all tables that are accessible to the current user.

Column Names

Description

INDEX_OWNER

Owner of the index

INDEX_NAME

Name of the index

TABLE_OWNER

Owner of the table or cluster

TABLE_NAME

Name of the table or cluster

COLUMN_NAME

Column name or attribute of object type column

COLUMN_POSITION

Position of column or attribute within the index

COLUMN_LENGTH

Indexed length of the column

CHAR_LENGTH

Maximum code point length of the column

DESCEND

Whether the column is sorted in descending order (Y/N)

ALL_OBJECTS

Objects accessible to the user:

Column Name

Description

OWNER

Owner of the object

OBJECT_NAME

Name of object

SUBOBJECT_NAME

Name of the subobject

OBJECT_ID

Object number of the object

DATA_OBJECT_ID

Dictionary object number of the segment that contains the object

OBJECT_TYPE

Type of object

CREATED

N/A

LAST_DDL_TIME

N/A

TIMESTAMP

N/A

STATUS

State of the object

TEMPORARY

Whether the object is temporary

GENERATED

Was the name of this object system-generated?

SECONDARY

N/A

ALL_SYNONYMS

All synonyms accessible to the user:

Column Name

Description

OWNER

Owner of the synonym

SYNONYM_NAME

Name of the synonym

TABLE_OWNER

Owner of the object referenced by the synonym

TABLE_NAME

Name of the object referenced by the synonym

DB_LINK

N/A

ALL_TABLES

Description of tables accessible to the user:

Column Name

Description

OWNER

Owner of the table

TABLE_NAME

Name of the table

TABLESPACE_NAME

Name of the tablespace containing the table

CLUSTER_NAME

N/A

IOT_NAME

Name of the index-organized table

PCT_FREE

N/A

PCT_USED

N/A

INI_TRANS

N/A

MAX_TRANS

N/A

INITIAL_EXTENT

N/A

NEXT_EXTENT

N/A

MIN_EXTENTS

N/A

MAX_EXTENTS

N/A

PCT_INCREASE

N/A

FREELISTS

Number of process free lists allocated to this segment

FREELIST_GROUPS

Number of free list groups allocated to this segment

LOGGING

Logging attribute

BACKED_UP

N/A

NUM_ROWS

Number of rows in the table

BLOCKS

N/A

EMPTY_BLOCKS

N/A

AVG_SPACE

N/A

CHAIN_CNT

N/A

AVG_ROW_LEN

Average length of a row in the table in bytes

AVG_SPACE_FREELIST_BLOCKS

The average free space of all blocks on a free list

NUM_FREELIST_BLOCKS

The number of blocks on the free list

DEGREE

The number of threads per instance for scanning the table

INSTANCES

The number of instances across which the table is to be scanned

CACHE

Whether the cluster is to be cached in the buffer cache

TABLE_LOCK

Whether table locking is enabled or disabled

SAMPLE_SIZE

Sample size used in analyzing this table

LAST_ANALYZED

Date on which this table was most recently analyzed

PARTITIONED

Indicates whether this table is partitioned

IOT_TYPE

Whether this is an index-organized table

TEMPORARY

Can the current session only see data that it placed in this object itself?

SECONDARY

N/A

NESTED

Whether the table is a nested table

BUFFER_POOL

The default buffer pool for the object

ROW_MOVEMENT

N/A

GLOBAL_STATS

N/A

USER_STATS

N/A

DURATION

N/A

SKIP_CORRUPT

N/A

MONITORING

N/A

CLUSTER_OWNER

N/A

DEPENDENCIES

N/A

COMPRESSION

N/A

ALL_TAB_COLUMNS

Columns of all tables, views, and clusters accessible to the user:

Column Name

Description

OWNER

Owner of the table or view

TABLE_NAME

Table or view name

COLUMN_NAME

Column name

DATA_TYPE

Data type of column

DATA_TYPE_MOD

Data type modifier of the column

DATA_TYPE_OWNER

Owner of the data type of the column

DATA_LENGTH

Maximum length of the column in bytes

DATA_PRECISION

N/A

DATA_SCALE

Digits to the right of decimal point in a number

NULLABLE

Does the column permit nulls? Value is n if there is a NOT NULL constraint on the column or if the column is part of a PRIMARY key.

COLUMN_ID

Sequence number of the column as created

DEFAULT_LENGTH

N/A

DATA_DEFAULT

N/A

NUM_DISTINCT

Number of distinct values in each column of the table

LOW_VALUE

For tables with more than three rows, the second lowest and second highest values. These statistics are expressed in hexadecimal notation for the internal representation of the first 32 bytes of the values.

HIGH_VALUE

N/A

DENSITY

N/A

NUM_NULLS

The number of nulls in the column

NUM_BUCKETS

The number of buckets in histogram for the column

LAST_ANALYZED

The date on which this column was most recently analyzed

SAMPLE_SIZE

The sample size used in analyzing this column

CHARACTER_SET_NAME

The name of the character set

CHAR_COL_DECL_LENGTH

The length of the character set

GLOBAL_STATS

N/A

USER_STATS

N/A

AVG_COL_LEN

Average length of the column (in bytes)

CHAR_LENGTH

Displays the length of the column in characters

CHAR_USED

N/A

ALL_TAB_COMMENTS

Comments on tables and views accessible to the user:

Column Name

Description

OWNER

Owner of the object

TABLE_NAME

Name of the object

TABLE_TYPE

Type of object

COMMENTS

Comments on the object

ALL_USERS

Information about all users of the database:

Column Name

Description

USERNAME

Name of the user

USER_ID

N/A

CREATED

N/A

ALL_VIEWS

Text of views accessible to the user:

Column Name

Description

OWNER

Owner of the view

VIEW_NAME

Name of the view

TEXT_LENGTH

Length of the view text

TEXT

View text. Only the first row of text is returned, even if multiple rows exist.

TYPE_TEXT_LENGTH

Length of the type clause of the typed view

TYPE_TEXT

Type clause of the typed view

OID_TEXT_LENGTH

Length of the WITH OID clause of the typed view

OID_TEXT

WITH OID clause of the typed view

VIEW_TYPE_OWNER

Owner of the type of the view if the view is a typed view

VIEW_TYPE

Type of the view if the view is a typed view

SUPERVIEW_NAME

N/A

COLUMN_PRIVILEGES

Grants on columns for which the user is the grantor, grantee, or owner, or PUBLIC is the grantee:

Column Name

Description

GRANTEE

Name of the user to whom access was granted

OWNER

Username of the object's owner

TABLE_NAME

Name of the object

COLUMN_NAME

Name of the column

GRANTOR

Name of the user who performed the grant

INSERT_PRIV

Permission to insert into the column

UPDATE_PRIV

Permission to update the column

REFERENCES_PRIV

Permission to reference the column

CREATED

Timestamp for the grant

DICTIONARY

List or data dictionary tables:

Column Name

Description

TABLE_NAME

Table name

COMMENTS

Description of table

DUAL

Column Name

Description

DUMMY

A dummy column

TABLE_PRIVILEGES

Grants on objects for which the user is the grantor, grantee, or owner, or PUBLIC is the grantee:

Column Name

Description

GRANTEE

Name of the user to whom access is granted

OWNER

Owner of the object

TABLE_NAME

Name of the object

GRANTOR

Name of the user who performed the grant

SELECT_PRIV

Permission to select from an object

INSERT_PRIV

Permission to insert into an object

DELETE_PRIV

Permission to delete from an object

UPDATE_PRIV

Permission to update an object

REFERENCES_PRIV

N/A

ALTER_PRIV

Permission to alter an object

INDEX_PRIV

Permission to create or drop an index on an object

CREATED

Timestamp for the grant

USER_CATALOG

Tables, views, synonyms, and sequences owned by the use:

Column Name

Description

TABLE_NAME

Name of the object

TABLE_TYPE

Type of object

USER_COL_COMMENTS

Comments on columns of user's tables and views:

Column Name

Description

TABLE_NAME

Object name

COLUMN_NAME

Column name

COMMENTS

Comments on column

USER_CONSTRAINTS

Constraint definitions on user's tables:

Column Name

Description

OWNER

Owner of the constraint definition

CONSTRAINT_NAME

Name associated with the constraint definition

CONSTRAINT_TYPE

Type of constraint definition

TABLE_NAME

Name associated with table with constraint definition

SEARCH_CONDITION

Text of search condition for table check

R_OWNER

Owner of table used in referential constraint

R_CONSTRAINT_NAME

Name of unique constraint definition for referenced table

DELETE_RULE

Delete rule for referential constraint

STATUS

Status of constraint

DEFERRABLE

Whether the constraint is deferrable

DEFERRED

Whether the constraint was initially deferred

VALIDATED

Whether all data obeys the constraint

GENERATED

Whether the name of the constraint is user or system generated

BAD

Constraint specifies a century in an ambiguous manner

LAST_CHANGE

When the constraint was las enabled or disabled

INDEX_OWNER

N/A

INDEX_NAME

N/A

USER_CONS_COLUMNS

Information about columns in constraint definitions owned by the user:

Column Name

Description

OWNER

Owner of the constraint definition

CONSTRAINT_NAME

Name associated with the constraint definition

TABLE_NAME

Name associated with table with constraint definition

COLUMN_NAME

Name associated with column specified in the constraint definition

POSITION

Original position of column in definition

USER_INDEXES

Description of the user's own indexes:

Column Name

Description

INDEX_NAME

Name of the index

INDEX_TYPE

Type of index

TABLE_OWNER

Owner of the indexed object

TABLE_NAME

Name of the indexed object

TABLE_TYPE

Type of the indexed object

UNIQUENESS

Uniqueness status of the index

COMPRESSION

N/A

PREFIX_LENGTH

0

TABLESPACE_NAME

Name of the tablespace containing the index

INI_TRANS

N/A

MAX_TRANS

N/A

INITIAL_EXTENT

N/A

NEXT_EXTENT

N/A

MIN_EXTENTS

N/A

MAX_EXTENTS

N/A

PCT_INCREASE

N/A

PCT_THRESHOLD

Threshold percentage of block space permitted per index entry

INCLUDE_COLUMN

Column ID of the last column to be included in index-organized table

FREELISTS

Number of process freelists allocated to this segment

FREELIST_GROUPS

Number of freelist groups allocated to this segment

PCT_FREE

N/A

LOGGING

Logging information

BLEVEL

Depth of the index from its root block to its leaf blocks. A depth of 1 indicates that the root and leaf block are the same.

LEAF_BLOCKS

Number of leaf blocks in the index

DISTINCT_KEYS

Number of distinct indexed values. For indexes that enforce UNIQUE and PRIMARY KEY constraints, this value is the same as the number of rows in the table.

AVG_LEAF_BLOCKS_PER_KEY

N/A

AVG_DATA_BLOCKS_PER_KEY

N/A

CLUSTERING_FACTOR

N/A

STATUS

State of the indexes: VALID

NUM_ROWS

Number of rows in the index

SAMPLE_SIZE

Size of the sample used to analyze the index

LAST_ANALYZED

Date on which this index was most recently analyzed

DEGREE

Number of threads per instance for scanning the index

INSTANCES

Number of instances across which the index is to be scanned

PARTITIONED

Whether this index is partitioned

TEMPORARY

Whether the index is on a temporary table

GENERATED

Whether the name of the index is system generated

SECONDARY

N/A

BUFFER_POOL

Whether the index is a secondary object

USER_STATS

N/A

DURATION

N/A

PCT_DIRECT_ACCESS

N/A

ITYP_OWNER

N/A

ITYP_NAME

N/A

PARAMETERS

N/A

GLOBAL_STATS

N/A

DOMIDX_STATUS

N/A

DOMIDX_OPSTATUS

N/A

FUNCIDX_STATUS

N/A

JOIN_INDEX

N/A

IOT_REDUNDANT_PKEY_ELIM

N/A

USER_OBJECTS

Objects owned by the user:

Column Name

Description

OBJECT_NAME

Name of object

SUBOBJECT_NAME

Name of the subobject

OBJECT_ID

Object number of the object

DATA_OBJECT_ID

Dictionary object number of the segment that contains the object

OBJECT_TYPE

Type of object

CREATED

N/A

LAST_DDL_TIME

N/A

TIMESTAMP

N/A

STATUS

State of the object: VALID

TEMPORARY

Whether the object is temporary

GENERATED

Was the name of this object system generated?

SECONDARY

N/A

USER_SYNONYMS

The user's private synonyms:

Column Name

Description

SYNONYM_NAME

Name of the synonym

TABLE_OWNER

Owner of the object referenced by the synonym

TABLE_NAME

Name of the object referenced by the synonym

DB_LINK

N/A

USER_TABLES

Description of the user's own tables:

Column Name

Description

TABLE_NAME

Name of the table

TABLESPACE_NAME

Name of the tablespace containing the table

CLUSTER_NAME

N/A

IOT_NAME

Name of the index organized table

PCT_FREE

N/A

PCT_USED

N/A

INI_TRANS

N/A

MAX_TRANS

N/A

INITIAL_EXTENT

N/A

NEXT_EXTENT

N/A

MIN_EXTENTS

N/A

MAX_EXTENTS

N/A

PCT_INCREASE

N/A

FREELISTS

Number of process freelists allocated to this segment

FREELIST_GROUPS

Number of freelist groups allocated to this segment

LOGGING

Logging information

BACKED_UP

N/A

NUM_ROWS

Number of rows in the table

BLOCKS

N/A

EMPTY_BLOCKS

N/A

AVG_SPACE

N/A

CHAIN_CNT

N/A

AVG_ROW_LEN

Average length of a row in the table in bytes

AVG_SPACE_FREELIST_BLOCKS

The average freespace of all blocks on a freelist

NUM_FREELIST_BLOCKS

The number of blocks on the freelist

DEGREE

The number of threads per instance for scanning the table

INSTANCES

The number of instances across which the table is to be scanned

CACHE

Whether the cluster is to be cached in the buffer cache

TABLE_LOCK

Whether table locking is enabled or disabled

SAMPLE_SIZE

Sample size used in analyzing this table

LAST_ANALYZED

Date on which this table was most recently analyzed

PARTITIONED

Indicates whether this table is partitioned

IOT_TYPE

If this is an index organized table

TEMPORARY

Can the current session only see data that it placed in this object itself?

SECONDARY

N/A

NESTED

If the table is a nested table

BUFFER_POOL

The default buffer pool for the object

ROW_MOVEMENT

N/A

GLOBAL_STATS

N/A

USER_STATS

N/A

DURATION

N/A

SKIP_CORRUPT

N/A

MONITORING

N/A

CLUSTER_OWNER

N/A

DEPENDENCIES

N/A

COMPRESSION

N/A

USER_TAB_COLUMNS

Columns of user's tables, views, and clusters:

Column Name

Description

TABLE_NAME

Table, view, or cluster name

COLUMN_NAME

Column name

DATA_TYPE

data type of column

DATA_TYPE_MOD

data type modifier of the column

DATA_TYPE_OWNER

Owner of the data type of the column

DATA_LENGTH

Maximum length of the column in bytes

DATA_PRECISION

N/A

DATA_SCALE

Digits to the right of decimal point in a number

NULLABLE

Does the column permit nulls? Value is n if there is a NOT NULL constraint on the column or if the column is part of a PRIMARY key.

COLUMN_ID

Sequence number of the column as created

DEFAULT_LENGTH

N/A

DATA_DEFAULT

N/A

NUM_DISTINCT

Number of distinct values in each column of the table

LOW_VALUE

For tables with more than three rows, the second lowest and second highest values. These statistics are expressed in hexadecimal notation for the internal representation of the first 32 bytes of the values.

HIGH_VALUE

N/A

DENSITY

N/A

NUM_NULLS

The number of nulls in the column

NUM_BUCKETS

The number of buckets in histogram for the column

LAST_ANALYZED

The date on which this column was most recently analyzed

SAMPLE_SIZE

The sample size used in analyzing this column

CHARACTER_SET_NAME

The name of the character set

CHAR_COL_DECL_LENGTH

The length of the character set

GLOBAL_STATS

N/A

USER_STATS

N/A

AVG_COL_LEN

Average length of the column (in bytes)

CHAR_LENGTH

Displays the length of the column in characters

CHAR_USED

N/A

USER_TAB_COMMENTS

Comments on the tables and views owned by the user:

Column Name

Description

TABLE_NAME

Name of the object

TABLE_TYPE

Type of object

COMMENTS

Comments on the object

USER_USERS

Information about the current user:

Column Name

Description

USERNAME

Name of the user

USER_ID

N/A

ACCOUNT_STATUS

Indicates if the account is locked, expired or unlocked

LOCK_DATE

Date the account was locked

EXPIRE_DATE

Date of expiration of the account

DEFAULT_TABLESPACE

N/A

TEMPORARY_TABLESPACE

N/A

CREATED

N/A

EXTERNAL_NAME

User external name

USER_VIEWS

Text of views owned by the user:

Column Name

Description

VIEW_NAME

Name of the view

TEXT_LENGTH

Length of the view text

TEXT

First line of the view text

TYPE_TEXT_LENGTH

Length of the type clause of the typed view

TYPE_TEXT

Type clause of the typed view

OID_TEXT_LENGTH

Length of the WITH OID clause of the typed view

OID_TEXT

WITH OID clause of the typed view

VIEW_TYPE_OWNER

Owner of the type of the view if the view is a typed view

VIEW_TYPE

Type of the view if the view is a typed view

SUPERVIEW_NAME

N/A

B Sample Files

This appendix contains sample files of gateway initialization and Oracle Net tnsnames.ora and listener.ora files.

- Sample gateway initialization file

- Sample Oracle Net tnsnames.ora File

- Sample Oracle Net listener.ora File

Sample gateway initialization file

The following sample gateway initialization file (inithoa1.ora) needs customization. For information on customizing this file, refer to "Configuring the Host" in Chapter 10, "Configuring the Gateway". Also, refer to Appendix C.

#
# HS specific parameters
#
FDS_CLASS=TG4DRDA_DB2MVS
#TRACE_LEVEL=255
#LOG_DESTINATION=DB2.log
#ORACLE_DRDA_TCTL=debug.tctl
HS_COMMIT_POINT_STRENGTH=255
HS_NLS_DATE_FORMAT=YYYY-MM-DD
HS_LANGUAGE=AMERICAN_AMERICA.WE8ISO8859P1
HS_RPC_FETCH_REBLOCKING=off
HS_RPC_FETCH_SIZE=32767
HS_FDS_FETCH_ROWS=20
#
# DRDA specific parameters
#
DRDA_CONNECT_PARM=DRDACON1
DRDA_REMOTE_DB_NAME=DB2V7R1
DRDA_PACKAGE_COLLID=ORACLE
DRDA_PACKAGE_NAME=G2DRSQL
DRDA_PACKAGE_CONSTOKEN=A92617CB3FE54701
DRDA_RECOVERY_USERID=ORADRDA
DRDA_RECOVERY_PASSWORD=ORADRDA
DRDA_ISOLATION_LEVEL=CS
#DRDA_PACKAGE_OWNER=ORADRDA
#DRDA_DISABLE_CALL=TRUE

Sample Oracle Net tnsnames.ora File

For information on tailoring the tnsnames.ora file for the gateway, refer to the instructions for "Configuring Oracle Net".

ipc-ora=(DESCRIPTION=
(ADDRESS=
(PROTOCOL=IPC)
(KEY=ORCL)
)
(CONNECT_DATA=(SID=ORA102))
(HS=)
)
ipc-gw=(DESCRIPTION=
(ADDRESS=
(PROTOCOL=IPC)
(KEY=ORCL)
)
(CONNECT_DATA=(SID=drdahoa1))
(HS=)

)

Sample Oracle Net listener.ora File

For information on tailoring the listener.ora file for the gateway, refer to the instructions in "Configuring Oracle Net".

#
# Sample listener.ora file for the Transparent Gateway for IBM DRDA
# Version Date: Jan-01-2002
# Filename: Listener.ora
#
LISTENER =
(ADDRESS_LIST =
(ADDRESS= (PROTOCOL= IPC)(KEY= ORCL))
)

SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC=
(SID_NAME=drdahoa1)
(ORACLE_HOME=C:\Oracle\GTWHome)
(PROGRAM=g4drsrv)
)
)

STARTUP_WAIT_TIME_LISTENER = 0
INBOUND_CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = OFF

This sample listener.ora file resides in the ORACLE_HOME\network\admin directory. If the listener uses the Oracle Net TCP/IP adapter instead of the IPC adapter, then replace these lines under the LISTENER keyword:

(ADDRESS=
(PROTOCOL=IPC)
(KEY=ORCL)
)
with
(ADDRESS=
(PROTOCOL=TCP)
(HOST=your_IP_node_name)
(PORT=your_port_number)
)

C DRDAESpecific Parameters

This appendix contains the DRDAEspecific parameters defined in the gateway initialization file. Read and understand the information on each parameter, taking special note of parameters that have defaults that do not apply to your system.

This appendix contains the following sections:

- Modifying the Gateway Initialization File

- Setting Parameters in the Gateway Initialization File

- Syntax and Usage

- Gateway Initialization File Parameters

Modifying the Gateway Initialization File

If you change any parameters in the gateway initialization file, then you must stop and restart the gateway in order for them to take effect. If you change certain parameters, then you must also rebind the DRDA package. Any parameters that affect the DRDA package have a note in their description that rebinding is required.

Setting Parameters in the Gateway Initialization File

Parameters specific to the gateway are stored in the gateway initialization file, initsid.ora.

Syntax and Usage

Parameters and their values are specified according to the syntax rules put forth by heterogeneous services. The general form is:

[set] [private] drda_parameter = drda_parameter_value

where:

- drda_parameter is one of the DRDA parameters

- drda_parameter_value is a character string with contents dependent on the drda_parameter

The set and private keywords are optional and have the following effect. If the set keyword is present, then the parameter and its value will be pushed into the process environment. If the private keyword is present, then the parameter and its value will not be uploaded to the Oracle server. In general, Oracle recommends that the private keyword not be used unless the parameter contains sensitive information (a user ID or password, for example).

For further information on heterogeneous services and initialization parameters, see the section "Setting Initialization Parameters" in the Oracle Database Heterogeneous Connectivity Administrator's Guide.

Gateway Initialization File Parameters

Following is a list of gatewayEspecific initialization file parameters and their descriptions. In addition to these parameters, generic Heterogeneous Services initialization file parameters may be set. Refer to the Oracle Database Heterogeneous Connectivity Administrator's Guide for a list of additional parameters.

DRDA_CACHE_TABLE_DESC

Default value: TRUE

Range of values: {TRUE│FALSE}

Syntax: DRDA_CACHE_TABLE_DESC={TRUE│FALSE}

DRDA_CACHE_TABLE_DESC directs the gateway to cache table descriptions once per transaction. This can reduce the number of table lookups requested of the DRDA Server by Oracle and can speed up processing of SQL statements. You may wish to turn this option off if you will be altering the structure of a remote table and if you will be examining it within the same transaction.

DRDA_CAPABILITY

Default value: none

Range of values: Refer to Native Semantics

Syntax: DRDA_CAPABILITY={FUNCTION/{ON│OFF}},...

DRDA_CAPABILITY specifies which Oracle mapped functions will be treated natively. In other words, no special preprocessing or postprocessing will be done for these functions. They will be passed to the DRDA Server unmodified.

DRDA_CODEPAGE_MAP

Default value: codepage.map

Range of values: any valid file path

Syntax: DRDA_CODEPAGE_MAP=codepage.map

DRDA_CODEPAGE_MAP specifies the location of the codepage map. You may specify only the file name, which will be searched for within the ORACLE_HOME\tg4drda\admin directory, or you may specify the full path name of the file.

DRDA_COMM_BUFLEN

Default value: 32767

Range of values: 512 through 32767

Syntax: DRDA_COMM_BUFLEN=num

DRDA_COMM_BUFLEN specifies the communications buffer length. This is a number indicating the size of the SNA send/receive buffer in bytes.

DRDA_CONNECT_PARM (SNA format)

Default value: DRDACON1

Range of values: any alphanumeric string 1 to 8 characters in length

Syntax: RDA_CONNECT_PARM=name

DRDA_CONNECT_PARM specifies the Side Information name. Refer to Chapter 6, "Configuring Microsoft SNA Server or Host Integration Server" and Chapter 7, " Configuring IBM Communication Server" for details.

DRDA_CONNECT_PARM (TCP/IP format)

Default value: DRDACON1:446

Range of values: Any alphanumeric string 1 to 255 characters in length

Syntax: DRDA_CONNECT_PARM={hostname│ip_address}{:port}

DRDA_CONNECT_PARM specifies the TCP/IP host name or IP Address of the DRDA Server and, as an option, the Service Port number on which the DRDA Server is listening. For more information about the port number, refer to "Port Number".

DRDA_CMSRC_CM_IMMEDIATE

Default value: FALSE

Range of values: {TRUE │FALSE}

Syntax: DRDA_CMSRC_CM_IMMEDIATE={TRUE│FALSE}

DRDA_CMSRC_CM_IMMEDIATE sets the SNA session allocation mode. A setting of FALSE will cause the gateway to wait for a free session if no free sessions exist. A setting of TRUE will cause the gateway to fail the allocation immediately if no free sessions exist.

DRDA_DEFAULT_CCSID

Default value: none

Range of values: any supported DRDA Server CCSID

Syntax: DRDA_DEFAULT_CCSID=ccsid

DRDA_DEFAULT_CCSID specifies the default CCSID or character set code page for character set conversions when the DRDA Server database indicates that a character string has a CCSID of 65535. DRDA Servers use CCSID 65535 for columns specified as "FOR BIT DATA". In most cases, this parameter should not be specified, permitting CCSID 65535 to be treated as an Oracle RAW data type.

This parameter is for supporting databases (in particular, DB2/400) that use CCSID 65535 as the default for all tables created. Permitting CCSID 65535 to be treated as another CCSID can save such sites from having to modify every table.

WARNING:

Specifying any value for DRDA_DEFAULT_CCSID causes all "FOR BIT DATA" columns to be handled as text columns that need character set conversion and, therefore, any truly binary data in these columns can encounter conversion errors (ORAE28527).

DRDA_DESCRIBE_TABLE

Default value: TRUE

Range of values: {TRUE│FALSE}

Syntax: DRDA_DESCRIBE_TABLE={TRUE│FALSE}

DRDA_DESCRIBE_TABLE directs the gateway to use the DRDA operation "Table Describe" to return the description of tables. This is an optimization that reduces the amount of time and resources that are used to look up the definition of a table.

Note:
This feature is not compatible with DB2 aliases or Synonyms. If you will be using DB2 aliases, then be sure this option is not enabled.

DRDA_DISABLE_CALL

Default value: TRUE

Range of values: {TRUE│FALSE}

Syntax: DRDA_DISABLE_CALL={TRUE│FALSE}

DRDA_DISABLE_CALL controls stored procedure usage, and it is also used to control how the package is bound on the target database. This parameter should be set to FALSE only for supported target DRDA servers and should be set to TRUE otherwise. See DB2 Considerations for supported target servers.

Rebinding Required:
Any change to this parameter requires you to rebind.

DRDA_FLUSH_CACHE

Default value: SESSION

Range of values: {SESSION│COMMIT}

Syntax: DRDA_FLUSH_CACHE={SESSION│COMMIT}

DRDA_FLUSH_CACHE specifies when the cursor cache is to be flushed. With DRDA_FLUSH_CACHE=COMMIT, the cursor cache is flushed whenever the transaction is committed. With DRDA_FLUSH_CACHE=SESSION, the cache is not flushed until the session terminates.

DRDA_GRAPHIC_PAD_SIZE

Default value: 0

Range of values: 0 through 127

Syntax: DRDA_GRAPHIC_PAD_SIZE=num

DRDA_GRAPHIC_PAD_SIZE is used to pad the size of a Graphic column as described by the DRDA Server. This is sometimes necessary depending on the character set of the DRDA database and the Oracle database. If the Oracle database is based on EBCDIC and the DRDA database is based on ASCII, then a pad size of 2 may be needed.

DRDA_GRAPHIC_LIT_CHECK

Default value: FALSE

Range of values: {TRUE│FALSE}

Syntax: DRDA_GRAPHIC_LIT_CHECK={TRUE│FALSE}

DRDA_GRAPHIC_LIT_CHECK directs the gateway to evaluate string literals within INSERT SQL statements to determine if they need to be converted to doubleEbyte format for insertion into a Graphic column at the DRDA Server database. This is done by querying the column attributes of the table in the SQL statement to determine if a string literal is being applied to a column with a Graphic data type. If the table column is Graphic, and if this parameter is TRUE, then the gateway will rewrite the SQL statement with the literal converted to doubleEbyte format. Existing doubleEbyte characters in the string will be preserved, and all singleEbyte characters will be converted to doubleEbyte characters.

DRDA_GRAPHIC_TO_MBCS

Default value: FALSE

Range of values: {TRUE│FALSE}

Syntax: DRDA_GRAPHIC_TO_MBCS={TRUE│FALSE}

DRDA_GRAPHIC_TO_MBCS directs the gateway to convert Graphic data that has been fetched from the DRDA Server into Oracle multibyte data, translating doubleEbyte characters into singleEbyte characters where possible.

DRDA_GRAPHIC_CHAR_SIZE

Default value: 4

Range of values: 1 through 4

Syntax: DRDA_GRAPHIC_CHAR_SIZE=num

DRDA_GRAPHIC_CHAR_SIZE is used to define the character conversion size to be used for GRAPHIC data types. It is a tuning parameter which affects the maximum size of a GRAPHIC data type when the column is described.

DRDA_ISOLATION_LEVEL

Default value: CHG for DB2/400, CS for DB2/OS390, DB2/UDB, DB2/VM

Range of values: {CHG│CS│RR│ALL│NC}

Syntax: DRDA_ISOLATION_LEVEL={CHG│CS│RR│ALL│NC}

DRDA_ISOLATION_LEVEL specifies the isolation level that is defined to the package when it is created. All SQL statements that are sent to the remote DRDA database are run with this isolation level. Isolation level seriously affects performance of applications. Use caution when specifying an isolation level other than the default. For information on isolation levels, refer to IBM database manuals.

The following table lists isolation levels and their descriptions. The levels are specified in ascending order of control, with CHG having the least reliable cursor stability and RR having the most. Note that higher stability uses more resources on the server and can lock those resources for extended periods.

Table C-1 Isolation Levels and Their Descriptions

Level

Description

CHG

Change (default for DB2/400)

CS

Cursor Stability (default for DB2/UDB, DB2/OS390, and DB2/VM)

RR

Repeatable Read

ALL

ALL

NC

No Commit

Rebinding Required:
Any change to this parameter requires you to rebind.

DRDA_LOCAL_NODE_NAME

Default value: AIX_RS6K

Range of values: any alphanumeric string 1 to 8 characters in length

Syntax: DRDA_LOCAL_NODE_NAME=name

DRDA_LOCAL_NODE_NAME specifies the name by which the gateway will be known to the DRDA Server. This name is used internally by the DRDA Server to identify the local node.

DRDA_MBCS_TO_GRAPHIC

Default value: FALSE

Range of values: {TRUE│FALSE}

Syntax: DRDA_MBCS_TO_GRAPHIC={TRUE│FALSE}

DRDA_MBCS_TO_GRAPHIC directs the gateway to convert multibyte data (that has been sent from Oracle to the DRDA database) into pure doubleEbyte characters. This parameter is primarily intended to be used with bind variables to ensure that the data is properly formatted and will therefore be acceptable to the DRDA Server. It applies only to INSERT SQL statements that are using bind variables. When used in combination with the DRDA_GRAPHIC_LIT_CHECK parameter, this parameter can help ensure that data that is being inserted into a Graphic column is handled correctly by the target DRDA Server.

DRDA_OPTIMIZE_QUERY

Default value: TRUE

Range of values: {TRUE│FALSE}

Syntax: DRDA_OPTIMIZE_QUERY={TRUE│FALSE}

DRDA_OPTIMIZE_QUERY turns on or off the distributed query optimizer (DQO) capability. Refer to Performing Distributed Queries in Chapter 11, "Using the Gateway". The DQO capability is useful for optimizing queries that access large amounts of data, but it can add overhead to small queries.

This parameter is valid only if the DRDA Server is DB2/OS390 or DB2/VM. If the DRDA Server is DB2/400 or DB2/UDB, then you must set the value to FALSE.

DRDA_PACKAGE_COLLID

Default value: ORACLE

Range of values: an alphanumeric string 1 to 18 characters in length

Syntax: DRDA_PACKAGE_COLLID=collection_id

DRDA_PACKAGE_COLLID specifies the package collection ID. Note that in DB2/400, the collection ID is actually the name of an AS/400 library.

Rebinding Required:
Any change to this parameter requires you to rebind the package.

DRDA_PACKAGE_CONSTOKEN

Default value: none, use the sample provided

Range of values: a 16-digit hexadecimal number

Syntax: DRDA_PACKAGE_CONSTOKEN=hexnum

DRDA_PACKAGE_CONSTOKEN specifies the package consistency token. This is a 16Edigit hexadecimal representation of an 8Ebyte token. Oracle Corporation recommends that you do not change the consistency token. The consistency token used at run time must match the one used when the package is bound. The value depends on the DRDA Server being used.

Rebinding Required:
Any change to this parameter requires you to rebind the package.

DRDA_PACKAGE_NAME

Default value: G2DRSQL

Range of values: an alphanumeric string 1 to 18 characters in length

Syntax: DRDA_PACKAGE_NAME=name

DRDA_PACKAGE_NAME specifies the package name. Note that the package is stored in the DRDA Server under this name as a SQL resource. Refer to the DRDA Server documentation for length limitations on package names. Many typical implementations restrict the length to 8 characters.

Rebinding Required:
Any change to this parameter requires that you rebind the package.

DRDA_PACKAGE_OWNER

Default value: none

Range of values: any valid user ID

Syntax: DRDA_PACKAGE_OWNER=userid

DRDA_PACKAGE_OWNER specifies the database user ID that owns the package. This enables the owner to be a user other than the connected user ID when the package is created. The package owner must be the same user as the owner of the ORACLE2PC table. This is not valid for DB2/VM.

Rebinding Required:
Any change to this parameter requires you to rebind the package.

DRDA_PACKAGE_SECTIONS

Default value: 100

Range of values: any integer between 1 and 65535

Syntax: DRDA_PACKAGE_SECTIONS=num

DRDA_PACKAGE_SECTIONS specifies the number of cursors declared at the remote database when the package is bound. This is the maximum number of open cursors permitted at any one time. Change this parameter only if an application needs more than 100 open concurrent cursors.

Rebinding Required:
Any change to this parameter requires you to rebind the package.

DRDA_READ_ONLY

Default value: FALSE

Range of values: {TRUE│FALSE}

Syntax: DRDA_READ_ONLY={TRUE│FALSE}

DRDA_READ_ONLY specifies whether the gateway runs in a read-only transaction mode. In this mode, SQL statements which modify data are not permitted.

DRDA_RECOVERY_PASSWORD

Default value: none

Range of values: any valid password

Syntax: DRDA_RECOVERY_PASSWORD=passwd

DRDA_RECOVERY_PASSWORD is used with the DRDA_RECOVERY_USERID parameter. The recovery user connects to the IBM database if a distributed transaction is in doubt. For more information, refer to "TwoEPhase Commit Processing". Also refer to Chapter 13, "Security Considerations" for information about security and about encrypting passwords.

DRDA_RECOVERY_USERID

Default value: ORARECOV

Range of values: any valid user ID

Syntax: DRDA_RECOVERY_USERID=userid

DRDA_RECOVERY_USERID specifies the user ID that is used by the gateway if a distributed transaction is in doubtful state. This user ID must have execute privileges on the package and must be defined to the IBM database.

If a distributed transaction is in doubtful state, then the Oracle integrating server determines the status of the transaction by connecting to the IBM database, using the DRDA_RECOVERY_USERID. If this parameter is missing, the gateway attempts to connect to a user ID of ORARECOV. For more information, refer to "TwoEPhase Commit Processing".

DRDA_REMOTE_DB_NAME

Default value: DB2V2R3

Range of values: an alphanumeric string 1 to 18 characters in length

Syntax: DRDA_REMOTE_DB_NAME=name

DRDA_REMOTE_DB_NAME specifies the DRDA Server location name. This is an identifying name that is assigned to the server for DRDA purposes. A technique for determining this name by using a SQL SELECT statement is discussed in each of the serverEspecific installation sections in Chapter 5, "Configuring the DRDA Server".

DRDA_SECURITY_TYPE

Default value: PROGRAM

Range of values: {PROGRAM│SAME}

Syntax: DRDA_SECURITY_TYPE={PROGRAM│SAME}

DRDA_SECURITY_TYPE specifies the type of security used for SNA communications. For more information about types of security and about setting DRDA_SECURITY_TYPE, refer to Chapter 13, "Security Considerations". Also refer to Chapter 15 for information about security and encrypting passwords.

FDS_CLASS

Default value: TG4DRDA_DB2MVS

Range of values: Refer to the list below for valid values

Syntax: FDS_CLASS=TG4DRDA_DB2MVS

FDS_CLASS specifies the capability classification used by the Oracle Database server and the gateway. These values might change from release to release, depending on whether the gateway capabilities change.

The valid default values for FDS_CLASS are as follows:

For a DB2/OS390 database: TG4DRDA_DB2MVS

For a DB2/VM database: TG4DRDA_DB2VM

For a DB2/400 database: TG4DRDA_DB2400

For a DB2/UDB database: TG4DRDA_DB2UDB

FDS_CLASS_VERSION

Default value: 10.1.0.2.0

Range of values: 10.1.0.2.0

Syntax: FDS_CLASS_VERSION=1

FDS_CLASS_VERSION specifies the version of the FDS_CLASS capabilities. Do not specify this parameter unless directed to do so by Oracle Support Services.

FDS_INSTANCE

Default value: DRD1

Range of values: the name of the gateway SID

Syntax: FDS_INSTANCE=drdahoa1

FDS_INSTANCE specifies a subset of the FDS_CLASS capabilities that may be modified by the user, based on initialization file parameters. If you do not specify this parameter, then its value will be the Oracle SID that is defined in the TNS Listener entry.

HS_FDS_FETCH_ROWS

Default value: 20

Range of values: any integer between 1 and 1000

Syntax: HS_FDS_FETCH_ROWS=num

HS_FDS_FETCH_ROWS specifies the fetch array size. This is the number of rows to fetch at one time from the DRDA Server and to return to the Oracle Database server. This parameter will be affected by the HS_RPC_FETCH_SIZE and HS_RPC_FETCH_REBLOCKING parameters. For further information on these parameters, refer to the section "Controlling the Array Fetch Between Agent and NonEOracle Database server" in the Oracle Database Heterogeneous Connectivity Administrator's Guide.

HS_LANGUAGE

Default value: none

Range of values: any valid language specification

Syntax: HS_LANGUAGE=language[_territory.character_set ]

HS_LANGUAGE specifies the language and the character set that the gateway will use to interact with the DRDA Server. Care must be taken in choosing the value of these parameters, especially when the gateway will be accessing GRAPHIC data. For additional details, refer to Appendix D, "National Language Support" and to the Oracle Database Heterogeneous Connectivity Administrator's Guide.

HS_NLS_NCHAR

Default value: none

Range of values: any valid character set specification

Syntax: HS_NLS_NCHAR=character_set

HS_NLS_NCHAR specifies the character set that the gateway will use to interact with the DRDA Server when accessing GRAPHIC data. Set this parameter to the same value as the character set component of the HS_LANGUAGE parameter. For additional details, refer to Appendix D, "National Language Support" and to the Oracle Database Heterogeneous Connectivity Administrator's Guide.

LOG_DESTINATION

Default value: ORACLE_HOME\tg4drda\log\gateway sid_pid.log

Range of values: any valid file path

Syntax: LOG_DESTINATION=logpath

LOG_DESTINATION specifies the destination for gateway logging and tracing. This parameter should specify a file. If the file already exists, then it will be overwritten.

After any failure to open the log path, a second attempt to open the default is made.

Usually, LOG_DESTINATION should specify a directory. If it is specified as a file and if two or more users simultaneously use the same instance of the gateway, then they are writing to the same log. The integrity of this log is not guaranteed. If you do not specify this parameter, then the default is assumed.

ORA_MAX_DATE

Default value: 4712-12-31

Range of values: any valid date less than 4712E12E31

Syntax: ORA_MAX_DATE=yyyy-mm-dd

ORA_MAX_DATE specifies the gateway maximum date value. If the fetched date value is larger than 4712E12E31, then the gateway replaces the date value with the value defined by the ORA_MAX_DATE parameter. Any date between January 1, 4712 BC and December 31, 4712 AD is valid.

ORA_NLS10

Default value: ORACLE_HOME\nls\data

Range of values: any valid NLS directory path

Syntax: SET ORA_NLS10=nlspath

ORA_NLS10 specifies the directory to which the gateway loads its character sets and other language data. Normally, this parameter does not need to be set. Some configurations, however, may require that it be set.

ORACLE_DRDA_TCTL

Default value: none

Range of values: any valid file path

Syntax: ORACLE_DRDA_TCTL=tracecontrolpath

ORACLE_DRDA_TCTL specifies the path to the DRDA internal trace control file. This file contains module tracing commands. A sample file is stored in ORACLE_HOME\tg4drda\admin\debug.tctl. This parameter is used for diagnostic purposes.

ORACLE_DRDA_TRACE

Default value: value specified for LOG_DESTINATION

Range of values: any valid file path

Syntax: ORACLE_DRDA_TRACE=logpath

ORACLE_DRDA_TRACE is used to specify a different log path for DRDA internal tracing. This tracing is separate from the rest of the gateway tracing, as specified by the LOG_DESTINATION parameter. By default, this parameter will append the DRDA internal trace to the gateway trace. This parameter is used for diagnostic purposes.

TRACE_LEVEL

Default Value: 0

Range of values: 0-255

Syntax: TRACE_LEVEL=number

TRACE_LEVEL specifies a code tracing level. This value determines the level of detail which is logged to the gateway log file during processing. This parameter is primarily used for diagnostics.

D National Language Support

This appendix documents the National Language Support (NLS) information for the Oracle Transparent Gateway for DRDA. This supplements the general Oracle NLS information found in the Oracle Database Application Developer's Guide - Fundamentals.

National Language Support enables users to interact with Oracle applications in their native language, using their conventions for displaying data. The Oracle NLS architecture is dataEdriven, enabling support for specific languages and character encoding schemes to be added without any changes in source code.

There are a number of different settings in the gateway, DRDA Server, Oracle Database 10g server, and client that affect NLS processing. In order for translations to take place correctly, character settings of these components must be compatible.

This appendix contains the following sections:

- Overview of NLS Interactions

- Client and Oracle Integrating Server Configuration

- Gateway Language Interaction with DRDA Server

- Gateway Codepage Map Facility

- Multibyte and DoubleEByte Support in the Gateway

- Message Availability

- Example of NLS Configuration

Overview of NLS Interactions

Figure D-1 illustrates NLS interactions within your system, including each component of your system and the parameters of each component that affect NLS processing in a distributed environment. Table D-1 describes the architecture illustrated in Figure D-1.

Figure D-1 Architecture of NLS Interactions with Your System Components

Table D-1 describes in detail the parameters and variables needed for NLS processing within each of your system environments: the client environment, the Oracle integrating server, the gateway, and the DRDA Server.

Table D-1 Parameters Needed for NLS Processing in Your System Environments

Environment

Parameter or Variable

Description

Client

NLS_LANG

An environmental variable. NLS_LANG sets the NLS environment that is used by the database, both for the server session and for the client application. This ensures that the language environments of both database and client application are automatically the same. Because NLS_LANG is an environment variable, it is read by the client applications at startup time. The client communicates the information defined in NLS_LANG to the server when it connects. Refer to "Client and Oracle Integrating Server Configuration" for detailed information.

Oracle integrating server

CHARACTER SET

This option is set during creation of the database. CHARACTER SET determines the character encoding scheme that is used by the database. CHARACTER SET is defined at database creation in the CREATE DATABASE statement. All data columns of type CHAR, VARCHAR2, and LONG have their data stored in the database character set. Refer to "Client and Oracle Integrating Server Configuration" for detailed information.

Oracle Transparent Gateway for DRDA

ORA_NLS11

An environmental variable. ORA_NLS11 determines where the gateway loads its character sets and other language data. Refer to "Gateway Language Interaction with DRDA Server" for detailed information.

Oracle Transparent Gateway for DRDA

NLS_LANG

An environmental variable. NLS_LANG defines the character set that is used for communication between the gateway and the Oracle integrating server. Refer to "Gateway Language Interaction with DRDA Server" for detailed information.

Oracle Transparent Gateway for DRDA

HS_LANGUAGE

An initialization parameter HS_LANGUAGE defines the character set that is used for communication between the gateway and the DRDA Server. Refer to "Gateway Language Interaction with DRDA Server" for detailed information.

Oracle Transparent Gateway for DRDA

HS_NLS_NCHAR

An initialization parameter. HS_NLS_NCHAR defines the NCHAR character set that is used for communications between the gateway and the DRDA Server. This parameter is required when the gateway will be accessing GRAPHIC or multibyte data on the DRDA Server. Set this parameter to the same value as the character set component of the HS_LANGUAGE parameter. For detailed information, refer to "Gateway Language Interaction with DRDA Server".

Oracle Transparent Gateway for DRDA

HS_NLS_DATE_FORMAT

An initialization parameter. HS_NLS_DATE_FORMAT specifies the format for dates that are used by the DRDA Server. Refer to "Gateway Language Interaction with DRDA Server" for detailed information.

Oracle Transparent Gateway for DRDA

HS_NLS_DATE_LANGUAGE

An initialization parameter. HS_NLS_DATE_LANGUAGE specifies the language that is used by the DRDA Server for day and month names, and for date abbreviations. Refer to "Gateway Language Interaction with DRDA Server" for detailed information.

DRDA Server

CCSID

CCSID is the server character set that is mapped in the gateway to the equivalent Oracle character set. The CCSID specifies the character set that the DRDA database uses to store data. It is defined when you create your database. Refer to "Gateway Codepage Map Facility".

Client and Oracle Integrating Server Configuration

A number of NLS parameters control NLS processing between the Oracle Database server and client. You can set language-dependent action defaults for the server, and you can set language-dependent action for the client that overrides these defaults. For a complete description of NLS parameters, refer to the NLS chapter in the Oracle Database Administrator's Guide. These parameters do not directly affect gateway processing. However, you must ensure that the client character set (which is specified by the Oracle Database server NLS_LANG environment variable) is compatible with the character sets that you specify on the gateway and on the DRDA Server.

When you create the Oracle Database, the character set that is used to store data is specified by the CHARACTER SET clause of the CREATE DATABASE statement. After the database is created, the database character set cannot be changed unless you reEcreate the database.

Normally, the default for CHARACTER SET is US7ASCII, which supports only the 26 Latin alphabetic characters. If you have specified 8Ebit character sets on the gateway and DRDA Server, then you must have a compatible 8Ebit character set defined on your database. To check the character set of an existing database, run the command:

SELECT USERENV('LANGUAGE') FROM DUAL;

For more information, refer to "Specifying Character Sets" in the Oracle Database Administrator's Guide.

Note that this does not mean that the gateway character set must be the same as the Oracle server character set. The Oracle Net facility will be performing implicit conversion between the Oracle server character set and the gateway character set.

Gateway Language Interaction with DRDA Server

During logon of the gateway to the DRDA Server, initial language information is exchanged between the Gateway and the server. First, the gateway sends to the DRDA Server the CCSID it will be conversing in. In the following example, the Oracle character set "WE8ISO8859P1" is mapped to CCSID 819 (an ASCII Code Page). This CCSID is sent to the DRDA Server. The DRDA Server responds with the CCSID that it will be conversing in. This will be the CCSID with which the DB2 database was generated. Also, in the following example, this is CCSID 500, an EBCDIC code page. Figure D-2, "Gateway Language Interaction with DRDA Server", illustrates this process.

A DB2 instance will map unknown CCSIDs using the SYSIBM.SYSSTRINGS table (this table has different names for the various DB2 versions). It is possible to add additional character set mappings to this table using DB2 utilities. Please refer to the DB2 Installation documentation for details.

The setting of the HS_LANGUAGE parameter in the gateway initsid.ora determines which CCSID is used by the gateway for the conversation. Similarly, the setting of the HS_NLS_NCHAR parameter determines which CCSID will be used by the gateway for GRAPHIC data interchange. For the list of supported ASCIIEbased Oracle character sets that are mapped to CCSIDs, refer to "Gateway Codepage Map Facility".

Note again that the gateway character set need not be the same as the Oracle Database server character set. In many cases, it is not feasible to set the gateway character set equal to the Oracle Database server character set because the DRDA Server will not have a valid translation for it. Instead, choose a character set that will have the most complete intersection with the character set that is used by the DRDA Server. The Oracle Net facility will do any translation between the gateway character set and the Oracle server character set.

Figure D-2 Gateway Language Interaction with DRDA Server

Gateway Configuration

After the gateway is installed, you must change several parameters to customize for NLS support.

NLS Parameters in the Gateway Initialization File

Four parameters in the gateway initialization file (initsid.ora) affect NLS:

- HS_LANGUAGE

- HS_NLS_NCHAR

- HS_NLS_DATE_FORMAT

- HS_NLS_DATE_LANGUAGE

HS_LANGUAGE

HS_LANGUAGE defines the character set that is used for communication between the gateway and the DRDA Server. It specifies the conventions such as: the language used for messages from the target system; names of days and months; symbols for AD, BC, AM, and PM; and default language sorting mechanism.

The syntax of the HS_LANGUAGE parameter is:

HS_LANGUAGE=language[_territory.character_set]

where:

language can be any valid language.

territory is optional, and defaults to AMERICA.

character_set is optional and defaults to US7ASCII. This must be an ASCII base character set name, and it should match a character set listed in the gateway code page map. Refer to "Gateway Codepage Map Facility" for the list of supplied character set mappings.

If you omit the HS_LANGUAGE parameter from initsid.ora, then the default setting is AMERICAN_AMERICA.US7ASCII. EBCDIC character sets are not supported. The values for language and territory (such as AMERICAN_AMERICA) must be valid, but they have no effect on translations.

HS_NLS_NCHAR

HS_NLS_NCHAR specifies the character set that is used by the gateway to interchange GRAPHIC data. For correct compatibility, set it to the same character set name that is specified in the HS_LANGUAGE parameter. If it is set to a character set other than that specified in HS_LANGUAGE, or if it is omitted, then translation errors will occur.

HS_NLS_DATE_FORMAT

HS_NLS_DATE_FORMAT specifies the format for dates used by the DRDA Server.

The syntax of the NLS_DATE_FORMAT parameter is:

HS_NLS_DATE_FORMAT=date_format

where date_format must be YYYY-MM-DD, the ISO date format. If this parameter is set to any other value or is omitted, then you receive an error when updating, deleting from, selecting from, or inserting into, a table with date columns.

HS_NLS_DATE_LANGUAGE

HS_NLS_DATE_LANGUAGE specifies the language used by the DRDA Server for day and month names, and for date abbreviations. Because ISO date format contains numbers only, this parameter has no effect on gateway date processing and should be omitted.

Gateway Codepage Map Facility

The gateway now has a user-specifiable facility to map IBM Coded Character Set Identifiers (CCSIDs) to Oracle Character Sets for the purpose of data translation.

The map name defaults to codepage.map and is located in the directory ORACLE_HOME\tg4drda\admin. Refer to Appendix C, "DRDAESpecific Parameters" for more detailed information about the DRDA_CODEPAGE_MAP parameter.

The map has two different forms of syntax. The first form of syntax defines a mapping between a CCSID and an Oracle Database character set:

[S│D│M] CCSID direction Oracle_CharacterSet {shift}

where:

S designates a singleEbyte character set

D designates a doubleEbyte character set

M designates a multibyte character set

CCSID  is the IBM coded character set identifier

direction is one of the following:

- =  means mapping is bidirectional

- <  means mapping is one-way, Oracle character set to CCSID

- >  means mapping is one-way, CCSID to Oracle character set

Oracle_CharacterSet  is the name of a valid Oracle character set.

shift indicates a character set that requires Shift OUT/IN processing. Set this attribute only for EBCDICEbased doubleEbyte and multibyte mappings.

The second form of syntax defines a mapping of a multibyte CCSID to its singleEbyte and doubleEbyte CCSID equivalents:

MBC multi = single double

where:

multi is the multibyte CCSID

single is the single-byte CCSID

double is the double-byte CCSID

This facility is intended as a way of mapping CCSIDs which were not previously mapped as shipped with the gateway. You must contact Oracle Support Services before modifying this map.

The following are the contents of the map as shipped with the Oracle Transparent Gateway for DRDA;

# Copyright (c) 2001, 2003, Oracle Corporation.  All rights reserved.
# Transparent Gateway for IBM DRDA - CodePage/Oracle CharacterSet Map
# S==Single-byte, D==Double-byte, M==Multi-byte, MBC==SBC DBC mapping
#
# Single-byte codepage mappings
#
S    37 = WE8EBCDIC37   # United States/Canada                          EBCDIC
S   273 = D8EBCDIC273   # Austria/Germany                               EBCDIC
S   277 = DK8EBCDIC277  # Denmark/Norway                                EBCDIC
S   278 = S8EBCDIC278   # Finland/Sweden                                EBCDIC
S   280 = I8EBCDIC280   # Italy                                         EBCDIC
S   284 = WE8EBCDIC284  # Latin America/Spain                           EBCDIC
S   285 = WE8EBCDIC285  # United Kingdom                                EBCDIC
S   297 = F8EBCDIC297   # France                                        EBCDIC
#S   420 = AR8EBCDICX    # Arabic Bilingual (USA English)                EBCDIC
S   420 = AR8XBASIC     # Arabic Bilingual (USA English)                EBCDIC
S   424 = IW8EBCDIC424  # Israel (Hebrew)                               EBCDIC
S   437 = US8PC437      # Personal Computer,USA                         ASCII
S   500 = WE8EBCDIC500  # International                                 EBCDIC
S   813 = EL8ISO8859P7  # Greek                                         ASCII
S   819 = WE8ISO8859P1  # ISO/ANSI Multilingual                         ASCII
S   838 = TH8TISEBCDIC  # Thai w/Low-Tone Marks & Ancient Chars         EBCDIC
S   850 < US7ASCII      # Multilingual Page - Personal Computer         ASCII
S   850 = WE8PC850      # Multilingual Page - Personal Computer         ASCII
S   864 = AR8ISO8859P6  # Arabic - Personal Computer                    ASCII
S   870 = EE8EBCDIC870  # Latin 2, Multilingual/ROECE                   EBCDIC
S   871 = WE8EBCDIC871  # Iceland - CECP                                EBCDIC
S   875 = EL8EBCDIC875  # Greece                                        EBCDIC
S   904 > US7ASCII      # Traditional Chinese - PC-Data                 ASCII
S   912 = EE8ISO8859P2  # Latin 2 8-bit                                 ASCII
S   916 = IW8ISO8859P8  # Israel (Hebrew)                               ASCII
S  1025 = CL8EBCDIC1025 # Cyrillic, Multiling                           EBCDIC
S  1086 = IW8EBCDIC1086 # Israel                                        EBCDIC
S  1252 = WE8MSWIN1252  # Latin 1 - MS-Windows                          ASCII
S  1253 = EL8MSWIN1253  # Greek - MS-Windows                            ASCII
S 28709 > WE8EBCDIC37   # United States/Canada (CP28709==CP37)          EBCDIC
#
# Multibyte codepage mappings
#
#S   833 > KO16DBCS       # Korean Extended single-byte                  EBCDIC
#D   834 > KO16DBCS shift # Korean double-byte                           EBCDIC
#M   933 = KO16DBCS shift # Korean Mixed multi-byte                      EBCDIC

#MBC 933 = 833 834        # Korean Mixed multi-byte                      EBCDIC
#
#S  1088 > KO16MSWIN949 # Korean KS single-byte PC-Data                  ASCII
#D   951 > KO16MSWIN949 # Korean KS double-byte PC-Data                  ASCII
#M   949 = KO16MSWIN949 # Korean KS multi-byte PC-Data                   ASCII
#MBC 949 = 1088 951     # Korean KS multi-byte PC-Data                   ASCII
#
#S   891 > KO16KSC5601 # Korean single-byte                              ASCII
#S  1040 > KO16KSC5601 # Korean single-byte                              ASCII
#D   926 > KO16KSC5601 # Korean double-byte                              ASCII
#M   934 = KO16KSC5601 # Korean multi-byte                               ASCII
#M   944 > KO16KSC5601 # Korean multi-byte                               ASCII
#MBC 934 = 891 926     # Korean multi-byte                               ASCII
#MBC 944 = 1040 926    # Korean multi-byte Extended                      ASCII
#
#S 28709 > ZHT16DBCS       # Traditional Chinese single-byte             EBCDIC
#D   835 > ZHT16DBCS shift # Traditional Chinese double-byte             EBCDIC
#M   937 = ZHT16DBCS shift # Traditional Chinese multi-byte              EBCDIC
#MBC 937 = 28709 835       # Traditional Chinese multi-byte              EBCDIC
#
#S  1114 > ZHT16MSWIN950 # Traditional Chinese single-byte               ASCII
#D   947 > ZHT16MSWIN950 # Traditional Chinese double-byte               ASCII
#M   950 = ZHT16MSWIN950 # Traditional Chinese multi-byte                ASCII
#MBC 950 = 1114 947      # Traditional Chinese multi-byte                ASCII
#

#S   836 > ZHS16DBCS       # Simplified Chinese single-byte              EBCDIC
#D   837 > ZHS16DBCS shift # Simplified Chinese double-byte              EBCDIC
#M   935 = ZHS16DBCS shift # Simplified Chinese multi-byte               EBCDIC
#MBC 935 = 836 837         # Simplified Chinese multi-byte               EBCDIC
#
#S  1027 > JA16DBCS       # Japanese single-byte                         EBCDIC
#D   300 > JA16DBCS shift # Japanese double-byte                         EBCDIC
#D  4396 > JA16DBCS shift # Japanese double-byte                         EBCDIC
#M   939 = JA16DBCS shift # Japanese multi-byte                          EBCDIC
#M  5035 > JA16DBCS shift # Japanese multi-byte                          EBCDIC
#MBC  939 = 1027 300      # Japanese multi-byte                          EBCDIC
#MBC 5035 = 1027 4396     # Japanese multi-byte                          EBCDIC
#
#S   290 > JA16EBCDIC930       # Japanese single-byte                    EBCDIC
#D   300 > JA16EBCDIC930 shift # Japanese double-byte                    EBCDIC
#D  4396 > JA16EBCDIC930 shift # Japanese double-byte                    EBCDIC
#M   930 = JA16EBCDIC930 shift # Japanese multi-byte                     EBCDIC
#M  5026 > JA16EBCDIC930 shift # Japanese multi-byte                     EBCDIC
#MBC  930 = 290 300            # Japanese multi-byte                     EBCDIC
#MBC 5026 = 290 4396           # Japanese multi-byte                     EBCDIC
#

Refer to the following list to check the character set of an existing database:

- for DB2/OS390: Ask your system administrator. There is no single command you use.

- for DB2/400: Run the command DSPSYSVAL SYSVAL(QCCSID)

- for DB2/UDB: Ask your system administrator. There is no single command you use.

- for DB2/VM: Run the statement ID. This shows you the default CCSIDs used at startup.

Multibyte and DoubleEByte Support in the Gateway

To enable the gateway to properly handle doubleEbyte and multibyte data, you must configure the code page map facility with proper multibyte maps and (as an option) you can set the following gateway configuration parameters:

- DRDA_GRAPHIC_LIT_CHECK

- DRDA_GRAPHIC_TO_MBCS

- DRDA_MBCS_TO_GRAPHIC

- DRDA_GRAPHIC_PAD_SIZE

- DRDA_GRAPHIC_CHAR_SIZE

Refer to Appendix C, "DRDAESpecific Parameters", for the values of these parameters.

Configuring the code page map requires knowledge of the code pages that have been configured in the DRDA Server database as well as knowledge of compatible Oracle Database character sets.

IBM coded character set identifiers (CCSIDs) are used to indicate which code pages are configured as the primary codepage for the database, as well as any translation character sets loaded into the database. Some DRDA Servers, such as with DB2, have a translation facility in which character set transforms are mapped between two compatible character sets. For DB2/OS390, these transforms are stored in the table SYSIBM.SYSSTRINGS and transform on the CCSID codepage to another CCSID codepage. In SYSSTRINGS, IN and OUT columns specify the CCSIDs that are used in the transform. Typical transforms are from ASCII to EBCDIC and back again. Two transforms are therefore used for two given CCSIDs.

Multibyte codepages are a composite of a singleEbyte codepage and a doubleEbyte codepage. As an example, the Korean EBCDIC multiEbyte codepage, CCSID 933, is composed of two codepages, codepage 833 (for singleEbyte) and codepage 834 (for doubleEbyte). The DRDA Server, therefore, can send data to the gateway in any of these three codepages, and the gateway must translate suitably depending on which codepage the data is associated with. Because CCSID 933 is an EBCDICEbased codepage, and the gateway must use an ASCIIEbased codepage, we identify an equivalent set of codepages, which are ASCIIEbased. An example would be the Korean multibyte codepage, CCSID 949, which is composed of two codepages, codepage 1088 (for singleEbyte) and codepage 951 (for doubleEbyte).

The codepage map facility is used to map these CCSIDs into the equivalent Oracle Database character sets. Unlike IBM CCSIDs, Oracle Database character sets are unified (in that singleEbyte and doubleEbyte character sets have been combined into one set) and are thus identified by one ID instead of three IDs. In our previous example, the equivalent Oracle Database Character Set for the ASCII Korean codepages would be KO16MSWIN949, and the EBCDIC Korean codepages would be KO16DBCS. These are identified to the gateway by using a set of mapping entries in the codepage.map file.

First, the EBCDIC Korean sets are:

S   833 > KO16DBCS       # Korean Extended single-byte                  EBCDIC
D   834 > KO16DBCS shift # Korean double-byte                           EBCDIC
M   933 = KO16DBCS shift # Korean Mixed multi-byte                      EBCDIC
MBC 933 = 833 834        # Korean Mixed multi-byte                      EBCDIC

Notice that the multibyte set is a bidirectional map to KO16DBCS, while the single and double codepages are mapped one-way to KO16DBCS. Because only one bidirectional CCSID to Oracle Database character set entry for a given pair can exist, we directly map the multibyte sets. And because the singleEbyte and doubleEbyte CCSIDs are ostensibly subsets of KO16DBCS, we map them as oneEway entries. Note that doubleEbyte and multibyte maps are tagged with the shift attribute. This is required for EBCDIC doubleEbyte and multibyte codepages as part of the shift out/in encapsulation of data. Note that the singleEbyte map is not marked because singleEbyte sets are not permitted to contain doubleEbyte data and thus will never use shift encapsulation. Also note that the MBC entry ties the codepages together.

The ASCII Korean sets are similarly mapped and are:

S  1088 > KO16MSWIN949 # Korean KS single-byte PC-Data                  ASCII
D   951 > KO16MSWIN949 # Korean KS double-byte PC-Data                  ASCII
M   949 = KO16MSWIN949 # Korean KS multi-byte PC-Data                   ASCII
MBC 949 = 1088 951     # Korean KS multi-byte PC-Data                   ASCII

Notice that the multibyte set is a bidirectional map to KO16MSWIN949, while the single and double codepages are mapped oneEway to KO16MSWIN949. Because only one bidirectional CCSID to Oracle Database character set entry for a given pair can exist, we directly map the multibyte sets. And because the singleEbyte and doubleEbyte CCSIDs are ostensibly subsets of KO16MSWIN949, we map them as oneEway entries. Note that there is no shift attribute in any of these mappings. This is because ASCIIEbased sets do not use shift out/in encapsulation. Instead, ASCIIEbased sets use a different method (which does not use a shift out/in protocol) to identify doubleEbyte characters.

The above entries supply the necessary codepage mappings for the gateway. To complete the example, we need to specify the correct character set in the HS_LANGUAGE and HS_NLS_NCHAR parameters in the gateway initialization file. The gateway initialization parameters would look as follows:

HS_LANGUAGE=AMERICAN_AMERICA.KO16MSWIN949
HS_NLS_NCHAR=KO16MSWIN949

Note that the specified character set must be ASCIIEbased.

This takes care of configuration of the gateway. The last step is to set up transforms between the EBCDIC codepages and the ASCII codepages in the DRDA Server database. Normally, the gateway would use a total of six transforms, one of each pair in both directions. You may save some table space by installing only the ASCIIEtoEEBCDIC transforms. The reasoning is that the DRDA Server needs to translate only the ASCII data that is sent by the gateway, but the DRDA Server does not need to send ASCII data. The gateway will receive the EBCDIC data and translate as needed. This oneEsided data transfer methodology is called "receiverEmakesEright", meaning that the receiver must translate whatever character set the sender uses. In our example, the DRDA Server is EBCDICEbased, so it will send all data in EBCDIC. The server, therefore, does not need to have an EBCDICEtoEASCII transform because the server will never use the transform.

In our previous example, the DRDA Server database is assumed to be EBCDIC, which is likely to be true for a DB2/OS390 database. For a DB2/UDB database, however, this is not likely to be true. Because most DB2/UDB databases are running on ASCIIEbased computers, they will likely be created with ASCIIEbased codepages. In such cases, the gateway needs to have only one set of codepage map definitions, which are those for the ASCII set. Also, because both the DRDA Server and the gateway will be using the same codepages, no character set transforms need to be loaded into the DB2 database. This can help reduce the amount of CPU overhead that is associated with character translation.

One final note concerning codepage map entries: Be aware that some multiEbyte codepages may be composed of singleEbyte CCSIDs that are already defined in the codepage.map file that is provided with the product. If you are adding a new set of entries to support a multibyte set, then comment out the provided entries so that your new entries will be used correctly.

Additional codepage mappings, which are not already provided, are possible. You may construct entries such as those in our examples, given knowledge of the IBM CCSIDs and the Oracle Database character sets. Because this can be complex (given the IBM documentation of codepage definitions and Oracle Database Character Set definitions), thoroughly test your definitions for all desired character data values before putting them into production.

If you are uncertain, then contact Oracle Support Services to request proper codepage mapping entries.

Message Availability

Whether a language message module is available depends on which modules are installed in the Oracle product set running on the server. If message modules for a particular language set are not installed, then specifying that language with a language parameter does not display messages in the requested language.

Example of NLS Configuration

Following is an example of all the settings needed to configure the gateway, DRDA Server, Oracle server, and client so that a language and character set are working compatibly across the system. In this example, the settings enable a customer in Germany to interact with the gateway in German:

Gateway initsid.ora file:

HS_LANGUAGE=AMERICAN_AMERICA.WE8ISO8859P1
HS_NLS_DATE_FORMAT=YYYY-MM-DD

DRDA Server CCSID:

273 (D8EBCDIC273)

Oracle server and client setting for database:

SELECT USERENV('language') FROM DUAL;
USERENV('LANGUAGE')
-----------------------------
AMERICAN_AMERICA.WE8ISO8859P1

Oracle server and client environment variables:

NLS_LANG=GERMAN_GERMANY.WE8ISO8859P1

E Configuration Worksheet

Information That You Need in Order to Configure the Gateway and the Communications Interfaces (SNA Server and TCP/IP)

Table E-1 List of Parameters Needed to Configure the Gateway

Reason

Name of Parameter Needed

Your Specific Parameters Here

For: Gateway's Oracle Home

- ORACLE_HOME

__________________________

For: Gateway's System ID

- ORACLE_SID

__________________________

For: SNA Server Definition

- SNA Subdomain

- SNA Service

____________________________________________________

For: Primary Service Definition

- Network Name

- Control Point Name

__________________________

__________________________

For: SNA Server Link Service

- Suitable Link Service Identification (example: DLC 80202 Link Service)

__________________________

For: Link Service Properties

- Suitable Network Adapter information (example: IBM Auto 16/4 TokenERing Adapter)

__________________________

For: Creating a General Connection Definition

- Suitable Connection Type (Example: 802.2)

- Connection Name

- Suitable Link Service

__________________________
__________________________
__________________________

For: Connection Properties Address

- Remote Network Address

- Remote SAP Address

__________________________

__________________________

For: System Identification: Local Node Name and Remote Node Name

- For each: Network Name

- Control Point Name

- Local Node ID

- Remote Node ID

__________________________

__________________________

__________________________

__________________________

For: DLC values

possible change of default values

__________________________

For: Creating a Local LU Definition:

- LU Alias

- LU Name

__________________________

__________________________

For: General APPC Mode Definition

- Mode Name

__________________________

For: APPC Mode Limits

- Parallel Session Limit

- Minimum Contention Winner Limit

- Partner Min Contention Winner Limit

- Automatic Activation Limit

__________________________

__________________________

__________________________

__________________________

For: APPC Mode Characteristics

- Pacing Send Count

- Pacing Receive Count

- Max Send RU Size

__________________________

__________________________

__________________________

For: Remote LU Definition, General Properties

- Suitable Connection name

- LU ALias

- Network Name

- Uninterpreted Network Name

__________________________

__________________________

__________________________

__________________________

For: Remote LU Properties Options

- Any Security Options needed

__________________________

For: Creating CPIEC Symbolic Destination Names (Side Information Profiles), general information

- Suitable Name for each Side Information Profile

- Suitable Mode

__________________________

__________________________

For: Partner Information in CPIEC Name Properties

- TP Name

- Partner LU Name Alias

__________________________

__________________________

For: Configuring TCP/IP

- Local Host name, Domain Name

- IP Address

- Network Mask

- Name Server IP Address

- DRDA Server Host name or IP Address

- DRDA Server Service Port Number

__________________________

__________________________

__________________________

__________________________

__________________________

__________________________

For: Recovery user ID

- DRDA_RECOVERY_USERID

__________________________

For: Recovery Password

- DRDA_RECOVERY_PASSWORD

__________________________

For: Remote Database Name

- DRDA_REMOTE_DB_NAME

__________________________

For: Connection Parameter

- DRDA_CONNECT_PARM

__________________________

For: Remote collection ID

DRDA_PACKAGE_COLLID

___________________________

For: Remote package name

DRDA_PACKAGE_NAME

__________________________

For: Owner ID of DRDA package

DRDA_PACKAGE_OWNER

___________________________

For: DB Name used with Oracle server

HS_DB_NAME

___________________________

For: DB Domain used with Oracle server

HS_DB_DOMAIN

___________________________

Note:
The user ID that is used to bind or rebind the DRDA package must have the following privileges on the remote database; your database administrator will need to provide these.

- package privileges of BIND, COPY, and EXECUTE

- collection privilege of CREATE IN

- system privileges of BINDADD and BINDAGENT

F Quick Reference to Oracle SQL Functions

Following are the Oracle SQL functions:

Table F-1 Oracle SQL Functions in Alphabetic Order

Functions

ABS

ACOS

ADD_MONTHS

ASIN

ASCII

ATAN

ATAN2

CEIL

CHAR_TO_ROWID

CHR

CONVERT

COS

COSH

DECODE

DUMP

EXP

FLOOR

GREATEST

HEXTORAW

INITCAP

INSTR

INSTRB

LAST_DAY

LEAST

LENGTH

LENGTHB

LN

LOG

LOWER

LPAD

LTRIM

MOD

MONTHS_BETWEEN

NEW_TIME

NEXT_DAY

NLS_INITCAP

NLS_LOWER

NLS_UPPER

NLSSORT

POWER

RAWTOHEX

REPLACE

ROUND

ROWIDTOCHAR

RPAD

RTRIM

SIGN

SIN

SINH

SOUNDEX

SQRT

STDDEV

SUBSTR

SUBSTRB

SYSDATE

TAN

TANH

TO_CHAR

TO_DATE

TO_LABEL

TO_MULTI_BYTE

TO_NUMBER

TO_SINGLE_BYTE

TRANSLATE

TRUNC

UID

UPPER

USER

USERENV

VARIANCE

VSIZE

BITAND

G Sample Applications

This appendix contains sample applications that can be used with the gateway:

- DB2INS

- ORAIND

DB2INS

DB2INS is a sample DB2 stored procedure that inserts a row into a DB2 table. This procedure uses the SIMPLE linkage convention.

/*********************************************************************/
/*                                                                   */
/* This DB2 stored procedure inserts values for the DNAME and LOC    */
/* columns of DB2 user table SCOTT.DEPT.                             */
/*                                                                   */
/* The SCOTT.DEPT table is defined to DB2 as                         */
/*       DEPTNO INTEGER, DNAME CHAR(14), LOC VARCHAR(13).            */
/*                                                                   */
/* This procedure receives 3 input parameters from the calling       */
/* program which contain the values to insert for DEPTNO, DNAME, and */
/* LOC.                                                              */
/*                                                                   */
/* The linkage convention used for this stored procedure is SIMPLE.  */
/*                                                                   */
/* The output parameter for this procedure contains the SQLCODE from */
/* the INSERT operation.                                             */
/*                                                                   */
/* The entry in the DB2 catalog table SYSIBM.SYSPROCEDURES for this  */
/* stored procedure might look like this:                            */
/*                                                                   */
/* INSERT INTO SYSIBM.SYSPROCEDURES                                  */
/*   (PROCEDURE, AUTHID, LUNAME, LOADMOD, LINKAGE, COLLID, LANGUAGE, */
/*    ASUTIME, STAYRESIDENT, IBMREQD, RUNOPTS, PARMLIST)             */
/* VALUES                                                            */
/*   ('DB2INS',  ' ', ' ', 'DB2INS', ' ', 'DB2DEV', 'C', '0', ' ',   */
/*    'N', ' ', 'A INT IN, B CHAR(14) IN, C VARCHAR(13) IN,          */
/*    D INT OUT, E CHAR(10) OUT');                                   */
/*********************************************************************/
#pragma runopts(plist(os))
#include <stdlib.h>
EXEC SQL INCLUDE SQLCA;
/*********************************************************************/
/* Declare C variables for SQL operations on the parameters.  These  */
/* are local variables to the C program which you must copy to and   */
/* from the parameter list provided to the stored procedure.         */
/*********************************************************************/

EXEC SQL BEGIN DECLARE SECTION;
long dno;               /* input parm - DEPTNO */
char dname[15];         /* input parm - DNAME  */
char locale[14];        /* input parm - LOC    */
EXEC SQL END DECLARE SECTION;
main(argc,argv)
int argc;
char *argv[];
{
/*********************************************************************/
/* Copy the input parameters into the area reserved in the local     */
/* program for SQL processing.                                       */
/*********************************************************************/
dno = *(int *) argv[1];
strcpy(dname, argv[2]);
strcpy(locale, argv[3]);
/*********************************************************************/
/* Issue SQL INSERT to insert a row into SCOTT.DEPT                  */
/*********************************************************************/
EXEC SQL INSERT INTO SCOTT.DEPT VALUES(:dno, :dname, :locale);
/*********************************************************************/
/* Copy SQLCODE to the output parameter list.                        */
/*********************************************************************/
*(int *) argv[4] = SQLCODE;
}

ORAIND

ORAIND is a sample host program that calls a DB2 stored procedure (DB2INS) to insert a row into a DB2 table.

/*********************************************************************/
/* This sample ProC program calls DB2 stored procedure DB2INS to     */
/* insert values into the DB2 user table SCOTT.DEPT.  This calling   */
/* program uses embedded PL/SQL to call the stored procedure.        */
/*********************************************************************/
#include <stdio.h>
EXEC SQL BEGIN DECLARE SECTION;
VARCHAR         username[20];
VARCHAR         password[20];
int             dept_no;
char            dept_name[14];
VARCHAR         location[13];
int             code;
char            buf[11];
int             x;
EXEC SQL END DECLARE SECTION;
EXEC SQL INCLUDE SQLCA;
main()
{
/*********************************************************************/
/* Setup Oracle user id and password                                  */
/*********************************************************************/
strcpy(username.arr, "SCOTT");          /* copy the username */
username.len = strlen(username.arr);
strcpy(password.arr, "TIGER");          /* copy the password */
password.len = strlen(password.arr);
EXEC SQL WHENEVER SQLERROR GOTO sqlerror;
/*********************************************************************/
/* Logon to Oracle                                                   */
/*********************************************************************/
EXEC SQL CONNECT :username IDENTIFIED BY :password;
printf("\nConnected to ORACLE as user: %s\n", username.arr);
/* Delete any existing rows from DB2 table */
EXEC SQL DELETE FROM SCOTT.DEPT@GTWLINK;
EXEC SQL COMMIT;

/*------------------------ begin pl/sql block -----------------------*/
/*********************************************************************/
/* Insert 1 row into DB2 table SCOTT.DEPT by invoking DB2 stored     */
/* procedure DB2INS.  The DB2 stored procedure will perform the      */
/* INSERT.                                                           */
/*                                                                   */
/* SCOTT.DEPT table is defined on DB2 as:                            */
/*                                                                   */
/*    DEPTNO    INTEGER;                                             */
/*    DNAME     CHAR(14);                                            */
/*    LOC       VARCHAR(13);                                         */
/*                                                                   */
/*********************************************************************/
EXEC SQL EXECUTE
BEGIN
:dept_no := 10;
:dept_name := 'GATEWAY';
:location := 'ORACLE';
DB2INS@GTWLINK(:dept_no, :dept_name, :location, :code);
END;
END-EXEC;
/*------------------------- end pl/sql block ------------------------*/
/*********************************************************************/
/* Check the SQLCODE returned from the stored procedures INSERT.     */
/*********************************************************************/
if (code == 0)
printf("DB2INS reports successful INSERT\n");
else
{
printf("DB2INS reports error on INSERT.\nSQLCODE=%d\n",code);
goto sqlerror;
}
/*********************************************************************/
/* Verify row insertion.  Query the data just inserted.              */
/*********************************************************************/
EXEC SQL SELECT deptno, dname, loc INTO
:dept_no, :dept_name, :location
FROM SCOTT.DEPT@GTWLINK WHERE deptno = 10;
printf("\nData INSERTed was:\n");
printf("\ndeptno = %d, dname = %s, loc = %s\n",
dept_no, dept_name, location.arr);
/*********************************************************************/
/* Logoff from Oracle                                                */
/*********************************************************************/
EXEC SQL COMMIT RELEASE;
printf("\n\nHave a good day\n\n");
exit(0);
sqlerror:
printf("\n% .70s \n", sqlca.sqlerrm.sqlerrmc);
EXEC SQL WHENEVER SQLERROR CONTINUE;
EXEC SQL ROLLBACK RELEASE;
exit(1);
}

Index
A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  Z

A

access method transparency (introduction), 1.3.1

accessing

DRDA Servers, 10.9

gateway, 10.8

action items of Oracle Universal Installer, 4.6.4 Advanced Security

CHECKSUM command, 9.5

encryption

export encryption algorithms, 9.5

international version types supported, 9.6

resetting configuration parameters on gateway, 9.7.2

setting test parameters for gateway, 9.6.1

setting test parameters for Oracle integrating server, 9.6.2

setting up for test, 9.6

testing gateway and Oracle integrating server, 9.7.1

function on the gateway, 1.3.3 test error

error 12660, 9.6

testing advanced security encryption, 9.7.1

AGW ADD USERID command, 13.5.1.2 AGW DELETE USERID command, 13.5.1.2 AIX_RS6K, default value for DRDA_LOCAL_NODE_NAME, C.4.17 alias

DB2, C.4.9

objects, DB2, known restrictions, 2.5

ALL_CATALOG view, A.2.1 ALL_COL_COMMENTS view, A.2.2 ALL_CON_COLUMNS view, A.2.3 ALL_CONSTRAINTS view, A.2.4 ALL_DB_LINKS data dictionary view, 11.1.4 ALL_INDEXES view, A.2.5 ALL_OBJECTS view, A.2.7 ALL_SYNONYMS view, A.2.8 ALL_TAB_COMMENTS view, A.2.11 ALL_TABLES view, A.2.9 ALL_USERS view, A.2.12 ALL_VIEWS view, A.2.13 allocation mode, SNA session, DRDA_CMSRC_CM_IMMEDIATE, C.4.7 ALTER session statement, 11.1.2 ANSI-standard SQL

gateway capabilities, 1.3.5

heterogeneous database integration, 1.9.10

API (application program interface), Oracle Net, 9.3 APPC

concurrent connections, 3.1.2

configuring another profile, 10.9

database link behavior, 12.4

DB2/VM, 13.5.1.2

mode definition, 6.4.3.6

password length, 15.3

user ID length, 15.3

APPC VTAM Support (AVS)

also see AVS, 13.5.1.2

mapping user ID, 2.5.1

APPEND command

supported by COPY, 11.8

application

application program interface defined, see API, 9.3

authenticating logons, 13.2

development on the gateway, 1.9.16

portability, 1.9.13

server support, 1.3.3

architecture of the gateway, 1.5 array size

fetch reblocking, 1.9.3

how determined, 12.1.1

AS/400

command DSPRDBDIRE, 5.3.4

configuring communications, 5.3.1

defining user ID, 5.3.2

library name, DRDA_PACKAGE_COLLID, C.4.20

ASCII

code page, D.3

sort order, 12.6.2

tables, known restrictions, 1.9.21

translated from EBCDIC, 12.7.1

US7ASCII, D.3.2.1

US7ASCII, NLS, D.2

authority

CONNECT, 13.5.1.2

execute, 13.5.1.2

autonomy, site, 1.3.14 AVS

also see APPC VTAM Support, 2.5.1

configuring, 5.5.1

DB2/VM, 13.5.1.2

mapping user IDs (DB2/VM), 2.5.1

user ID mapping, 13.5.1.2

B

binary data, non-character, 12.7.1

Bind Package Stored Procedure

DB2/400, 5.3.2

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

DB2/VM, 5.5.2

bind privilege

configuration worksheet, E

DB2/400, 5.3.2

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

DB2/VM, 5.5.2

bind variables

native SQL passthrough, 12.8

restrictions, 2.5.2

BINDADD authority, binding packages on DB2/UDB, 10.4.5 BINDADD privilege

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

DB2/VM, 5.5.2

BINDAGENT privilege

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/VM, 5.5.2

binding the DRDA package

authority of user ID and password

DB2/400, 5.3.2

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

DB2/VM, 5.5.2

backward compatibility, 14.4 configuring the host, 10.4.4 on DB2/UDB, 10.4.5 upgrading from version 3, 10.4.5 bug

bugs fixed in release 10.1.0.2.0, 2.3

debugging

drc values used by Oracle Support Services, 15.1.3

setting trace parameters, 15.4

SQL tracing reduces gateway performance, 11.10

number 205538, 2.5.2

C

call

a CICS or IMS transaction, 12.3.2

DB2 stored procedure

DRDA Server definition, 12.3

look up in server catalog, 12.3.1

DRDA_DISABLE_CALL

default, 10.5.1.1

sample Gateway Initialization File, B.1

empproc stored procedure, 12.3 Oracle Call Interface, 15.1 PL/SQL, 12.3.1 stored procedure

location transparency with synonym, 12.2

null values not passed, 2.5.1

using standard Oracle PL/SQL, 12.2

capabilities, DRDA server, native semantics, 12.6 CCSID

65535 as the default for all tables created, C.4.8

CCSID (coded character set identifiers), defined, D.5

code page mapping facility, D.4

DRDA Server, NLS, D.1

external mapping to supported Oracle character sets, Codepage Map Facility, 1.9.19

changed parameters, 14.3.2 changes in this release

IBM DB2 Version 5.1 EBCDIC and ASCII Tables, 1.9.21

IBM DB2/UDB supported, 1.9.20

read-only support, 1.9.22

CHARACTER SET

clause, client/server configuration, D.2

parameter description, D.1

character sets

and code page map facility, D.4

ASCII, known restrictions, 1.9.21

codepage, DRDA_DEFAULT_CCSID specifies default CCSID, C.4.8

EBCDIC, known restrictions, 1.9.21

supported, codepage map facility, 1.9.19

character strings

converting character string data types, 12.7.2

performing character string operations, 12.7.1

checklist

DRDA Server configuration, 5.1

gateway configuration, 10.1

gateway installation, 4.3

Oracle Net, 9.1

CHECKSUM command

also see Advanced Security, 1.3.3

Oracle Net, Advanced Security Encryption, 9.5

CICS transaction, 12.3.2 clauses

CHARACTER SET, client/server configuration, D.2

CONNECT TO, 11.1.1

GROUP BY, 12.6.3

HAVING, 12.6.3

ORDER BY, 12.6.3

SQL

DELETE, 12.7.7

INSERT, 12.7.7

SELECT WHERE, 12.7.7

UPDATE, 12.7.7

TO_DATE, 12.7.7 USING, 11.1.1 VALUES, 12.7.7 WHERE

compatible for all versions of DRDA Server, 12.6.3

SQL limitations, Oracle ROWID column, 2.5.2

WHERE CURRENT OF CURSOR, ROWID column, 2.5.2 client, defined in gateway architecture, 1.5 code page map facility

for data translation, D.4

code tracing, C.4.41 codepage map facility

configuring support for character sets, 2.5.1

supported by gateway, 1.9.19

coercion of data, defined, 12.6 collection privilege - CREATE IN

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/VM, 5.5.2

collection privilege - CREATETAB, DB2/OS390, 5.2.2 column

date columns function, 12.7.7

Oracle ROWID, 2.5.2

supported in a result set, 1.9.8

commands

AGW ADD USERID, 13.5.1.2

AGW DELETE USERID, 13.5.1.2

CHECKSUM

advanced security, 1.3.3

supported by Oracle Net, 9.5

COPY

known restriction for INSERT, 2.5

SQL*Plus command, 11.8

CREATE DATABASE LINK, 5.5.2 EXECUTE, 1.3.9.1 EXPLAIN PLAN, 15.4.1 INSERT, known restriction, 2.5 commit confirm protocol, 1.3.13 Communication Database (CDB) tables, DDF, 5.2.5 communications requirements, 3.2.3 compatible SQL set operators and clauses, 12.6.3 concatenation restrictions, 2.5.1 concurrent connections

APPC, 3.1.2

TCP/IP, 3.1.2

configuring

additional DRDA Servers, 10.9

AS/400 communications, 5.3.1

AVS, 5.5.1

binding DRDA package, 10.5

checklist for gateway, 10.1

checklists for DRDA Server, 5.1

DB2/400, 5.3

DB2/OS390, 5.2

DB2/UDB, 5.4

list of parameters needed to configure the gateway, E

Oracle integrating server, 10.7

Oracle Net, 9.4

OS/390 (MVS) VTAM, 5.2.1

other Oracle servers, 10.8

SNA server, creating profiles, 6.3, 7.3

TCP/IP

for AS/400, 5.3.1

for DB2/VM, 5.5.1

for MS Windows, 8.2

for OS/390, 5.2.1

VM VTAM on DB2/VM, 5.5.1 workstation for gateway, 10.4 CONNECT authority

binding packages on DB2/UDB, 10.4.5

DB2/UDB, 5.4.2

user ID mapping on DB2/VM, 13.5.1.2

CONNECT BY not supported, known restrictions, 2.5.2 CONNECT TO clause, 11.1.1 connection

definition, 6.4.3.4

testing, 6.5, 7.5

conversion

data types, 12.7

errors, C.4.8

convert

character string data types, 12.7.2

character string operations, 12.7.1

DATE, 12.7.4.2

floating point to integer, 12.7.8

inbound user ID, 13.5.1.2

into most suitable data type, 12.7.10

to the numeric data type, 12.7.8

converter, protocol, 1.3.3 COPY

copying data from the DRDA server, 11.9

copying data from the Oracle server, 11.8

privilege

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/VM, 5.5.2

SQL*Plus COPY command

Oracle server to DRDA server, 11.8

substituted for INSERT, 2.5

COS function, 12.5.3 COUNT function, 12.7.9 CPI-C routine, 15.1.4 CPI-C Symbolic Destination Names, 6.4.3.8 CREATE command, supported by COPY, 11.8 CREATE DATABASE LINK

command, binding package on DB2/VM, 5.5.2

statement, defining path to remote database, 11.1.1

CREATE DATABASE statement, client/server configuration, D.2 CREATE IN privilege

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/VM, 5.5.2

CREATE PUBLIC DATABASE LINK privilege

binding the DRDA gateway package, 10.4.4

configuring Oracle integrating server, 10.7.1

CREATE TABLE statement, 1.3.8 CREATEIN privilege, DB2/UDB, 5.4.2 CREATETAB authority, 10.4.5 CREATETAB privilege

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

creating a database link, 11.1.1 cursor

defining the number of, 12.10

number of cursors, DRDA_PACKAGE_SECTIONS, C.4.24

stability, DRDA_ISOLATION_LEVEL, C.4.16

D

data coercion, defined, 12.6

data control language (DCL), 1.3.7

data definition language (DDL), 1.3.6

data dictionary

support, 10.5.2

using, 12.9.1

views

ALL_DB_LINKS, 11.1.4

considerations for migration from previous releases, 14.4

list and descriptions, A.2

not supported for DB2/VM, A.1

Oracle Emulation on DRDA Server, 12.9

supported for DB2/OS390, DB2/UDB, and DB2/400 servers, A.1

USER_DB_LINKS shows defined database links, 11.1.4

data storage transparency (introduction), 1.3.1 data type

column (ALL_TAB_COLUMNS), A.2.10

column (USER_TAB_COLUMNS), A.2.26

conversion

between Oracle and DRDA, 1.7

control over, 12.7.8

converting character string data types, 12.7.2

gateway mapping and restrictions, 12.7

performing character string operations, 12.7.1

date, 2.5.1 differences between Oracle server and DRDA databases, 12 DRDA Server data types list, 12.7 known restrictions, 2.5.1 mapping, 12.7 numeric

zoned decimal field, 12.7.10

Oracle data types RAW and LONG RAW, 12.7.1 performing character string operations, 12.7.1 restrictions, 12.7 size and value limitations, 12.7 supported by IBM DRDA, 12.7.4 supported by IBM DRDA databases, 12.7.4 data types

DATE, as calendar date only, 12.7.4

GRAPHIC, 12.7.3

LONG

converting character string data types, 12.7.2

known restrictions, 2.5.1

LONG RAW, translating ASCII to EBCDIC, 12.7.1 Oracle and IBM DATA data types are mapped to each other, 12.7.4.2 Oracle and IBM DATE, 12.7.4.2 processing TIME data types to Oracle DATE, 12.7.4.1 RAW

CCSID 65535, C.4.8

translating ASCII to EBCDIC, 12.7.1

TIME, time of day only, 12.7.4 TIMESTAMP, combining calendar data and time of day, 12.7.4 VARCHAR, 12.7.2 database

authorities - CONNECT, BINDADD, and CREATETAB, 5.4.2

catalogs, 12.9

link

behavior, 12.4

binding DRDA gateway package, 10.4.4

creating, 11.1.1

defining and controlling, 13.3

dropping links, 11.1.3

examining, 11.1.4

guidelines, 11.1.2

limits, 11.1.5

processing, 11.1

public, 10.7.1

suffix, 12.1

to identify the gateway, 1.7

native tool, 10.5.2 triggers, 1.3.2 date

2 or 4 digits, 12.7.5

arithmetic, known restrictions, 2.5.1

columns function, 12.7.7

data types and DRDA server restriction, 2.5.1

data types supported by IBM DRDA, 12.7.4

date handling has two categories, 12.7.5

gateway local date exit for DB2 ISO format, 12.7.6

HS_NLS_DATE_FORMAT

parameter, date handling, 12.7.5

patterns, 12.7.6

operations, 12.7.4 statements, SELECT, INSERT, UPDATE, DELETE, 12.7.5 TO_DATE function

date handling, 12.7.5

preprocessed in SQL, 12.7.7

DATE data type

implementation, 12.7.4

processing DATE data, 12.7.4.2

DB_DOMAIN parameter, 2.5.1 DB2

02pcg.sql granting authority, 10.5.2.5

alias objects, known restrictions, 2.5

aliases, not compatible with DRDA_DESCRIBE_TABLE, C.4.9

CICS, IMS, 12.3.2

data access, 1.3.9.1

Distributed Data Facility (DDF), 5.2.5

DRDA_DESCRIBE_TABLE compatibility, C.4.9

IBM DB2 version 5.1 ASCII Tables, 1.9.21

native SQL, 1.3.8

native stored procedures, 1.3.9.2

procedural feature considerations, 12.3.2

SPUFI utility, 5.2.5

SQL statements, 12.8.2

statements, CREATE TABLE, 1.3.8

stored procedures, considerations for use, 12.3.2

with OS/390, 5.2

DB2/400

catalog view, 12.9.1

configuring the DRDA Server, 5.3

data dictionary views supported by gateway, A.1

defining user ID, 5.3.2

DRDA_DEFAULT_CCSID, C.4.8

DRDA_ISOLATION_LEVEL, C.4.16

DRDA_OPTIMIZE_QUERY, C.4.19

DRDA_PACKAGE_COLLID, C.4.20

userid mapping, different capability, 13.5.1.3

DB2INS sample DB2 stored procedure, G.1 DB2/OS390

catalog view, 12.9.1

configuring, 5.2

data dictionary views supported by gateway, A.1

DRDA_ISOLATION_LEVEL, C.4.16

DRDA_OPTIMIZE_QUERY, C.4.19

userid mapping, 13.5.1.1

V6, V7 and V8 stored procedures supported, 1.9.18

with SPUFI, 10.5.2

DB2/UDB

catalog view, 12.9.1

configuring, 5.4

configuring the DRDA Server, 5.4

data dictionary views not supported, A.1

DRDA_ISOLATION_LEVEL, C.4.16

DRDA_OPTIMIZE_QUERY, C.4.19

grant authority, 10.5.2.5

known restrictions, 2.5.1

ORACLE2PC table, binding packages, 10.5.1.2

supported, changes in this release, 1.9.20

userid mapping, 13.5.1.4

DB2/VM

catalog view, 12.9.1

configuring, 5.5

data dictionary views not supported, A.1

database and SQL functions, 12.5.8

DRDA_ISOLATION_LEVEL, C.4.16

DRDA_OPTIMIZE_QUERY, C.4.19

DRDA_PACKAGE_OWNER, C.4.23

instance, DRDA location name, 5.5.4

server machine, 13.5.1.2

userid mapping, 13.5.1.2

DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE function

limited to nonqueries, 12.8

native SQL passthrough, 12.8

syntax, 12.8.2

DD basic tables, known restrictions, 2.5.1 DDF

subsystem, 5.2.1

DDL statement

native SQL passthrough, 12.8

number of rows affected, 12.8.2

debugging

error codes, 15.1.3

SQL tracing, 15.4

your application, 11.10

de-installing the gateway, 4.7.1 DELETE

known restrictions, 2.5.2

operation, 12.1

SQL clause, 12.7.7

statement

dates, 12.7.5

native SQL passthrough, 12.8

transaction semantics, 1.7.1

with read-only gateway, 11.6 Dependent LU, 6.3.1, 7.3.1 DESCRIBE

character string operations, 12.7.1

diagnostic parameter, C.4.39 dictionary

mapping, 1.3.4

tables, 12.9

DICTIONARY view, A.2.15 disk space requirements, 3.1.4 distributed

applications, support for, 1.9.15

database, 9.3.2

distributed query optimizer (DQO), better performance of distributed queries, 11.5

operations, DB2, 5.2.5

processing, 9.3.1

queries

example of, 11.5.1

two-phase commit, 11.5.2

transaction, DRDA_RECOVERY_USERID, C.4.27 distributed query optimizer (DQO), DRDA-specific parameters, C.4.19 double-byte support, D.5 DQO

also see distributed query optimizer, 11.5

DRDA-specific parameters, C.4.19

drc error code, 15.1.3 DRDA

catalog, 12.9.2

database requirements, 3.2.2

defining number of cursors, 12.10

location name

for DB2/UDB instance, 5.4.4

for DB2/VM instance, 5.5.4

session security options, 13.5.1.1 DRDA Application Server Function, 1.9.12 DRDA Server

accessing, 10.9

capabilities, native semantics, 12.6

CCSID

character set to store data in DRDA database, D.1

gateway code page map facility, D.4

parameters needed for NLS, D.1

character sets, known restrictions, 2.5.1 configuring

DB2/400, 5.3

DB2/OS390, 5.2

DB2/UDB, 5.4

DB2/VM, 5.5

considerations for binding packages, 14.4 database link behavior, 12.4 functions, native semantics, 12.6 gateway architecture definition, 1.5 Hostname or IP Address (configuring TCP/IP, worksheet), E port number (TCP/IP), 8.1.1 Service Port Number (configuring TCP/IP, worksheet), E stored procedures, native to DRDA server, 12.3 DRDA_CAPABILITY parameter, 12.6 DRDA_CMSRC_CM_IMMEDIATE parameter, description, C.4.7 DRDA_CODEPAGE_MAP parameter, D.4 DRDA_COMM_BUFLEN parameter, description, C.4.4 DRDA_CONNECT_PARM

(SNA format) parameter, description, C.4.5

(TCP/IP format) parameter, description, C.4.6

configuring IBM Communication Server, 7.4.1.2

configuring Microsoft SNA server or host server, 6.4.3.8

parameter

communication errors, 15.1.4

configuring the gateway for TCP/IP, 8.2

DRDA_DEFAULT_CCSID parameter, description, C.4.8 DRDA_DESCRIBE_TABLE parameter

description, C.4.9

known restrictions, 2.5

DRDA_DESCRIBE_TABLE=FALSE initialization parameter, 2.5 DRDA_DISABLE_CALL parameter

binding the DRDA gateway package, 10.5.1.1

description, C.4.10

DRDA_FLUSH_CACHE parameter, description, C.4.11 DRDA_GRAPHIC_LIT_CHECK parameter, description, C.4.13 DRDA_GRAPHIC_PAD_SIZE parameter, description, C.4.12 DRDA_GRAPHIC_TO_MBCS parameter, description, C.4.14 DRDA_ISOLATION_LEVEL parameter, description, C.4.16 DRDA_LOCAL_NODE_NAME parameter, description, C.4.17 DRDA_MBCS_TO_GRAPHIC parameter, description, C.4.18 DRDA_OPTIMIZE_QUERY parameter

description, C.4.19

DQO capability turned ON and OFF, 11.5

DRDA_PACKAGE_COLLID parameter

description, C.4.20

errors detected by server database, 15.1.5

DRDA_PACKAGE_CONSTOKEN parameter, description, C.4.21 DRDA_PACKAGE_NAME parameter

description, C.4.22

detecting errors, 15.1.5

value must be unique, 10.5.1.1

DRDA_PACKAGE_OWNER parameter, description, C.4.23 DRDA_PACKAGE_SECTIONS parameter

description, C.4.24

number of open cursors at IBM database, 12.10

DRDA_READ_ONLY parameter

description, C.4.25

read-only gateway, 11.6

DRDA_RECOVER_USERID parameter

DB2/400, 5.3.3

DB2/OS390, 5.2.3

DRDA_RECOVERY_PASSWORD parameter

DB2/OS390, 5.2.3, 5.3.3

DB2/UDB, 5.4.3

DB2/VM, 5.5.3

description, C.4.26

DRDA_RECOVERY_USERID parameter

DB2/400, 5.3.3

DB2/UDB, 5.4.3

DB2/VM, 5.5.3

description, C.4.27

DRDA_REMOTE_DB_NAME parameter, description, C.4.28 DRDA_SECURITY_TYPE parameter, description, C.4.29 DROP DATABASE LINK statement, 11.1.3 dropold.sql script, 10.5.2.2 DSPRDBDIRE command, 5.3.4 dynamic dictionary mapping, 1.3.4

E

EBCDIC

character set support, D.3.2.1

code page, D.3

DRDA server CCSID, D.7

sort order, 12.6.2

tables, known restrictions, 1.9.21

translated to ASCII, 12.7.1

EMP

creating system-wide synonym for EMP file, 11.4

table, 11.8

empproc

stored procedure, 12.3

encryption

export encryption algorithms, 9.5

types for Advanced Security, 9.6

environment

distributed, 12.2

heterogeneous, replicating in, 11.7

variable, NLS_LANG, D.2

environmental variable

NLS_LANG, D.1

ORA_NLS33, D.1

errd

error array returned from DRDA server database, 15.1.5

example of translated, mapped error, 15.2

example, retrieving data, 11.2.3

errmc

(error tokens), 15.1.5

communication errors, 15.1.4

errmc field lists any error tokens, 15.1.3

example of translated, mapped error, 15.2

example, retrieving data, 11.2.3

error

12660 (test error for Advanced Security), 9.6

basic description, 15.1

change

ORA-09100 to ORA-28500, 15.1.3

ORA-09101 to ORA-28501, 15.1.3

codes

drc, 15.1.3

grc, 15.1.3

communication, 15.1.4 condition, 15.1 conversion, C.4.8 date, D.3.2.3 detected

by gateway, 15.1.2

by integrating Oracle instance, 15.1.1

by server database, 15.1.5

in DRDA software, 15.1.3

drc= field

-300xx, 15.3

-7xx, 15.3

HGO-00706, 15.1.2 host database, 15.3 interpreting error messages, 15.1 mapped sqlstate, 15.2 messages & codes, main chapter, 15 messages, Oracle LONG data type larger than 32740 bytes, 12.7.2 number, return code, 15.1 ORA-00001, index constraint violated, 15.2 ORA-00942

object does not exist, 15.2

object name too long, 15.2

ORA-01017, logon denied, 15.2 ORA-01031, insufficient privileges, 15.2 ORA-01460, invalid CCSID, 15.2 ORA-01476, divide by zero, 15.2 ORA-02019, undefined database link name is specified, 15.1.1 ORA-28500

was ORA-09100, 15.1.3

detected by server database, 15.1.5

example, collection ID or package name not recognized, 15.1.5

ORA-28501

was ORA-09101, 15.1.4

communication error, 15.1.4

Side Information Profile not defined, 15.1.4

ORA-28527, conversion errors, C.4.8 ORA-9100 to ORA-9199, reserved for generic gateway layer, 15.1.1 Oracle error code for mapped errors, 15.2 server database, 15.1.5 specific error codes, 15.3 tokens listed by errmc for errors

detected by DRDA gateway, 15.1.3

detected by server database, 15.1.5

translation, 12.7.1 while binding the gateway package, 10.4.4 with Native Semantics, 12.6 errp

example, retrieving data, 11.2.3, 15.1.3, 15.1.5, 15.2

EXCEPT set operator, 12.6.3 execute authority

DB2/400, 13.5.1.3

DB2/UDB, 13.5.1.4

DB2/VM, 13.5.1.2

on the gateway DRDA package, 13.5.1.2

EXECUTE command, 1.3.9.1 EXECUTE privilege

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

DB2/VM, 5.5.2

exits, gateway local date, 12.7.6 EXPLAIN PLAN command, 15.4.1 EXPLAIN_PLAN table, features of the gateway, 1.9.9 export encryption algorithms, 9.5

F

FDS_CLASS parameter, description, C.4.30

FDS_CLASS_VERSION parameter, description, C.4.31

FDS_INSTANCE parameter, description, C.4.32

features of the gateway

main topic, 1.9

application development and end-user tools, 1.9.16

application portability, 1.9.13

columns supported in a result set, 1.9.8

distributed applications supported, 1.9.15

EXPLAIN_PLAN improvement, 1.9.9

fetch reblocking, 1.9.3

heterogeneous database integration, 1.9.10

heterogeneous services architecture, 1.9.1

large base of data access, 1.9.12

minimum impact on existing systems, 1.9.11

Native Semantics, 1.9.7

Oracle Database 10g passthrough supported, 1.9.4

Oracle snapshot, 11.7.2

performance enhancements, 1.9.2

remote data access, 1.9.14

retrieving result sets through passthrough, 1.9.5

support for TCP/IP, 1.9.6

fetch array size, with HS_FDS_FETCH_ROWS, C.4.33 fetch reblocking

features of the gateway, 1.9.3

supported with HS_RPC_RETCH_REBLOCKING, 12.1.1

fetched date, ORA_MAX_DATE parameter, description, C.4.37 fields

errmc, lists any error tokens, 15.1.3

errp, indicates program that detected error, 15.1.3

files

initsid.ora

invalid ORA_MAX_DATE specified, 15.3

parameter not recognized, 15.1.5

installation log file, verifying successful installation, 4.6.5 listener.ora

configure additional instance, 10.9

IPC key defined in, 9.4.2

member name, 11.3 sample

gateway initialization, tnsnames.ora, listener.ora, B

listener.ora, B.3

tnsnames.ora

configuring additional DRDA Server instance, 10.9

modifying the file, 9.4.2

VSAM, 12.3.2 FOR BIT DATA

DRDA_DEFAULT_CCSID, C.4.8

indicates RAW or LONG RAW, 12.7.1

option, 12.7.1

free session, DRDA_CMSRC_CM_IMMEDIATE, C.4.7 functions

COS, 12.5.3

COUNT, 12.7.9

DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE, 12.8.2

DRDA server, native semantics, 12.6

GROUPBY, 12.6.2

HAVING, 12.6.2

ROWID, with UPDATE or DELETE, 2.5.2

SQL, SUBSTR, 12.6

SUBSTR

known restrictions, 2.5.1

TO_DATE

entering twenty-first century dates, 12.7.5

Oracle function, preprocessed in SQL, 12.7.7

processing DATE data, 12.7.4.2

WHERE, 12.6.2

G

g4ddtab.sql script, 10.5.2.3

g4ddview.sql script, 10.5.2.3

gateway

access, 10.8

advantages

migration and coexistence, 1.3.15

security, 1.3.16

server technology and tools, 1.3.11

site autonomy, 1.3.14

two-phase commit and multi-site transactions, 1.3.13

use of SQL, 1.2.1

application tools, 1.9.16 architecture, 1.5 benefits of integration with Oracle Database 10g server, 1.3.3 configuration, 10.3 definition of terms, 1.4 de-installing, 4.7.1 features, main topic, 1.9 gateway and Oracle integrating server not on same host, 1.5 installing, 4.6 interface function, 1.7 local date exit, 12.7.6 logging, LOG_DESTINATION, C.4.36 migration problems, backout considerations, 14.2 parameter, 5.5.4 performance, 12.6 performance enhancements, 1.9.2 service name entries in the tnsnames.ora, 14.5 SQL differences, 1.7.1 stored procedures (Oracle and non-Oracle), 1.3.9 supported languages

CCSID, D.1

codepage map facility, D.4

tracing

LOG_DESTINATION, C.4.36

SQL statements, 11.10

Gateway Initialization File

parameter

list, C.4

new since V4 gateway, 14.3.1.1

reported errors, 10.4.4

sample, B.1 Gateway Initialization Parameter, DRDA_READ_ONLY, 11.6 Gateway System Identifier (SID), defined, 10.2 GCS virtual machine, 13.5.1.2 GLOBAL_NAMES

known restrictions, 2.5.1

GRANT

DB2/VM security, 13.5.1.2

statement, synonyms and views, 10.7.2

granting authority to a package for DB2, 10.5.2.5 GRAPHIC data type, 12.7.3 graphic string operations, unsupported, 12.7.3 grc error code, 15.1.3 GROUP BY clause, 12.6.3 GROUPBY function, 12.6.2 GTW$_BIND_PKG

configuring the host, 10.4.4

gateway package considerations, 10.5

H

hardware requirements, memory, 3.1.2

HAVING

clause compatible for all versions of DRDA Server, 12.6.3

SQL Functions That Can Be Disabled, 12.6.2

heterogeneous database integration, 1.9.10 Heterogeneous Services (HS)

see also HS, 1.2

component of the Oracle Database 10g server, 1.2

parameter syntax and usage, C.3

HGO-00706 error, 15.1.2 host

architecture, 1.5

components when installed on gateway, 1.6

creating an independent process, 1.6

database error, 15.3

networking needs, 3.2.5

relationship to gateway and Oracle server, 1.5

variable

converting character string data types, 12.7.2

moving data between applications and the database, 12.7

HS (Heterogeneous Services)

architecture features, 1.9.1

Oracle Net considerations, 14.5

HS= (TNSNAMES parameter for Oracle Net)

gateway migration problems, 14.2

modify tnsnames.ora file, 9.4.2

HS_DB_DOMAIN parameter, 2.5.1 HS_DB_NAME parameter, 2.5.1 HS_FDS_FETCH_ROWS parameter, description, C.4.33 HS_LANGUAGE parameter, description, C.4.34 HS_NLS_DATE_FORMAT

NLS parameters for initsid.ora file, D.3.2.3

parameter, 12.7.5

support, 12.7.6

HS_NLS_DATE_LANGUAGE, D.3.2.4 HS_NLS_NCHAR

parameter description, C.4.35

parameters in the Gateway Initialization File, D.3.2.2

HS_RPC_FETCH_REBLOCKING parameter

fetch reblocking described, 12.1.1

gateway features, 1.9.3

HS_RPC_FETCH_SIZE parameter

fetch reblocking described, 12.1.1

gateway features, 1.9.3

I

IBM Communication Server

definitions, 7.4.1

server selection, 7.4.1.1

implementation, gateway components, 1.6 implicit data conversion, 12.6 implicit protocol conversion, 1.3.3 IMS transaction, 12.3.2 IN and OUT columns, multi-byte support, D.5 inbound connections

processing, 13.5

Independent LU

configuring IBM Communication Server, 7.3.1

configuring Microsoft SNA Server, 6.3.1

initdrdahoa1.ora

sample Gateway Initialization File, B.1

initialization parameters

new since V4 gateway, 14.3.1.1

initsid.gtw file

sample, 10.4.1

initsid.gtwboot

file, migrating, 14.1.2

parameters moved to initsid.ora, 10.4

initsid.ora file

containing initsid.gwtboot parameters, 10.4

invalid ORA_MAX_DATE specified, 15.3

migrating, 14.1.2

NLS parameters, D.3.2

parameter not recognized, 15.1.5

parameters have changed format, 14.1.3

sample, 10.4.1

simplified syntax, see Appendix C, 10.4

tailoring, 10.4.2.1

input bind variables, 12.7.4.2 INSERT

command

known restriction, 2.5

supported by COPY, 11.8

operation, 12.1 Oracle SQL command, known restrictions, 2.5 SQL clause, 12.7.7 statement

dates, 12.7.5

native SQL passthrough, 12.8

transaction semantics, 1.7.1

with read-only gateway, 11.6 installation

checklists

configuring the gateway, 10.1

DRDA Server, 5.1

gateway, 4.3

Oracle Net, 9.1

configuring multiple DRDA Servers

details, 10.9

overview, 4.4

configuring multiple integrating servers

details, 10.8

overview, 4.4

from CD, 4.6 log file, INSTALL.LOG, 4.6.5 overview, 4.4 INSTALL.LOG, 4.6.5 internal tracing, C.4.40 Internet and intranet support, 1.3.3 INTERSECT, set operators, 12.6.3 IPC adapter, B.3 ISO standard

SQL, 1.3.5

isolation level, DRDA_ISOLATION_LEVEL, C.4.16

J

JOIN capability, 1.3.2

JOIN SQL statement, 12.1

K

keywords

LISTENER, sample listener.ora file, B.3

known restrictions

main topic, 2.5

accessing DB2 alias objects, 2.5

AVS mapping user IDs, 2.5.1

bind variables become SQL parameter markers, 2.5.2

binding the DRDA gateway package on DB2/UDB, 2.5.1

CONNECT BY not supported, 2.5.2

data type limitations, 2.5.1

date arithmetic, 2.5.1

DD basic tables and views, 2.5.1

dictionary views not provided for DB2/VM, 2.5.1

DRDA server character sets, 2.5.1

GLOBAL_NAMES parameter, 2.5.1

LONG data type in SQL*Plus, 2.5.1

null values and stored procedures, 2.5.1

Oracle ROWID column, 2.5.2

row length, 2.5.1

row length limitation, 2.5.1

SAVEPOINT, 2.5.1

single gateway instances per DRDA network interface, 2.5.1

string concatenation, 2.5.1

SUBSTR function post-processed, 2.5.1

L

LANGUAGE parameter, D.3.2.1

languages

SQL*Plus, 1.3.12

tools supported through the gateway, 1.3.10

link

also see Database Link, 12.4

service definition, 6.4.3.3

linkage conventions

SIMPLE with nulls, 12.3.2

listener

sample Oracle Net listener.ora file, B.3

LISTENER keyword, sample listener.ora file, B.3 listener.ora file

configuring additional DRDA Server instances, 10.9

IPC key defined, 9.4.2

sample, B.3

literal

character literals, 12.7.4.1

date, 12.7.4.2

specific data type, 12.7

TO_DATE, 12.7.7

Local LU definition, 6.4.3.5 location transparency (introduction), 1.3.1 log file, installation, verifying success, 4.6.5 LOG_DESTINATION parameter

description, C.4.36

used with ORACLE_DRDA_TRACE, C.4.40

logging, LOG_DESTINATION, C.4.36 LONG columns, known restrictions, 2.5.1 LONG data type

converting character string data types, 12.7.2

known restrictions, 2.5.1

LONG RAW datat ype, translating ASCII to EBCDIC, 12.7.1 LUs

dependent, 7.3.1

independent, 7.3.1

independent and dependent, 6.3.1

local definition, alias, network name, 6.4.3.5

remote definition, 6.4.3.7

M

mapped sqlstate errors, 15.2

mapping user IDs, known restrictions, 2.5.1

memory, hardware requirements, 3.1.2

Microsoft Windows Sockets, network attachment, 3.1.3

migration

defined, 14.1

migrating the gateway instance, 14.4

obsolete parameters, 14.3.4

problems, backout considerations, 14.2

MINUS

set operator, 12.6.3

Mobile Agents, 1.3.3 Mode definition, 6.4.3.6 multi-byte support, D.5

N

National Language Support

initsid.ora parameters, D.3.2

overview, D

Native Semantics

main topic, 12.6

gateway features, 1.9.7

parameters, 12.6.3

with SUBSTR function, 2.5.1

native SQL passthrough, 12.8 network

configuration tool, 8.2

Oracle Net configuration, 9.4

requirements, 3.1.3

transparency (introduction), 1.3.1

NLS

also see National Language Support, D

DRDA server character sets

codepage map facility, D.4

parameters needed for NLS processing, D.1

NLS parameters, configuration on client and Oracle servers, D.2 NLS_LANG

environment variable

client-server configuration, D.2

parameters needed for NLS processing, D.1

server-side parameter, D.1 non-character binary data, 12.7.1 null

rows, mapping the COUNT function, 12.7.9

values

known restrictions, 2.5.1

mapping the COUNT function, 12.7.9

number of cursors, DRDA_PACKAGE_SECTIONS, C.4.24 numbers, concatenation restrictions, 2.5.1 numeric data type

conversion, destination column, 12.7.8

zoned decimal operations, 12.7.10

O

o2pc.sql

binding the DRDA gateway package, 10.5.2.6

two-phase commit processing, 11.5.2

obsolete parameters since V4 gateway, 14.3.4 open cursors, at the IBM database, 12.10 OPEN_LINKS parameter, 11.1.5 operating system requirements, 3.2.1 operating system transparency (introduction), 1.3.1 operations, SELECT, INSERT, UPDATE, DELETE, 12.1 operators

UNION, 12.6.3

UNION ALL, 12.6.3

option

binding packages, 10.4.5

data dictionary views, 12.9

date format string, 12.7.5

DRDA session security, 13.5.1.1

FOR BIT DATA, 12.7.1

Oracle server, 1.5

read-only

gateway configuration, 1.3.13

no updates permited by gateway, 11.6

replicating, 11.7 security conduct, 13.5 service port number, DRDA_CONNECT_PARM, C.4.6 SNA security

configuring IBM Communication Server, 7.7

configuring Microsoft SNA Server or Host Integration Server, 6.7

SQL functions that can be disabled, 12.6.2 SQL functions that can be enabled, 12.6.1 SQL*Plus COPY command, 11.8 ora

listener.ora file, 10.9

tnsnames.ora file, 9.4.2

ORA_MAX_DATE parameter, description, C.4.37 ORA_NLS33 parameter

description (default value), C.4.38

needed in system environment, D.1

ORA-00001 error, index constraint violated, 15.2 ORA-00942 error

object does not exist, 15.2

object name too long, 15.2

ORA-01017 error, logon denied, 15.2 ORA-01031 error, insufficient privileges, 15.2 ORA-01460 error, invalid CCSID, 15.2 ORA-01476 error, divide by zero, 15.2 ORA-02019 error, undefined database link name is specified, 15.1.1 ORA1 Oracle instance, 12.2 ORA-28500 error

was ORA-09100, 15.1.3

example, collection ID or package name not recognized, 15.1.5

ORA-28501 error

was ORA-09101, 15.1.3

communication error, 15.1.4

Side Information Profile not defined, 15.1.4

ORA-28527, conversion errors, C.4.8 ORA-9100 error, 15.1.1 ORA-9199 error, 15.1.1 Oracle

error code, mapped errors, 15.2

error number or return code, 15.1

products compatibility, 1.8

RAW data type, C.4.8

snapshots, 11.7.2

stored procedure, defined, 12.2

Oracle Database 10g server

introduction, 1.2

relationship to host, 1.5

services

list, 1.3.2

database triggers, 1.3.2

distributed capabilities, 1.3.2

distributed query optimization, 1.3.2

SQL, 1.3.2

stored procedures, 1.3.2

two-phase commit protection, 1.3.2

Oracle integrating server

architecture, 1.5

configuration, 10.7

defined in gateway architecture, 1.5

gateway and Oracle integrating server not on same host, 1.5

requirements, 3.2.4

Oracle Net

and application development, 1.9.16

and remote data access, 1.9.14

and server coexistence, 1.5

API, 9.3

compatibility with SQL*Net, 9.2

configuring, 9.4

distributed

database, 9.3.2

processing, 9.3.1

editing to set up security test, 9.6.1 gateway and Oracle integrating server not on same host, 1.5 gateway migration problems, 14.2 Heterogeneous Services (HS) facility, 9.2 introduction, 9.2 migration considerations, 14.5 operating system authentication, 13.2 overview, 9.3 purpose, 1.6 requirements, 3.2.5 sample files, B sample listener.ora file, B.3 support (introduction), 1.3.11 support for CHECKSUM and encryption, 9.5 terminology, 9.3.3 Oracle ROWID column, 2.5.2 Oracle ROWID function, with UPDATE or DELETE, 2.5.2 ORACLE_DRDA_TCTL parameter, description, C.4.39 ORACLE_DRDA_TRACE parameter, description, C.4.40 ORACLE_HOME, preinstallation and caution notice, 4.5 ORACLE2PC table

before binding gateway package, 10.5.1.2

binding packages on DB2/UDB, 10.4.5

DB2/400, 5.3.2

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

DB2/UDB, granting authority to package, 10.5.2.5

DB2/VM, 5.5.2

distributed DRDA transactions, 11.5.3

DRDA_PACKAGE_OWNER description, C.4.23

ORADRDA.ORACLE2PC table, two-phase commit, 11.5.2 ORAIND sample DB2 stored procedure, G.2 oraproc1, stored procedure, 12.2 oraproc2, stored procedure, 12.2 ORARECOV user ID

DB2/400, 5.3.3

DB2/OS390, 5.2.3

DB2/UDB, 5.4.3

DB2/VM, 5.5.3

DRDA_RECOVERY_USERID description, C.4.27

ORA2 Oracle instance, 12.2 ORDER BY clause, 12.6.3 OS/390 (MVS) VTAM, configuring, 5.2.1

P

package

collection id, DRDA_PACKAGE_COLLID, C.4.20

consistency token, DRDA_PACKAGE_CONSTOKEN, C.4.21

privileges - BIND and EXECUTE, DB2/UDB, 5.4.2

privileges - BIND, COPY, and EXECUTE

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/VM, 5.5.2

packed decimal, 12.7.10 parameter

changed, 14.3.2

checking settings, 10.5.1.1

diagnostic, C.4.39

gateway, 5.5.4

list of parameters needed to configure the gateway, E

Native Semantics, 12.6.3

new since V4 gateway, 14.3.1.1

obsolete since V4 gateway, 14.3.4

parameter syntax and usage, C.3

renamed since V4 gateway, 14.3.3

parameters

DB_DOMAIN, 2.5.1

DRDA_CAPABILITY, 12.6

DRDA_CODEPAGE_MAP

described, C.4.3

mapping IBM CCSID, D.4

DRDA_CONNECT_PARM

configuring IBM Communication Server, 7.4.1.2

configuring Microsoft SNA server or host server, 6.4.3.8

configuring the gateway for TCP/IP, 8.2

DRDA_DESCRIBE_TABLE, known restrictions, 2.5 DRDA_DISABLE_CALL, 10.5.1.1 DRDA_PACKAGE_NAME, 10.5.1.1 DRDA_PACKAGE_SECTIONS, open cursors, 12.10 DRDA_READ_ONLY, read-only gateway, 11.6 DRDA_RECOVERY_PASSWORD

DB2/400, 5.3.3

DB2/OS390, 5.2.3

DB2/UDB, 5.4.3

DB2/VM, 5.5.3

DRDA_RECOVERY_USERID

DB2/400, 5.3.3

DB2/OS390, 5.2.3

DB2/UDB, 5.4.3

DB2/VM, 5.5.3

FDS_CLASS, description, C.4.30 FDS_CLASS_VERSION, description, C.4.31 FDS_INSTANCE, description, C.4.32 Gateway Initialization File

DRDA_CACHE_TABLE_DESC, C.4.1

DRDA_CAPABILITY, C.4.2

DRDA_CMSRC_CM_IMMEDIATE, C.4.7

DRDA_CODEPAGE_MAP, C.4.3

DRDA_COMM_BUFLEN, C.4.4

DRDA_CONNECT_PARM, 8.2, 15.1.4

DRDA_CONNECT_PARM (SNA format), C.4.5

DRDA_CONNECT_PARM (TCP/IP format), C.4.6

DRDA_DEFAULT_CCSID, C.4.8

DRDA_DESCRIBE_TABLE, C.4.9

DRDA_DISABLE_CALL, C.4.10

DRDA_FLUSH_CACHE, C.4.11

DRDA_GRAPHIC_LIT_CHECK, C.4.13

DRDA_GRAPHIC_PAD_SIZE, C.4.12

DRDA_GRAPHIC_TO_MBCS, C.4.14

DRDA_ISOLATION_LEVEL, C.4.16

DRDA_LOCAL_NODE_NAME, C.4.17

DRDA_MBCS_TO_GRAPHIC, C.4.18

DRDA_OPTIMIZE_QUERY, 11.5, C.4.19

DRDA_PACKAGE_COLLID, 15.1.5, C.4.20

DRDA_PACKAGE_CONSTOKEN, C.4.21

DRDA_PACKAGE_NAME, 15.1.5, C.4.22

DRDA_PACKAGE_OWNER, C.4.23

DRDA_PACKAGE_SECTIONS, C.4.24

DRDA_READ_ONLY, C.4.25

DRDA_RECOVERY_PASSWORD, C.4.26

DRDA_RECOVERY_USERID, C.4.27

DRDA_REMOTE_DB_NAME, C.4.28

DRDA_SECURITY_TYPE, C.4.29

HS_FDS_FETCH_ROWS, C.4.33

HS_LANGUAGE, C.4.34

HS_NLS_NCHAR, C.4.35

LOG_DESTINATION, C.4.36

ORA_MAX_DATE, C.4.37

ORA_NLS33, C.4.38

ORACLE_DRDA_TCTL, C.4.39, C.4.39

ORACLE_DRDA_TRACE, C.4.40

TRACE_LEVEL, C.4.41

HS_DB_DOMAIN, 2.5.1 HS_DB_NAME, 2.5.1 HS_NLS_DATE_FORMAT, 12.7.5 HS_RPC_FETCH_REBLOCKING

gateway features, 1.9.3

gateway support for fetch reblocking, 12.1.1

HS_RPC_FETCH_SIZE

gateway features, 1.9.3

gateway support for fetch reblocking, 12.1.1

LOG_DESTINATION, description, C.4.40 NLS_DATE_FORMAT, 12.7.5 OPEN_LINKS, 11.1.5 passthrough

DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE

gateway features, 1.9.4

DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE syntax

using the passthrough function, 12.8.2

example, 12.8.3.1 gateway feature, 1.3.8 native SQL through the gateway, 12.8 result sets example, 12.8.3.1 result sets from queries, 12.8 retrieving result sets, 12.8.3 SQL feature, 12.8 performance enhancements with fetch reblocking, 12.1.1 PL/SQL

call, 12.3.1

records, 12.3.2

routine, 1.3.9.1

running stored procedures, 12.3

standard Oracle, 1.3.9.2

stored procedure, 12.2

port number

446 as default for DRDA services (TCP/IP), 8.1.1

5000 as default for DRDA services (TCP/IP), 8.1.1

for DRDA Server (TCP/IP), 8.1.1

Primary

DB2/400, 5.3.1

DB2/OS390, 5.2.1

Recovery

DB2/400, 5.3.1

DB2/OS390, 5.2.1

post processing

defined, 12.5.3

native semantics, 12.6

post-processed SQL functions, overview, 12.5.3

SQL tracing, 15.4.1

PREPARE TRANSACTION statement, two-phase commit, 11.5.2 primary port number

DB2/400, 5.3.1

DB2/OS390, 5.2.1

privileges

BIND

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

DB2/VM, 5.5.2

BINDADD

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

DB2/VM, 5.5.2

BINDAGENT

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/VM, 5.5.2

CONNECT

DB2/UDB, 5.4.2

COPY

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/VM, 5.5.2

CREATE IN

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/VM, 5.5.2

CREATE PUBLIC DATABASE LINK

binding the DRDA gateway package, 10.4.4

configuring the Oracle integrating server, 10.7.1

CREATEIN

DB2/UDB, 5.4.2

CREATETAB

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

data dictionary limitations, 12.9 EXECUTE

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

DB2/VM, 5.5.2

procedure

stored procedures

REVISE_SALARY, example, 12.3.1

using DRDA server, 12.3

with read-only gateway, 11.6

procedures

DB2

DB2INS, sample, G.1

ORAIND, sample, G.2

processing time, with GROUPBY, HAVING, WHERE, 12.6.2 processor requirements, 3.1.1 profile set, APPC, configuring, 10.9 protocol

commit confirm, 1.3.13

communications and DRDA-specific parameters, 8.2

communications protocols with Oracle Net, 9.3

converter, 1.3.3

definition, 9.3.3

implicit protocol conversion, 1.3.3

network, 11.4

Oracle Net Protocol Adapters, 9.2

protocol-independent encryption, 1.3.3

two-phase commit, 11.5.2

protocols

IPC, 9.4.2

SNA, for the DRDA server, 1.5

TCP/IP

for the DRDA server, 1.5

how supported, 1.9.6

implicit protocol conversion, 1.3.3

public database link, 10.7.1

Q

queries, distributed, 11.5

R

RAW data type

DRDA_DEFAULT_CCSID description, C.4.8

translating ASCII to EBCDIC, 12.7.1

read-only gateway

main topic, 11.6

option, DRDA_READ_ONLY, C.4.25

read-only support, changes in this release, 1.9.22 rebind

DRDA_DISABLE_CALL, C.4.10

DRDA_ISOLATION_LEVEL, C.4.16

DRDA_PACKAGE_COLLID, C.4.20

DRDA_PACKAGE_CONSTOKEN, C.4.21

DRDA_PACKAGE_NAME, C.4.22

DRDA_PACKAGE_OWNER, C.4.23

DRDA_PACKAGE_SECTIONS, C.4.24

recovery port number

DB2/400, 5.3.1

DB2/OS390, 5.2.1

recovery user ID and password

DB2/400, 5.3.3

DB2/OS390, 5.2.3

DB2/UDB, 5.4.3

DB2/VM, 5.5.3

remote

computer, 9.3.1

connections, 11.1.5

data, 1.3.2

data access, 1.9.14

database

configuration worksheet, E

copy data from Oracle Database server to DRDA Server database, 11.8

creating database links, 11.1.1

DB2/400, 5.3.3

DB2/OS390, 5.2.3

DB2/UDB, 5.4.3

DB2/VM, 5.5.3

defining a path, 11.1.1

DRDA gateway package considerations, 10.5

DRDA_PACKAGE_SECTIONS, C.4.24

example error message, 15.1.1

gateway error codes, 30061, RDB not found, 15.3

DB2 system, 2.5 DRDA database, DRDA_ISOLATION_LEVEL, C.4.16 instance, 12.2 LU definition, 6.4.3.7 objects, 13.3.1 Oracle instance

running a DB2 stored procedure, 12.3

synonym for calling a stored procedure, 12.2

Oracle servers, 9.3.2 procedure, 1.3.9.2 table, 1.3.4 transaction program, 3.1.2 userid and password, 11.1.1 renamed parameters, 14.3.3 REPLACE

command, supported by COPY, 11.8

replication in heterogeneous environment, 11.7 requirements

hardware, 3.1

software, 3.2

restrictions, 2.5 RESULT, 12.3.1 result sets

columns in, 1.9.8

features of the gateway, 1.9.5

return code, error, 15.1 REVISE_SALARY

stored procedure example, 12.3.1

row length

known restrictions, 2.5.1

ROWID

known restrictions, 2.5.2

Oracle column, 2.5.2

with UPDATE or DELETE, 2.5.2

S

sample

files

gateway initialization, tnsnames.ora, listener.ora, B

initsid.gtw, 10.4.1

initsid.ora, 10.4.1

Gateway Initialization File, initdrdahoa1.ora, B.1 listener.ora file, B.3 SQL scripts, 10.5.2 SAVEPOINT, known restrictions, 2.5.1 schema privileges - CREATEIN, 5.4.2 scripts

dropold.sql, 10.5.2.2

g4ddtab, 10.5.2.3

g4ddview.sql, 10.5.2.3

security

Advanced Security, 1.3.3

DRDA_SECURITY_TYPE, C.4.29

encryption, 9.5

overview, 13.1

site autonomy, 1.3.14

validation for SNA, 6.6, 7.6

validation for TCP/IP, 13.4

SELECT

and array size, 1.9.3

operation, 12.1

SQL statement, 12.8.3

statement

compensated SQL functions, 12.5.3

dates, 12.7.5

fetch reblocking, 12.1.1

retrieve results sets, 12.8.3

with read-only gateway, 11.6

SELECT WHERE SQL clause, 12.7.7 semantics, 12.6 server selection, 6.4.3.1, 7.4.1.1 service port number, DRDA_CONNECT_PARM, C.4.6 session, connection, 12.4 set operators

compatibility, 12.6.3

EXCEPT, 12.6.3

INTERSECT, 12.6.3

MINUS, 12.6.3

SQL set operators and clauses, 12.6.3

shift attribute, multi-byte support, D.5 SID

choosing a gateway SID, 10.2

configuring additional DRDA server instances, 10.9

Gateway System Identifier, defined, 10.2

Side Information Profile

communication error, 15.1.4

definition, 6.3, 7.3

SIMPLE linkage convention

DB2INS, sample DB2 stored procedure, G.1

of DB2 stored procedures, 12.3.2

site autonomy, 1.3.14 SNA, 5.4.1

configuring

AS/400 communications, 5.3.1

OS/390 communications, 5.2.1

VM communications, 5.5.1

conversation security, 6.7, 7.7 CPI-C error, 15.1.4 facilities, 1.9.11 functions, 1.6 LU, 13.5.1.1 protocol

DRDA server support, 1.5

remote access, 1.9.14 security validation

IBM Communication Server, 7.6

Microsoft SNA Server or Host Integration Server, 6.6

versus TCP/IP security, 13.4

security, DRDA_SECURITY_TYPE, C.4.29 SECURITY=PROGRAM, 6.7.1, 7.7.1 SECURITY=SAME, 6.7.2, 7.7.2 send/receive buffer, C.4.4 session allocation mode, DRDA_CMSRC_CM_IMMEDIATE, C.4.7 SNA Server

connection definition, 6.4.3.4

CPI-C symbolic destination names, 6.4.3.8

definitions

creating side information profiles, 7.3

creating SNA definitions for SNA Server version 3, 6.4.3

side information profiles, 6.3

for Windows NT, 6.3.1 link service definition, 6.4.3.3 local LU definition, 6.4.3.5 mode definition, 6.4.3.6 remote LU definition, 6.4.3.7 server selection, 6.4.3.1 testing the connection, 6.5 SNA Server for Windows NT

dependent LUs, 7.3.1

independent LUs, 7.3.1

testing the connection, 7.5

SNACFG command, 6.4.1 snacfg.ctl file, 6.4.1, 7.3.2.1 snapshots

known restrictions, 2.5.2

Oracle snapshot feature, 11.7.2

software requirements, 3.2 sort order

with ORDERBY, 12.6.2

SPUFI on DB2/OS390, 10.5.2 SQL

main topic, 1.3.5

ANSI standard, 1.3.5

clause compatibility, 12.6.3

clauses

DELETE, 12.7.7

INSERT, 12.7.7

SELECT WHERE, 12.7.7

UPDATE, 12.7.7

constructs, Oracle processing, 12.5 differences in the gateway, 1.7.1 functions

and Native Semantics, 12.6

quick reference list, F

SUBSTR, 12.6

ISO standard, 1.3.5 native DB2, 1.3.8 passthrough

described, 12.8

retrieving results sets example, 12.8.3.1

using DBMS_HS_PASSTHROUGH.EXECUTE_IMMEDIATE, 12.8.2

statements

DB2, 12.8.2

DRDA_ISOLATION_LEVEL, C.4.16

passing through gateway, 12.8

run through the gateway, 11.10

using JOIN, 12.1

syntax, 12.7.9 tracing

improving performance, 11.10

tracing errors in the Oracle Database, 15.4.1

SQL functions

column functions, 12.5.1

compatible, defined, 12.5.1

compensated, defined, 12.5.3

DB2/400, 12.5.7

DB2/OS390, 12.5.5

DB2/UDB, 12.5.6

DB2/VM, 12.5.8

that can be disabled, 12.6.2

that can be enabled, 12.6.1

translated

defined, 12.5.2

with Native Semantics, 12.6.1 SQL set operators and clauses, 12.6.3 SQL*Net

Heterogeneous Services (HS) facility, 9.2

replaced by Oracle Net, 9.2

SQL*Plus

connecting gateway to Oracle integrating server, 9.7.1

copying data from Oracle server to DRDA Server, 11.8

extending gateway uses, 1.8.1

introduction, 1.3.12

sqlstate, mapped sqlstate errors, 15.2 stability, of cursor, DRDA_ISOLATION_LEVEL, C.4.16 Startup Shell Script

migration, 14.1.2

statements

CREATE DATABASE LINK, 11.1.1

CREATE DATABASE, client/server configuration, D.2

DB2 CREATE TABLE, 1.3.8

DDL

nonqueries supported by gateway passthrough, 12.8

number of rows affected by passthrough, 12.8.2

DELETE

and TO_DATE function, 12.7.5

nonqueries supported by gateway passthrough, 12.8

DROP DATABASE LINK, 11.1.3 GRANT, 10.7.2 INSERT

and TO_DATE function, 12.7.5

nonqueries supported by gateway passthrough, 12.8

passing SQL through gateway, 12.8 PREPARE TRANSACTION, two-phase commit, 11.5.2 SELECT

and TO_DATE function, 12.7.5

compensated SQL functions, 12.5.3

fetch reblocking, array size, 12.1.1

retrieve results sets, 12.8.3

with read-only gateway, 11.6

SQL

DB2, 12.8.2

JOIN, 12.1

SELECT, 12.8.3

UPDATE

and TO_DATE function, 12.7.5

nonqueries supported by gateway passthrough, 12.8

stored procedure

creating on DB2, 12.3.1

DB2

considerations for use, 12.3.2

native to DRDA server, 12.3

with read-only gateway, 11.6

DB2INS, sample, G.1 extended database services, 1.3.2 GTW$_BIND_PKG, 10.4.4 native DB2, 1.3.9.2 Oracle and non-Oracle, 1.3.9 Oracle Database 10g server

using, 12.2

Oracle database server

local instance, 12.2

PL/SQL, 12.2

remote instance, 12.2

Oracle, description, 1.3.9.1 ORAIND, sample, G.2 restriction, 2.5.1 REVISE_SALARY, example, 12.3.1 usage, C.4.10 using DRDA server, 12.3 string concatenation, known restrictions, 2.5.1 string index, with Native Semantics, 12.6 Structured Query Language, also see SQL, 1.2.1 SUBSTR

SQL function

known restrictions, 2.5.1

Oracle implementation permits negative values, 12.6

with Native Semantics, 2.5.1

synonym

feature, 11.4

for location transparency, 12.2

how the gateway works, 1.7

system privileges - BINDADD and BINDAGENT

configuration worksheet, E

DB2/OS390, 5.2.2

DB2/VM, 5.5.2

T

table

create a table in DB2, 12.8.2.1

insert a row into a DB2 table, 12.8.2.1

TABLE_PRIVILEGES view, A.2.17 tables

ORACLE2PC, 10.5.1.2, 10.5.2.5

ORACLE2PC, distributed transactions, 11.5.3

ORADRDA.ORACLE2PC, two-phase commit, 11.5.2

tailoring

initsid.ora file, 10.4.2

TCP/IP

affecting memory requirements, 3.1.2

concurrent connections, 3.1.2

configuration chapter, 8

configuration worksheet, E

configuring

for AS/400, 5.3.1

for OS/390, 5.2.1

for VM, 5.5.1

to use DNS, 8.2

using DRDA_CONNECT_PARM parameter, 8.2

database link behavior, 12.4 default port number, 9.4.2 DRDA_CONNECT_PARM, C.4.6 facilities, 1.9.11 format, gateway initialization file parameter, C.4.6 functions, 1.6 gateway architecture, connecting to DRDA Server, 1.5 known restrictions, DRDA Network Interfaces, 2.5.1 modifying tnsnames.ora in Oracle Net, 9.4.2 protocol

access across multiple networks - transparency, 1.3.1

DRDA server support, 1.5

implicit protocol conversion, 1.3.3

remote access, 1.9.14 sample Oracle Net listener.ora file, B.3 security validation, 13.4 support, 1.9.6 you must choose either SNA or TCP/IP for the Networking Interface, 8.2 terminology defined, 1.4 tg4drdasnacommsvr subdirectory, sample SNA Server definitions, 7.3.2.1, 7.3.2.1 tg4drdasnamssna subdirectory, sample SNA Server definitions, 6.4.1 TIME data type, 12.7.4.1 time operations, 12.7.4 TIMESTAMP data type, 12.7.4.1 TNSNAMES.ORA

changes to, during migration problems, 14.2

tnsnames.ora

adding a gateway service name, 9.4.2, 9.4.2

configuring additional DRDA Server instances, 10.9

connect descriptor, 11.1.1

using the HS facilities, 14.5

TO_DATE function

Oracle function preprocessed in SQL, 12.7.7

processing DATE data, 12.7.4.2

twenty-first century dates, 12.7.5

token

error tokens, 15.1.3

package consistency, DRDA_PACKAGE_CONSTOKEN, C.4.21

trace control, C.4.39 TRACE_LEVEL parameter, C.4.41 tracing

code, C.4.41

LOG_DESTINATION, C.4.36

ORACLE_DRDA_TRACE, C.4.40

SQL statements, 11.10

trade-off, Native Semantics, 12.6 transaction mode, read-only, DRDA_READ_ONLY, C.4.25 transactions

CICS, 12.3.2

IMS, 12.3.2

transform

character set transforms with multi-byte support, D.5

not required for DRDA Server, D.5

transparency

and performance, 12.6

main topic, gateway transparency, 1.3.1

triggers for Oracle Database 10g server, 11.7.1 TSO, 5.2 two-phase commit

ORACLE2PC table

DB2/400, 5.3.2

DB2/OS390, 5.2.2

DB2/UDB, 5.4.2

DB2/VM, 5.5.2

protection, 1.3.2 transactions, distributed queries, 11.5.2 unsupported statement, 11.5.2

U

UNION

capability, 1.3.2

operator, 12.6.3

UNION ALL

operator, 12.6.3

UPDATE

known restrictions, 2.5.2

operation, 12.1

SQL clause, 12.7.7

statement

dates, 12.7.5

native SQL passthrough, 12.8

transaction semantics, 1.7.1

with read-only gateway, 11.6 upgrading, defined, 14.1 user privileges, 12.9 USER_CATALOG view, A.2.18 USER_COL_COMMENTS view, A.2.19 USER_CONS_COLUMNS view, A.2.21 USER_CONSTRAINTS view, A.2.20 USER_DB_LINKS data dictionary view, 11.1.4 USER_INDEXES view, A.2.22 USER_OBJECTS view, A.2.23 USER_SYNONYMS view, A.2.24 USER_TAB_COLUMNS view, A.2.26 USER_TAB_COMMENTS view, A.2.27 USER_TABLES view, A.2.25 USER_USERS view, A.2.28 USER_VIEWS view, A.2.29 userid mapping

DB2/400, 13.5.1.3

DB2/OS390, 13.5.1.1

DB2/VM, 13.5.1.2

security, 13.5.1

userid translation

DB2, 13.5.1.2

USING clause, 11.1.1

V

VALUES clause, 12.7.7

VARCHAR data type, 12.7.2

variable

bind, 12.8

input bind, 12.7.4.2

view

catalog

DB2/400, 12.9.1

DB2/OS390, 12.9.1

DB2/UDB, 12.9.1

DB2/VM, 12.9.1

creating, 10.7.2 data dictionary, 12.9 VSAM file, 12.3.2 VTAM

DB2/OS390, 5.2

DB2/VM VTAM configuring, 5.5.1

W

WHERE clause

compatible for all versions of DRDA Server, 12.6.3

SQL limitations, Oracle ROWID column, 2.5.2

WHERE CURRENT OF CURSOR clause, ROWID column, 2.5.2 WHERE function, 12.6.2 wireless communication, 1.3.3 workarounds, 2.4

Z

zoned decimal operations, 12.7.10

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2016, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.