Db2 JDBC 5.1.4

     README
     Progress(R) DataDirect(R) 
     Progress(R) DataDirect(R) for JDBC(TM) for IBM Db2(TM) Driver
     Release 5.1.4
     February 2026


***********************************************************************
Copyright (C) 2026 Progress Software Corporation and/or its 
subsidiaries or affiliates. All Rights Reserved.

***********************************************************************


CONTENTS

Post-GA Product Announcements
Requirements
Installation Directory
Data Source and Platform Support
Changes Since 5.1.4 GA 
Changes for 5.1.4 GA
Notes, Known Problems, and Restrictions
Documentation 
Installed Files


     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

* A supported Java Virtual Machine (JVM) must be defined on your system path.

* 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 a JVM that is Java SE 8 or higher, including Oracle JDK,
  OpenJDK, and IBM SDK (Java) distributions.



     Installation Directory

The default installation directory for the driver is:

* Windows:
  C:\Program Files\Progress\DataDirect\JDBC

* UNIX/Linux:
  /opt/Progress/DataDirect/JDBC
  
  Note: For UNIX/Linux, if you do not have access to "/opt", your user's home
  directory will take the place of this directory.


    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    
  
  
    Changes Since 5.1.4 GA 

Installer JRE Requirement
-------------------------
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.
 
Note: 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

Installer Upgrade
-----------------
The installer program has been enhanced to use a more modern and
secure technology. As a result of this enhancement: 

* The default installation location has been changed to:

  - For Windows:
    C:\Program Files\Progress\DataDirect\JDBC

  - For UNIX/Linux:
    /opt/Progress/DataDirect/JDBC

* The new installer program does not support upgrading installations 
  made with earlier versions of the installer. You will need to 
  uninstall the existing installation and reinstall with the new 
  installer to resume upgrades in the same directory. 

* The references to the old installation location will not be
  changed to the new installation location automatically. To 
  learn how to update them, refer to the best practices article 
  at https://community.progress.com/s/.

* License keys you have used for the retired 5.1 installer cannot 
  be used with the new installer. Request new keys by either 
  contacting the Progress DataDirect Technical Support team or visiting
  https://www.progress.com/datadirect-connectors/request-upgrade.

Signed Installer Packages
-------------------------
Starting June 20, 2022, installer packages signed with a digital signature 
will be available for download from OEM FTP. For instructions on verifying 
installer package signatures, refer to 
https://community.progress.com/s/article/Signed-packages-for-DataDirect-OEMs.

Documentation
-------------
Any product package made available after August 7, 2020 will not include the
HTML help system or user's guide PDF. The Progress DataDirect Connect Series for
JDBC documentation set is available via product and data source tiles from the
Progress Information Hub:
https://docs.progress.com

While the product packages will not include these documentation items, the
installation Help directory will provide an HTML redirect for direct access
to the HTML help.

Timestamp Logging in Spy and JDBC Packet Logs
---------------------------------------------
The driver has been enhanced to include timestamp in the Spy and JDBC packet
logs by default. If required, you can disable the timestamp logging by 
specifying the following at connection: For Spy logs, set 
spyAttributes=(log=(file)Spy.log;timestamp=no) and for JDBC packet logs,
set ddtdbg.ProtocolTraceShowTime=false.

Interactive SQL for JDBC 
------------------------
Interactive SQL for JDBC (JDBCISQL) is now installed with the product. 
JDBCISQL is a command-line interface that supports connecting your driver
to a data source, executing SQL statements and retrieving results in a 
terminal. This tool provides a method to quickly test your drivers in an 
environment that does not support GUIs. 

Java SE 7 Support
-----------------
Java SE 7 has reached the end of its product life cycle and will no longer 
receive generally available security updates. As a result, the drivers will no 
longer support JVMs that are version Java SE 7 or earlier. Support for 
distributed versions of Java SE 7 and earlier will also end, including
IBM SDK (Java Edition). 

Kerberos krb5.conf File
-----------------------
The driver supports Kerberos authentication. It no longer sets the 
java.security.krb5.conf system property to force the use of the krb5.conf 
file installed with the driver jar files in the /lib directory of the product 
installation directory. For thelatest instructions on configuring the drivers 
for Kerberos, see the "Notes, Known Problems, and Restrictions" section below.

