IBM Data Server DB2 User Manual
Page 160

146
DB2 Deployment Guide
Installing IBM Data Server Driver for ODBC and CLI
To install IBM Data Server Client for ODBC and CLI, perform these steps:
1. Uncompress the compressed file to a directory on the target machine.
2. Create the directory $HOME/db2_cli_odbc_driver, where the driver will be
installed.
3. Untar the tar archive with directory structure preserved using the -xvf option.
4. Ensure that db2dump and the db2 directories are writable. Alternatively, the
path you have referenced in the diagpath parameter must also be writable.
Example 4-1 shows how to uncompress the compressed file in the Linux and 
UNIX systems. This example assumes that the compressed file is in the directory 
db2_cli_odbc_driver under the home directory.
Example 4-1 Uncompressing the compressed file in Linux and UNIX systems.
cd $HOME/db2_cli_odbc_driver
uncompress db2_driver_for_odbc_cli.tar.Z
tar -xvf db2_driver_for_odbc_cli.tar
rm db2_driver_for_odbc_cli.tar
Installing IBM Data Server Driver for ODBC, CLI, and .NET
To install IBM Data Server Driver for ODBC, CLI, and .NET for Windows 
systems, uncompress the compressed driver file and run the setup.exe installer 
file and follow the instructions.
For further information regarding setup command options for installing IBM Data 
Server Driver for ODBC, CLI, and .NET, refer to following URL:
If your system already has an IBM Data Server Client or IBM Data Server 
Runtime Client installed and you want to install one or more copies of the IBM 
Data Server Driver for ODBC and CLI, follow the same process described in 
“Installing IBM Data Server Driver for ODBC and CLI” on page 146. Ensure that 
the application is using the correct copy of the driver by dynamically loading the 
driver from the target installation directory.
For installing multiple copies of IBM Data Server Driver for ODBC and CLI, 
ensure that a different path is specified when you untar the extracted file.
For installing multiple copies of IBM Data Server Driver for ODBC, CLI, and 
.NET, you can issue: 
setup /n "COPY_NAME"
