The IBM® Data Server Driver for ODBC
and CLI is not part of the IBM Data
Server Client or the IBM Data Server Runtime Client. It must be installed and configured separately. You must
configure the IBM Data Server Driver for ODBC
and CLI, and the software components of your database application
runtime environment in order for your applications to use the driver
successfully.
Before you begin
To configure the
IBM Data Server Driver for ODBC
and CLI and your application environment for the driver, you need:
Procedure
To configure theIBM Data Server Driver for ODBC
and CLI, and the runtime environment of your IBM Data Server Driver for ODBC
and CLI applications to use the driver:
- Configure aspects of the driver's behavior such as data
source name, user name, performance options, and connection options
by updating the db2cli.ini initialization file.
The location of the
db2cli.ini file might
change based on whether the Microsoft ODBC Driver Manager is used, the type of data source
names (DSN) used, the type of client or driver being installed, and
whether the registry variable
DB2CLIINIPATH is
set.
There is no support for the Command Line Processor (CLP)
with the IBM Data Server Driver for ODBC
and CLI. For this reason, you can not update CLI configuration
using the CLP command "db2 update CLI cfg"; you must
update the db2cli.ini initialization file manually.
If you have multiple copies of the IBM Data Server Driver for ODBC
and CLI installed, each copy of the driver will have its own db2cli.ini file. Ensure you make the additions to the db2cli.ini for the correct copy of the driver.
- Configure application environment variables.
- For applications participating in transactions managed
by the Microsoft Distributed
Transaction Coordinator (DTC) only, you must register the driver with
the DTC.
- For ODBC applications using the Microsoft ODBC driver manager only, you
must register the driver with the Microsoft driver manager.