Statement Pooling
-----------------
Added the RegisterStatementPoolMonitorMBean connection property. Note that the
driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
You must set RegisterStatementPoolMonitorMBean to true to register the Statement
Pool Monitor and manage statement pooling with standard JMX API calls.

Support for Generic Security Standard (GSS) Plug-in
---------------------------------------------------
The driver has been enhanced to support the Generic Security Standard (GSS) 
  plug-in for authentication. The plug-in consists of a set of APIs that you can
  implement to customize your authentication requirements and interoperate with 
  various security methods. You can configure a GSS plug-in using the refreshed 
  AuthenticationMethod property and the new GSSPluginName and GSSPluginObject 
  properties.

HTTP Proxy Support
-------------------  
The driver has been enhanced to support connecting to a proxy server through
an HTTP connection. HTTP proxy support is configurable with the new 
ProxyHost, ProxyMode, ProxyPassword, ProxyPort, and ProxyUser connection 
properties.

KeepAlive Connection Property
-----------------------------
The KeepAlive connection property has been added to the driver. 
Enabling the KeepAlive property allows the client to keep idle TCP
connections active by periodically passing packets to the server.

Support for Windows Defender Credential Guard
---------------------------------------------
The driver has been enhanced to support Windows Defender Credential
Guard when using Kerberos Authentication.  

AlternateID Connection Property - Changed Behavior
--------------------------------------------------
For DB2 for z/OS, the AlternateID connection property has been modified to set
the name of the schema in the DB2 CURRENT SCHEMA special register instead of
the DB2 CURRENT SQLID special register. AlternateID now sets the name of the
schema in the CURRENT SCHEMA special register for DB2 for i, DB2 for
Linux/UNIX/Windows, and DB2 for z/OS.

Cursor Type OUT Parameters
--------------------------
Added support for cursor type OUT parameters for DB2 for Linux, UNIX, Windows
stored procedures.


    Changes for 5.1.4 GA

Enhancements
------------
* The connection properties RandomGenerator and SecureRandomAlgorithm have been
  added to the driver.

  * RandomGenerator allows you to specify the type of random number generator
    (RNG) the database uses for secure seeding.

  * SecureRandomAlgorithm can be used to specify the SecureRandom number
    generation algorithm used for secure seeding with implementations of JDK 8
    or higher when RandomGenerator is set to secureRandom.

* To avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE
  vulnerability, the CryptoProtocolVersion connection property can be used with
  the driver.

* Support for result set holdability has been added to the driver.


	Notes, Known Problems, and Restrictions

The following are notes, known problems, and restrictions for the 5.1.4 
Release of the driver.

BLOB, CLOB, and DBCLOB Type Limitation
-------------------------------------
Unlike previous versions of the DB2 driver, the 5.1.0 version of the driver 
does not buffer the input stream if a parameter is a BLOB, CLOB, or DBCLOB
type.

ResultSetMetaData.getObject Method
-----------------------------------
The ResultSetMetaData.getObject method returns a Long object instead of a
BigDecimal object when called on BIGINT columns. In versions previous to
DataDirect Connect Series for JDBC 3.5, the DataDirect Connect for JDBC DB2
driver returned a BigDecimal object.

No Support for Scroll-sensitive Result Sets
-------------------------------------------
Scroll-sensitive result sets are not supported. Requests for scroll-sensitive
result sets are downgraded to scroll-insensitive result sets when possible.
When this happens, a warning is generated.

Implicit Conversions of the Parameter Values
--------------------------------------------
The DB2 driver must be able to determine the data type of the column or stored
procedure argument to implicitly convert the parameter value. Not all DB2
database versions support getting parameter metadata for prepared statements.
Implicit conversions are not supported for database versions that do not
provide parameter metadata for prepared statements.

GSS Plug-in Authentication Implementation 
-----------------------------------------
The following limitations apply to connection pooling through LDAP using GSS 
authentication:

* GssPluginObject cannot be specified in the connection URL.

* GssPluginObject cannot be stored in LDAP for pooled connections.

