Preparing the DB2 Environment

In this section:

How to:

The Adapter for DB2 minimally requires the installation of the DB2 Client for the CLI type adapter or the DB2 load library for the CAF adapter. The DB2 Client allows you to connect to a local or remote DB2 data source server.

For the server running in the z/OS environment using the CLI interface FMID JDB7717, the DB2 component must be installed on the MVS system.


Top of page

x
Procedure: How to Set Up the Environment on Microsoft Windows

On Microsoft Windows, the DB2 environment is set up during the installation of DB2.

The adapter supports Unicode data in DB2 version 8 or higher databases created with the option CODESET UTF-8. You must add DB2CODEPAGE=1208 to the Windows environment either by:

DB2CODEPAGE=1208

For IBM i: To connect to the IBM i platform (formerly known as i5/OS) using the Adapter for DB2, you must use the IBM DB2 connect client. You must also set DB2CODEPAGE 1208 on the Windows platform (regardless of whether you are using Unicode data). This setting ensures proper communication with the DB2 catalog. Without it, you will receive errors when accessing the DB2 catalog (for example, when creating a synonym).

Note that the setting only affects synonym creation. Existing synonyms can be used for reporting regardless of this setting.


Top of page

x
Procedure: How to Set Up the Environment on UNIX

To set up the Adapter for a DB2 environment on UNIX, do all of the following:


Top of page

x
Procedure: How to Set Up the Environment on z/OS

Two types of Adapters for DB2 are available in this environment. Each one requires different pre-configuration steps prior to using the Web Console.


Top of page

x
Procedure: How to Set Up the Environment on IBM i

To create tables with one-part names, a CURLIB must be set. Thereafter, the location can be anywhere in the library path. The first table found is the one used.


Top of page

x
Accessing a Remote Database Server

Using the standard rules for deploying the DB2 Client, the server supports connections to:

When using DB2/CLI to connect to a remote DB2 data source, the DB2 client catalog must contain an entry for the node where the remote data source resides and an entry for the remote database name.

Support for Remote Aliases. An alias entry in a local DB2 system that points to a table in another DB2 system is only supported with the CREATE SYNONYM command. It is not supported for metadata queries when SET ENGINE=DB2 is in effect.


Top of page

x
XA Support

Read/write applications accessing DB2 data sources are able to perform transactions managed in XA-compliant mode.

To activate the XA Transaction Management feature, the server has to be configured in Transaction Coordination Mode, using the Web console configuration functions. Using Transaction Coordination Mode guarantees the integrity of data modification on all of the involved DBMSs and protects part of the data modifications from being committed on one DBMS and terminated on another.

Note that on DB2, support for XA in 64bit DB2 requires the installation of Fix Pack 13.

For complete documentation on XA compliance, see XA Support.


iWay Software