Db2 ODBC 8.0.2 UNIX
- Last Updated: May 8, 2026
- 14 minute read
- OpenAccess SDK
- Documentation
README
Progress(R) DataDirect(R)
Progress DataDirect for ODBC for Db2 Wire Protocol Driver
UNIX and LINUX Platforms (32- and 64-bit)
Release 8.0.2
April 2026
***********************************************************************
Copyright (C) 2026 Progress Software Corporation and/or its
subsidiaries or affiliates. All Rights Reserved.
***********************************************************************
This README file contains information for Progress(R) DataDirect(R)
for ODBC Db2(TM) Wire Protocol Driver.
This README file contains information not included in the PROGRESS
DATADIRECT FOR ODBC FOR DB2 WIRE PROTOCOL DRIVER USER'S GUIDE.
CONTENTS
Post-GA Product Announcements
Requirements
Installation Directory
Data Source and Platform Support
Third-party Components Compatibility Matrix
Changes since 8.0.2
Release 8.0.2 Features
Configuring Data Sources
Driver WorkAround Options
Notes, Known Problems, and Restrictions
Documentation
Installed Files for the 32-bit Driver
Installed Files for the 64-bit Driver
Post-GA Product Announcements
The readme files will no longer be updated with product announcements and new
features after the General Availability (GA) of the product. For the latest
updates and enhancements, please refer to the release notes
(https://www.progress.com/datadirect-connectors/whats-new).
Requirements
* The installer program requires a JVM that is Java SE 11 or higher, including
Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
* The driver requires the following runtime libraries:
- AIX: C/C++ runtime libraries version 16.1 or higher
- Linux: C/C++ runtime libraries version GCC 2.12 or higher
- Solaris: C/C++ runtime libraries version 12.6 or higher
- IBM Power 8 (64-bit): C/C++ runtime libraries of GCC 2.17 or higher
- Linux z/OS (64-bit): C/C++ runtime libraries of GCC 2.17 or higher
- Linux PPC (64-bit): C/C++ runtime libraries of GCC 2.17 or higher
Installation Directory
* The default installation directory for the 32-bit driver is:
/opt/Progress/DataDirect/ODBC_32bit
* The default installation directory for the 64-bit driver is:
/opt/Progress/DataDirect/ODBC_64bit
Data Source and Platform Support
For the latest data source and platform support information, refer to the
Product Compatibility Guide:
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf
Third-party Components Compatibility Matrix
For information about the third-party components that are installed with the
product, refer to the ODBC Third-party Components Compatibility Matrix on the
DataDirect Product Life Cycle page:
https://docs.progress.com/bundle/datadirect-product-life-cycle/page/topics/
datadirect_life_cycle/datadirect-product-life-cycle.html
Changes since 8.0.2
ICU Library Upgrade (74.1)
--------------------------
The ICU library files that are installed with the product have been upgraded
to version 74.1. As a part of this upgrade, the following platforms and their
file names have been updated:
* AIX platforms
- 32-bit product package: From libivicu28.a to libivicu.a
- 64-bit product package: From libddicu28.a to libddicu.a
Note - This upgrade is available starting in build 08.02.1072 of the ICU
library files.
* Linux platforms
- 32-bit product package: From libivicu28.so to libivicu.so
- 64-bit product package: From libddicu28.so to libddicu.so
Note - This upgrade is available starting in build 08.02.0965 of the ICU
library files.
* Solaris platforms (Sparc and Solaris X)
- 32-bit product package: From libivicu28.so to libivicu.so
- 64-bit product package: From libddicu28.so to libddicu.so
Note - This upgrade is available starting in build 08.02.1799 of the ICU
library files.
* Limited availability platforms (Linux PPC, Linux z/OS, and IBM Power 8)
- 64-bit product package: From libddicu28.so to libddicu.so
Note - This upgrade is available starting in build 08.02.1799 of the ICU
library files.
As part of the ICU 74.1 upgrade, the complier and runtime versions for the
driver have been changed to the following:
* For AIX platforms, the compiler version has been upgraded to xlclang++ 16.1.
As a result, you must have C/C++ runtime libraries of 16.1 or higher on
your machine.
* For Linux platforms, the compiler version has been upgraded to GCC 7.3.1.
As a result, you must have C/C++ runtime libraries of GCC 2.12 or higher on
your machine.
* For Solaris platforms, the compiler version has been upgraded to Oracle
Developer Studio 12.6. As a result, you must have C/C++ runtime libraries
of 12.6 or higher on your machine.
* For limited availability platforms such as Linux PPC (64-bit), Linux z/OS
(64-bit), and IBM Power 8 (64-bit), the compiler version has been upgraded to
GCC 7.3.1. As a result, you must have C/C++ runtime libraries of GCC 2.17 or
higher on your machine.
Debugging Symbols
------------------
The driver binaries now include debugging symbols that can be used for
diagnosing and debugging issues in the driver.
JRE Requirement for the Installer
---------------------------------
The installer program now requires you to install a JRE that is Java SE 11 or
higher before running the installer. In earlier versions, the JRE used by the
installer program was included in the product. However, to avoid potential
security vulnerabilities, the installer program no longer includes a JRE.
Instead, the installer program uses the JRE in your environment to allow for
the most secure version of a JRE to be used.
Notes:
* This change does not affect the JVM requirements for the driver. For the latest
driver requirements, refer to the Product Compatibility Guide:
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf
* The installer program cannot remove the already installed JRE files from the
install directory automatically. Remove them manually.
TLSv1.3 Support
---------------
The driver has been enhanced to support the TLSv1.3 cryptographic protocol.
As part of this enhancement, the default cryptographic protocols enabled by the
driver have been updated to TLSv1.3 and TLSv1.2.
Crypto Protocol Version Changes
--------------------------------
The default value for the Crypto Protocol Version (CryptoProtocolVersion)
connection option has been changed to TLSv1.2. In addition, the TLSv1.1
and TLSv1.0 cryptographic protocols are no longer considered secure and,
therefore, are no longer recommended for use. However, the driver still
supports them for legacy servers that do not support more secure
protocols.
ODBC Cursor Library
-------------------
The product package no longer includes the ODBC Cursor library file
(odbccurs.so) because it has some known security vulnerabilities that
could potentially expose you to security risks.
Note: The installer program cannot remove the ODBC Cursor library file
automatically while installing a new version of the driver. Remove it
manually.
Changes to Installation of Non-Essential Components
-----------------------------------------------------
The installer program has been updated to no longer install common components
for drivers that do not use them. As a result, the installer program no longer
installs the Curl library files (libivcurl28.so and libddcurl28.so) for the Db2
Wire Protocol driver. If the files are not used by any other DataDirect driver
on your machine, you can safely remove them from existing product directories.
SSL Enhancement (3.0.9)
-----------------------
Note: OpenSSL library 3.0.9 has been replaced with a later version. For
the latest information about the third-party components that are installed
with the product, refer to the ODBC Third-party Components Compatibility
Matrix on the DataDirect Product Life Cycle page:
https://docs.progress.com/bundle/datadirect-product-life-cycle/page/topics/
datadirect_life_cycle/datadirect-product-life-cycle.html.
The default version of the OpenSSL library has been upgraded to version
3.0.9, which fixes the security vulnerabilities listed on the following
page: https://www.openssl.org/news/vulnerabilities-3.0.html
This upgrade is available in build 08.02.0595 of the following OpenSSL
library files:
- On AIX: libivopenssl30.a (32-bit) and libddopenssl30.a (64-bit)
- On other platforms: ivopenssl30.so [.sl] (32-bit) and ddopenssl30.so (64-bit)
Notes:
* The driver supports the following OpenSSL 3.0 providers: Default and
FIPS.
* The FIPS provider is supported only on the following platforms:
Windows 64-bit, Linux 64-bit, and AIX 64-bit.
* The following connection options have been added to configure the
driver to use OpenSSL 3.0: Enable FIPS (EnableFIPS), OpenSSL Config File
(OpenSSLConfigFile), and OpenSSL Provider Path (OpenSSLProviderPath).
For more information on the new connection options and how to configure
the driver to use OpenSSL 3.0, refer to the user's guide.
* When installing a new version of the product, the installer program will
automatically replace the OpenSSL 1.1.1 library files with the OpenSSL 3.0
library files in the install directory, which will impact all the DataDirect
ODBC drivers installed on a machine. Therefore:
- If you are using multiple 8.0 drivers, upgrade all your drivers to the latest
version.
- If you are using both 8.0 and 7.1 versions of the driver, copy the xxtls27.dll
file to a different location before installing a new version of the 8.0 driver.
Copy it back to the install directory once the installation is complete.
End of Support for OpenSSL 1.1.1
--------------------------------
The product no longer includes version 1.1.1 of the OpenSSL library.
The library will reach the end of its product life cycle in September 2023
and will not receive any security updates after that. Note that continuing
to use the library after September 2023 can potentially expose you to
security vulnerabilities.
Note: As a result of this change, when installing a new version of the product,
the installer program will automatically remove version 1.1.1 of the library
from the install directory, which will impact all the DataDirect ODBC drivers
installed on a machine.
Release 8.0.2 Features
Driver Enhancements
-------------------
* Note: OpenSSL library 1.1.1n has been replaced with version 1.1.1t. In
addition to fixing multiple new vulnerabilities, version 1.1.1t also
addresses the vulnerabilities resolved by version 1.1.1n.
The default version of the OpenSSL library has been upgraded to version
1.1.1n, which fixes the following security vulnerabilities:
- Infinite loop in BN_mod_sqrt() reachable when parsing certificates
(CVE-2022-0778)
- BN_mod_exp may produce incorrect results on MIPS (CVE-2021-4160)
This upgrade is available in build 08.02.0216 of the following OpenSSL
library files: libivtls28.so [.a] (32-bit) and libddtls28.so [.a] (64-bit).
* The driver has been enhanced to support the BINARY and VARBINARY data types.
* The driver has been enhanced to support TLS/SSL server authentication for
the applications deployed in a serverless environment. The driver stores the
TLS/SSL certificates in memory and lets applications use TLS/SSL server
authentication without storing the truststore file on the disk. To use this
enhancement, specify the content of the certificate in the refreshed
Trust Store (Truststore) connection option or the new
SQL_COPT_INMEMORY_TRUSTSTORECERT pre-connection attribute. Refer to the
user's guide for details.
* A Password Encryption Tool, called ddencpwd, is now included with the product
package. It encrypts passwords for secure handling in connection strings and
odbc.ini files. At connection, the driver decrypts these passwords and passes
them to the data source as required.
* The driver has been enhanced to support Select queries with parameterized
arrays.
* The driver has been enhanced to include timestamp in the internal packet logs
by default. If you want to disable the timestamp logging in packet logs, set
PacketLoggingOptions=1. The internal packet logging is not enabled by default.
To enable it, set EnablePacketLogging=1.
* The Driver Manager for UNIX/Linux has been enhanced to support setting the
Unicode encoding type for applications on a per connection basis. By passing
a value for the SQL_ATTR_APP_UNICODE_TYPE attribute using SQLSetConnectAttr,
your application can specify the encoding at connection. This allows your
application to pass both UTF-8 and UTF-16 encoded strings with a single
environment handle. The valid values for the SQL_ATTR_APP_UNICODE_TYPE
attribute are SQL_DD_CP_UTF8 and SQL_DD_CP_UTF16. The default value is
SQL_DD_CP_UTF8.
* The new AllowedOpenSSLVersions option determines which version of the OpenSSL
library file the driver uses for data encryption when multiple versions are
installed with the product. For example, when specifying a value of 1.1.1
(AllowedOpenSSLVersions=1.1.1) the driver uses the 1.1.1 version of the library
that is installed with the driver.
Changed Behavior
----------------
* The product no longer includes version 1.0.2 of the OpenSSL library.
The library has reached the end of its product life cycle and is not
receiving security updates anymore. Note that continuing to use the
library could potentially expose you to security vulnerabilities.
Note: As a result of this change, when installing a new version of the
driver, the installer program will automatically remove version 1.0.2
of the library from the install directory.
Configuring Data Sources
Data sources are stored in the system information file (typically,
odbc.ini). For details on configuring this file, see the PROGRESS DATADIRECT
FOR ODBC FOR DB2 WIRE PROTOCOL DRIVER USER'S GUIDE.
Driver WorkAround Options
Progress DataDirect has included non-standard connection options (workarounds)
for the driver that enable you to take full advantage of packaged ODBC-enabled
applications requiring non-standard or extended behavior. Refer to the chapter
"WorkAround options" in THE PROGRESS DATADIRECT FOR ODBC DRIVERS REFERENCE for a
description of these options.
Notes, Known Issues, and Restrictions
Using OpenSSL 3.0 against AS400 Servers
---------------------------------------
The SSL connection using OpenSSL 3.0 has not been tested against AS400 servers
as their SSL-enabled versions were unavailable.
Workaround for code page conversion error
------------------------------------------
When the LoadTableFromFile() function is called, if the code page value specified
in the configuration file, which is passed as an argument in LoadTableFromFile(),
is different from the default code page value of the machine, the value set for
the IANAAppCodePage connection attribute is replaced with it.
This change may cause the driver to return the following error: "String data code
page conversion failed." To work around it, set the SQL_ATTR_IANA_APP_CODE_PAGE
statement attribute to the code page value specified in the configuration file.
Specifying values for the same connection option multiple times
---------------------------------------------------------------
The driver does not support specifying values for the same connection
option multiple times in a connection string or DSN. If a value is
specified using the same attribute multiple times or using both
long and short attributes, the connection may fail or the driver may
not behave as intended.
For SSL Users
-------------
When trying to connect to a database using SSL encryption, you may
receive an error message similar to: "PRNG not seeded". This is because
certain versions of some operating systems do not generate truly random
numbers necessary for encryption. For more information about this error
and available patches, please refer to the Web site:
http://www.openssl.org/support/faq.html#USER1
ODBC Development on UNIX and Linux Platforms
--------------------------------------------
All of the Release 8.0 Core Components (header files, etc.) needed for
development of ODBC applications on UNIX and Linux are installed into
the /include directory created by the product installer.
Please read the notices.txt file in the installation directory for
licensing information regarding the ODBC Core Components. Contact your
Progress DataDirect representative if you have any questions.
Developers using programming languages other than C++:
The DataDirect ODBC Driver Manager is a C++ shared library. The ODBC
Driver Manager can be used with any language that supports loading a
C++ shared library; however, if you are using a programming language
other than C++, you must take additional steps to ensure that the C++
libraries are initialized properly when loaded. If you are not using
C++, consult your compiler documentation for instructions on using C++
shared libraries with your application.
LANG Environment Setting on UNIX and Linux Platforms
----------------------------------------------------
A default installation of the product on UNIX and Linux assumes that
the value of the LANG environment setting is en_US. If your locale is
not set to en_US, the drivers may not return error messages properly.
In this case, you must create a symbolic link in the
<Install_Dir>/locale directory that has the same value as the LANG
environment setting. This link must point to the
<Install_Dir>/locale/en_US directory.
SQLColAttribute(s)
------------------
The column attributes 1001 and 1002, which were assigned as DataDirect-
specific attributes, were inadvertently used as system attributes by
the Microsoft 3.0 ODBC implementation. Applications using those
attributes must now use 1901 and 1902, respectively.
SQL_C_NUMERIC
-------------
Because of inconsistencies in the ODBC specification, users attempting
to use SQL_C_NUMERIC parameters must set the precision and scale values
of the corresponding structure and the descriptor fields in the
Application Parameter Descriptor.
For Developers Using IIS
------------------------
One of the most common connectivity issues encountered while using IIS
(Microsoft's Internet Information Server) concerns the use and settings
of the account permissions. If you encounter problems using DataDirect
drivers with an IIS server, refer to KnowledgeBase document number 4274
on the Progress DataDirect web site:
http://knowledgebase.datadirect.com.
Documentation
PROGRESS DATADIRECT FOR ODBC FOR DB2 WIRE PROTOCOL DRIVER
DOCUMENTATION SET
----------------------------------------------------------
The user's guide is available as an HTML help system on the DataDirect
documentation web page:
https://docs.progress.com/category/datadirect-ibm-db2
You can also access the help system directly via the HTML redirect
in the installation Help directory.
Installed Files for the 32-bit Driver
This file list assumes a full installation of the 32-bit driver and
documentation.
The installer copies the following files and subdirectories to the
product installation directory, by default:
/opt/Progress/DataDirect/ODBC:
/<install_dir>/:
----------------
IVODBC.LIC DataDirect license file
license.txt Progress DataDirect license agreement
odbc.csh Setup script for C shell
odbc.ini Sample odbc.ini file
odbcinst.ini Sample odbcinst.ini file
odbc.sh Setup script for Bourne shell
/bin/:
-----
bind28 Db2 bind utility
ivtestlib Test application to check that required
libraries are present and loadable
/bind/LUW/:
-----------
DDODBC_LUW.lst Files for Linux/UNIX/Windows
DDOC510A.bnd
DDOC510B.bnd
DDOC510C.bnd
DDOR510A.bnd
DDOR510B.bnd
DDOR510C.bnd
DDOS510A.bnd
DDOS510B.bnd
DDOS510C.bnd
DDOU510A.bnd
DDOU510B.bnd
DDOU510C.bnd
/bind/iSeries/:
---------------
DDODBC_400.lst Files for iSeries
DDOC510A.bnd
DDOC510B.bnd
DDOC510C.bnd
DDON510A.bnd
DDON510B.bnd
DDON510C.bnd
DDOR510A.bnd
DDOR510B.bnd
DDOR510C.bnd
DDOS510A.bnd
DDOS510B.bnd
DDOS510C.bnd
DDOU510A.bnd
DDOU510B.bnd
DDOU510C.bnd
DDOV5R2.savf
DDOV5R3.savf
DDOV5R4.savf
DDOV6R1.savf
DDOV7R1.savf
CfODBC iSeries Manual Package Creation Instructions.txt
/bind/zOS/:
---------------
DDODBC_MVS.LST Files for z/OS
CNTLFILE.xmit
DBRMFILE.xmit
DDOC510A.bnd
DDOC510B.bnd
DDOC510C.bnd
DDOR510A.bnd
DDOR510B.bnd
DDOR510C.bnd
DDOS510A.bnd
DDOS510B.bnd
DDOS510C.bnd
DDOU510A.bnd
DDOU510B.bnd
DDOU510C.bnd
CfODBC zOS Manual Package Creation Instructions.txt
/FIXES/:
--------
fixes8.0.txt List of fixes since last release
/help/:
------
*.html HTML redirects to online connector help systems
and documentation resources
/include/:
---------
odbcinst.h Include files
qesqlext.h
sql.h
sqlext.h
sqltypes.h
sqlucode.h
sqlunx.h
/install/:
---------
*.* Files associated with the installer program
/lib/:
-----
ivdb228.so DB2 WP driver
ivopenssl30.so TLS/SSL support file (OpenSSL library
version 3.0) [libivopenssl30.a on AIX]
ivopenssl.so TLS/SSL support file (OpenSSL library
version 3.5) [libivopenssl.a on AIX]
ivtrc28.so Progress DataDirect trace library
libivicu.a Unicode conversion tables for AIX platforms
libivicu.so Unicode conversion tables for Linux and
Solaris platforms
libivicu28.so Unicode conversion tables for limited
availability platforms
libodbc.so ODBC Driver Manager
libodbcinst.so ODBC Installer
/locale/en_US/LC_MESSAGES/:
--------------------------
ivdb228.mo Db2 WP driver message file
ivdb228.po Db2 WP driver message file source
odbc.m ODBC Driver Manager message file
odbc.po ODBC Driver Manager message source
/NOTICES/:
---------
ODBC for Db2 v8.0
notices.txt Third-party vendor license agreements
/READMES/:
---------
ODBC for Db2 v8.0
readme.txt This file
/samples/bulk/:
---------------
bulk Bulk application
bulk.c Bulk example source
bulk.mak Bulk example make file
bulk.txt Bulk example description
ddlogging.properties Log configuration file for the
Db2 driver
/samples/bulkstrm/:
-------------------
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulkstrm Bulk streaming example application
bulkstrm.txt Bulk streaming example description
main.cpp Bulk streaming example source
msgprintf.hpp Bulk streaming example header
streambulk.mak Bulk streaming example make file
ddlogging.properties Log configuration file for the
Db2 driver
/samples/example/:
------------------
example Example application
example.c Example source
example.h Example header
example.mak Example make file
ddlogging.properties Log configuration file for the
Db2 driver
/samples/trn/:
--------------
makefile Translation Library example make file
readme.trn Translation Library example description
translat.c Translation Library example source file
/tools/:
-------
ddencpwd Password Encryption Tool
ddextu License Extender utility
ddprocinfo Processor Information utility
/uninstall/:
------------
*.* Files used to uninstall the product
Installed Files for the 64-bit Driver
This file list assumes a full installation of the 64-bit driver and
documentation.
The installer copies the following files and subdirectories to the
product installation directory, by default:
/opt/Progress/DataDirect/ODBC_64bit:
/<install_dir>/:
----------------
DDODBC.LIC DataDirect license file
license.txt Progress DataDirect license agreement
odbc.csh Setup script for C shell
odbc.ini Sample odbc.ini file
odbcinst.ini Sample odbcinst.ini file
odbc.sh Setup script for Bourne shell
/bin/:
-----
bind28 Db2 bind utility
ddtestlib Test application to check that required
libraries are present and loadable
/bind/LUW/:
-----------
DDODBC_LUW.lst Files for Linux/UNIX/Windows
DDOC510A.bnd
DDOC510B.bnd
DDOC510C.bnd
DDOR510A.bnd
DDOR510B.bnd
DDOS510A.bnd
DDOR510C.bnd
DDOS510B.bnd
DDOS510C.bnd
DDOU510A.bnd
DDOU510B.bnd
DDOU510C.bnd
/bind/iSeries/:
---------------
DDODBC_400.lst Files for Db2 for i
DDOC510A.bnd
DDOC510B.bnd
DDOC510C.bnd
DDON510A.bnd
DDON510B.bnd
DDON510C.bnd
DDOR510A.bnd
DDOR510B.bnd
DDOR510C.bnd
DDOS510A.bnd
DDOS510B.bnd
DDOS510C.bnd
DDOU510A.bnd
DDOU510B.bnd
DDOU510C.bnd
DDOV5R2.savf
DDOV5R3.savf
DDOV5R4.savf
DDOV6R1.savf
DDOV7R1.savf
CfODBC iSeries Manual Package Creation Instructions.txt
/bind/zOS/:
-----------
DDODBC_MVS.LST Files for z/OS
CNTLFILE.xmit
DBRMFILE.xmit
DDOC510A.bnd
DDOC510B.bnd
DDOC510C.bnd
DDOR510A.bnd
DDOR510B.bnd
DDOR510C.bnd
DDOS510A.bnd
DDOS510B.bnd
DDOU510A.bnd
DDOU510B.bnd
DDOU510C.bnd
DDOS510C.bnd
CfODBC zOS Manual Package Creation Instructions.txt
/FIXES/:
--------
fixes8.0.txt List of fixes since last release
/help:
------
*.html HTML redirects to online connector help systems
and documentation resources
/include/:
---------
odbcinst.h Include files
qesqlext.h
sql.h
sqlext.h
sqltypes.h
sqlucode.h
sqlunx.h
/install/:
---------
*.* Files associated with the installer program
/lib/:
-----
dddb228.so Db2 WP driver
ddopenssl30.so TLS/SSL support file (OpenSSL library
version 3.0) [libddopenssl30.a on AIX]
ddopenssl.so TLS/SSL support file (OpenSSL library
version 3.5) [libddopenssl.a on AIX]
ddtrc28.so Progress DataDirect trace library
fips.so Support file for FIPS provider
libddicu.a Unicode conversion tables for AIX platforms
libddicu.so Unicode conversion tables for Linux, Solaris
and limited availability platforms
libddicu28.so Unicode conversion tables for limited
availability platforms
libodbc.so ODBC Driver Manager
libodbcinst.so ODBC Installer
openssl.cnf Configuration file for FIPS provider
/locale/en_US/LC_MESSAGES/:
--------------------------
dddb228.mo Db2 WP driver message file
dddb228.po Db2 WP driver message file source
odbc.m ODBC Driver Manager message file
odbc.po ODBC Driver Manager message source
/NOTICES/:
---------
ODBC for Db2 v8.0
notices.txt Third-party vendor license agreements
/READMES/:
---------
ODBC for Db2 v8.0
readme.txt This file
/samples/bulk/:
---------------
bulk Bulk application
bulk.c Bulk example source
bulk.mak Bulk example make file
bulk.txt Bulk example description
ddlogging.properties Log configuration file for the
Db2 driver
/samples/bulkstrm/:
-------------------
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulkstrm Bulk streaming example application
bulkstrm.txt Bulk streaming example description
main.cpp Bulk streaming example source
msgprintf.hpp Bulk streaming example header
streambulk.mak Bulk streaming example make file
ddlogging.properties Log configuration file for the
Db2 driver
/samples/example/:
-------------------
example Example application
example.c Example source
example.h Example header
example.mak Example make file
/samples/trn/:
--------------
makefile Translation Library example make file
readme.trn Translation Library example description
translat.c Translation Library example source file
/tools/:
-------
ddencpwd Password Encryption Tool
ddextu License Extender utility
ddprocinfo Processor Information utility
/uninstall/:
------------
*.* Files used to uninstall the product
~~~~~~~~~~~~~~
April 2026
End of README