DashDB Constraints for Tables
-----------------------------
By default, dashDB does not enforce constraints for tables. As a result, dashDB
will not enforce uniqueness on the new tables, and therefore, incorrect or 
unexpected results can occur if table data violates the not-enforced 
constraint. If you want to enforce uniqueness, specify the ENFORCED parameter 
when creating or altering unique or referential constraints, such as primary 
keys and foreign keys. 

Using Kerberos Authentication with DB2 V10.5 for Linux, UNIX, and Windows
-------------------------------------------------------------------------
The DB2 driver cannot authenticate with Keberos due to the behavior of the
DB2 V10.5 for Linux, UNIX, and Windows server. The issue has been opened with
IBM: PMR 06453,756,000.

Executing Scripts (for UNIX Users)
----------------------------------
If you receive an error message when executing any DataDirect Connect for JDBC
shell script, make sure that the file has EXECUTE permission. To do this, use
the chmod command. For example, to grant EXECUTE permission to the
testforjdbc.sh file, change to the directory containing testforjdbc.sh and
enter:

chmod +x testforjdbc.sh

Distributed Transactions Using JTA
----------------------------------
If you are using JTA for distributed transactions, you may encounter 
problems when performing certain operations.

JDBC Methods
------------
The following notes on JDBC methods apply generally to Progress DataDirect for
JDBC drivers.

* The DataDirect Connect Series for JDBC drivers allow PreparedStatement.setXXX
  methods and ResultSet.getXXX methods on Blob/Clob data types, in addition to
  the functionality described in the JDBC specification. The supported
  conversions typically are the same as those for LONGVARBINARY/LONGVARCHAR,
  except where limited by database support.

* Calling CallableStatement.registerOutputParameter(parameterIndex, sqlType)
  with sqlType Types.NUMERIC or Types.DECIMAL sets the scale of the output
  parameter to zero (0). According to the JDBC specification, calling 
  CallableStatement.registerOutputParameter(parameterIndex, sqlType, scale) is
  the recommended method for registering NUMERIC or DECIMAL output parameters. 

* When attempting to create an updatable, scroll-sensitive result set for a
  query that contains an expression as one of the columns, the driver cannot
  satisfy the scroll-sensitive request. The driver downgrades the type of the
  result returned to scroll-insensitive.

* The DataDirect Connect Series for JDBC drivers support retrieval of output
  parameters from a stored procedure before all result sets and/or update counts
  have been completely processed. When CallableStatement.getXXX is called,
  result sets and update counts that have not yet been processed by the
  application are discarded to make the output parameter data available.
  Warnings are generated when results are discarded.

* The preferred method for executing a stored procedure that generates result
  sets and update counts is using CallableStatement.execute(). If multiple
  results are generated using executeUpdate, the first update count is returned.
  Any result sets prior to the first update count are discarded. If multiple
  results are generated using executeQuery, the first result set is returned.
  Any update counts prior to the first result set are discarded. Warnings are
  generated when result sets or update counts are discarded. 

* The ResultSet methods getTimestamp(), getDate(), and getTime() return
  references to mutable objects. If the object reference returned from any of
  these methods is modified, re-fetching the column using the same method
  returns the modified value. The value is only modified in memory; the database
  value is not modified.

  
     Documentation 

PROGRESS DATADIRECT CONNECT SERIES FOR JDBC DOCUMENTATION SET
-------------------------------------------------------------
The Progress DataDirect Connect Series for JDBC documentation set is available
via product and data source tiles from the Progress Information Hub:
https://docs.progress.com

You can access the online help system directly via the HTML redirect in the
installation Help directory.


     Installed Files

When you extract the contents of the installation download package to your
installer directory, you will notice the following files that are required to
install the driver:

Windows:
--------
* PROGRESS_DATADIRECT_JDBC_INSTALL.exe
* DriverModules
  - PROGRESS_DATADIRECT_JDBC_DB2_5.1.4_INSTALL.iam.zip
  - PROGRESS_DATADIRECT_JDBC_COMMON_5.1.4_INSTALL.iam.zip

Non-Windows:
------------
* PROGRESS_DATADIRECT_JDBC_INSTALL.jar
* DriverModules
  - PROGRESS_DATADIRECT_JDBC_DB2_5.1.4_INSTALL.iam.zip
  - PROGRESS_DATADIRECT_JDBC_COMMON_5.1.4_INSTALL.iam.zip

When you install the driver, the installer creates the following directories and
files in the product installation directory in the default installation
directory or in an installation directory you specify, represented by
INSTALL_DIR.


INSTALL_DIR/:
-------------
LicenseTool.jar            Product license file manager

ddprocinfo.exe             Windows executable to start the Processor Information
                           Utility

ddprocinfo                 UNIX/Linux script to start the Processor Information
                           Utility

fixes.txt                  Information on resolved issues for Progress
                           DataDirect for JDBC drivers


INSTALL_DIR/DB2/bind:
---------------------
iSeries/*.*                Files for explicitly creating DB2 packages on
                           DB2 for i

LUW/*.*                    Files for explicitly creating DB2 packages on
                           Linux/UNIX/Windows

zOS/*.*                    Files for explicitly creating DB2 packages on z/OS


INSTALL_DIR/Examples/Bulk/:
---------------------------
Load From File/bulkLoadFileDemo.java
                           Java source example for bulk loading from a CSV file

Load From File/load.txt    Sample data for the example

Streaming/bulkLoadStreamingDemo.java
                           Java source example for bulk loading from a result
                           set

Threaded Streaming/bulkLoadThreadedStreamingDemo.java
                           Java source example for multi-threaded bulk loading
                           from a result set

Threaded Streaming/README.txt
                           Instructions on how to use the thread.properties file

Threaded Streaming/thread.properties
                           Properties file for the example


INSTALL_DIR/Examples/JNDI/:
---------------------------
JNDI_FILESYSTEM_Example.java
                           Example Java(TM) source file

JNDI_LDAP_Example.java     Example Java source file


INSTALL_DIR/help/:
------------------
*.html                     HTML redirects to driver help systems


INSTALL_DIR/jdbcisql/:
----------------------
jdbcisql.bat               Batch file to start JDBC iSQL 

jdbcisql.ini               Configuration file for JDBC iSQL 

jdbcisql.jar               Java program to start JDBC iSQL 

jdbcisql.sh                Shell script to start JDBC iSQL 


INSTALL_DIR/install/: 
---------------------
.psc_dd_inst_reg.xml       Support file for the installation logs

logs/*.*                   Log file generated upon installation 


INSTALL_DIR/lib/51:
------------------
db2.jar                    DB2 Driver and DataSource classes

db2packagemanager.jar      DataDirect DB2 Package Manager jar file

db2packagemanager.bat      Batch file to start the DataDirect DB2 Package
                           Manager

db2packagemanager.sh       Shell script to start the DataDirect DB2 Package
                           Manager

JDBCDriverLogin.conf       Kerberos configuration file used to specify the JAAS
                           login module


INSTALL_DIR/NOTICES/:
---------------------
JDBC for Db2 v5.1.4 notices.txt
                           Third party agreement information


INSTALL_DIR/pool manager/:
--------------------------
pool.jar                   All DataDirect Connection Pool Manager classes


INSTALL_DIR/READMES/:
---------------------
JDBC for Db2 v5.1.4 readme.txt
                           This file
						   
						   
INSTALL_DIR/testforjdbc/:
-------------------------
Config.txt                 Configuration file for DataDirect Test

ddlogging.properties       Logging properties file

testforjdbc.bat            Batch file to start DataDirect Test

testforjdbc.sh             Shell script to start DataDirect Test

lib/testforjdbc.jar        DataDirect Test classes


INSTALL_DIR/uninstall/:
-----------------------
.com.zerog.registry.xml    Support file for the uninstaller

.psc_dd_uninst_reg.xml     Support file for the uninstaller

InstallScript.iap_xml      Support file for the uninstaller

installvariables.properties
                           Support file for the Windows uninstaller

Uninstall_JDBC.exe         Windows uninstaller

Uninstall_JDBC.lax         Support file for the Windows uninstaller

uninstaller.jar            Java uninstaller

db2/*.*                    Support files for the uninstaller

resource/*.*               Resource files for the Windows uninstaller


February 2026
================
End of README