     JDBCREADME.TXT

     DataDirect Technologies

     DataDirect Connect for JDBC

     Release 3.7 (Build 0048)

     October 2008



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

Copyright (c) 2001-2008 Progress Software Corporation. 

All rights reserved. 



DataDirect Connect is a registered trademark of Progress Software 

Corporation in the U.S. and other countries. Any other trademarks or 

service marks contained herein are the property of their 

respective owners.

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



This README file contains additional database driver information not 

included in the DataDirect Connect(R) for JDBC(TM) documentation or the 

online help.



CONTENTS



Changes Since 3.7 Service Pack 1 (SP1)

Changes Since 3.7 GA

Release 3.7 Features

Installation

Available DataDirect Connect for JDBC Drivers

Notes, Known Problems, and Restrictions

Using the Online Documents

DataDirect Connect for JDBC Files

Third-Party License Agreements





     Changes Since 3.7 Service Pack 1 (SP1)



- The DB2 driver has been certified against DB2 UDB V6R1 for iSeries via DRDA.



- The SQL Server driver has been certified against SQL Server 2008.



- The DB2 driver has been certified against DB2 9.5 for Linux/UNIX/Windows.



- Added a new String connection option, CurrentFunctionPath, to specify 

  the default path that is used to resolve unqualified function names 

  and data type references in dynamically prepared SQL statements. 

  It also is used to resolve unqualified stored procedure names 

  specified in CALL statements. The value of this property is a 

  comma-separated list of DB2 schema names. This property sets the 

  DB2 CURRENT PATH special register. The default is null.





     Changes Since 3.7 GA



New Features and Enhancmements

------------------------------

* New MySQL driver

* Support for the following new database versions:

  - DB2 v9.1 for z/OS

  - Informix 11

  - Oracle 11g

* DB2 driver features and enhancements:

  - New Database connection property synonym for the DatabaseName 

    connection property

  - Ability to use the DatabaseName connection property for all 

    DB2 versions

  - Support for new DB2 Graphic data types

  - Support for DB2 v9.1 for z/OS, including support for:

    * New DB2 v9.1 for z/OS data types

    * Distributed transactions

    * SQL Procedures

    * IPv6 addresses

* Informix driver features and enhancements:

  - New Database connection property synonym for the DatabaseName

    connection property

* Oracle driver features and enhancements:

  - Support for Oracle 11g, including support for server result set

    caching and XQuery functions.

* Microsoft SQL Server and Sybase driver features and enhancements:

  - New Database connection property synonym for the DatabaseName 

    connection property.

  - New LongDataCacheSize connection property controls whether the 

    driver caches long data (images, pictures, long text, or binary 

    data) in result sets.



For more information about these changes, refer to the DATADIRECT 

CONNECT FOR JDBC USER'S GUIDE AND REFERENCE SUPPLEMENT.



New MySQL Driver

----------------

See "DataDirect Connect(R) for JDBC Files" later in this readme for the 

complete list of files, including files for the MySQL driver.





     Release 3.7 Features



All Drivers

-----------

     * Support for the following JDBC 4.0 features:

       - Connection validation

       - Client information storage and retrieval

       - Auto-load driver classes (when using Java SE 6)

     * IPv6 support.

     * Enhanced support for returning auto-generated keys.

     * New integrated statement pooling monitoring feature.

     * Hibernate certification.

     * Reauthentication and Delegation of Credentials support in the 

       DataDirect Connection Pool Manager.

     * New ConvertNull connection option to control how 

       data conversions are handled for null values.

     * New ImportStatementPool connection option for configuring a 

       file to load the contents of the statement pool.  

     * New MaxStatements synonym for the MaxPooledStatements 

       connection option.

     * New QueryTimeout connection option for setting a default 

       query timeout.

     * Performance enhancements.



         

DB2

---

     * Support for DB2 V9.1 for Linux/UNIX/Windows, including 

       support for the new XML data type.

     * Support for DB2 UDB V5R4 on iSeries including:

       - JTA support

       - 2-MB length for SQL statements

       - 128-byte column names

       - RAISE_ERROR function

       - New timestamp identifier format

       - SQLDA record changes

       - Blanks in hexadecimal literals

       - Instead of triggers

       - ENCRYPT_TDES function

     * Reauthentication support for switching the user associated with 

       a connection to another user. 

     * Enhanced Kerberos authentication support:

       - Support for DB2 UDB for z/OS

       - Support for MIT Kerberos for DB2 UDB for Linux/UNIX/Windows 

         and DB2 UDB for z/OS.

     * DB2-specific encryption support.

     * New EncryptionMethod connection option for configuring 

       data encryption across the network.

       

Informix

--------

     * New FetchBufferSize connection option for configuring 

       The size (in bytes) of the fetch buffer.

     * Support for multiple output parameters for stored procedures.



Oracle

------

     * Reauthentication support for switching the user associated with 

       a connection to another user. 

     * Kerberos authentication support, including support for 

       Windows Active Directory and MIT Kerberos.

     * SSL encryption support.

     * Support for Insert/Update/Delete statements with a 

       RETURNING clause.

     * Asynchronous Commit support for Oracle 10g R2.

     * Enhanced support for returning and inserting/updating 

       data stored in XML columns.

     * Support for UROWID data type.

     * New EncryptionMethod connection option for configuring 

       data encryption across the network.

     * New connection options for configuring how the driver 

       implements SSL encryption, including:

       - ValidateServerCertificate and HostNameInCertificate 

         connection options for configuring certificate validation 

         behavior.

       - TrustStore and TrustStorePassword connection options 

         For configuring truststore information.

       - KeyStore, KeyStorePassword, and KeyPassword connection options

         for configuring keystore information for SSL client 

         authentication.

     * New SysLoginRole connection option for configuring whether the 

       user is logged on the database with the Oracle system privilege 

       SYSDBA or the Oracle system privilege SYSOPER.



SQL Server

----------

     * Reauthentication support for switching the user associated with 

       a connection to another user. 

     * Kerberos authentication support for MIT Kerberos.

     * SSL encryption support.

     * New EncryptionMethod connection option for configuring 

       data encryption across the network.

     * New connection options for configuring how the driver 

       implements SSL encryption, including:

       - ValidateServerCertificate and HostNameInCertificate 

         connection options for configuring certificate validation 

         behavior.

       - TrustStore and TrustStorePassword connection options 

         for configuring truststore information.

     * New DescribeParameters connection option to control whether 

       the driver will attempt to determine, at execute time, how to 

       send String parameters to the server based on the database 

       data type.



Sybase

------

     * Support for Sybase 12.5.4.

     * SSL encryption support.

     * Support for DOUBLE PRECISION data type.

     * New EncryptionMethod connection option for configuring 

       data encryption across the network.

     * New connection options for configuring how the driver 

       implements SSL encryption, including:

       - ValidateServerCertificate and HostNameInCertificate 

         connection options for configuring certificate validation 

         behavior.

       - TrustStore and TrustStorePassword connection options 

         for configuring truststore information.

     * New LongDataCacheSize connection option controls whether 

       the driver caches long data in results sets.

     * New PacketSize connection option for configuring the 

       database protocol packet size.

     * New TransactionMode connection option to control 

       how the driver delimits the start of a local transaction.



Enhancement Requests and Fixes

------------------------------

The following enhancement requests and fixes have been implemented 

in this release:



Issue # | Component Modified | Description of Issue



DEF0001394 | All Drivers | DriverPropertyInfo description for the 

InsensitiveResultSetBufferSize property has a misspelling in it.



DEF0001413 | All Drivers | Support auto-generated key methods which 

take column names and column indexes.



DEF0001487 | All Drivers | Support isFirst method for forward only 

result sets. 



DEF0001638 | All Drivers | Support IPv6.



DEF0001875 | All Drivers | Provide a way to clear the contents of a 

connection’s statement pool.



DEF0002908 | All Drivers | Provide an option to set the default value 

for query time out or to disable the query timeout functionality.



DEF000766 | DB2, Oracle, SQL Server, Sybase | Support Kerberos OS 

authentication from UNIX.



DEF0001669 | DB2, Oracle, SQL Server | Support Reauthentication / 

Impersonation.



DEF0000133 | Oracle, SQL Server, Sybase | Support SSL encryption.



DEF0002644 | Oracle, SQL Server | Build 64-bit Authentication DLL for 

x64 platform.



DEF0001474 | DB2 | Support JTA when connected to DB2 for AS/400. 



DEF000505 | Oracle | Support the Oracle UROWID data type.



DEF0001262 | Oracle | Logon with administrative privileges, sysdba for 

example.



DEF0001983 | Oracle | Support RETURNING clause on INSERT, UPDATE and 

DELETE statements for Oracle.



DEF0002838 | SQL Server | Cannot return a VARCHAR(max) data type from a 

function or stored procedure.



DEF0002875 | SQL Server | "Unsupported data conversion" occurs using 

getDate().





     Installation



For All Users

--------------

* A complete installation of DataDirect Connect for JDBC requires 

approximately 13 MB of hard disk space.



* At a minimum, J2SE 1.3 or higher is required to use 

  DataDirect Connect for JDBC. Standard installations of J2SE on some 

  platforms do not include the jar file containing the extended 

  encoding set that is required to support some of the less common 

  database code pages. To verify whether your J2SE version provides 

  extended code page support, check your J2SE installation for the 

  following file:



  - For J2SE 1.3 and 1.3.x, i18n.jar must be installed in the 

    lib subdirectory of your J2SE installation directory.



  - For J2SE 1.4 and higher, charsets.jar must be installed 

    in the lib subdirectory of your J2SE installation directory.



  If you do not have the required file for your J2SE version, 

  make sure that you install the international version of J2SE.



* The PDF versions of the DataDirect Connect for JDBC books are 

  no longer an installable option with the product for both the 

  GUI installer and the command-line installer (the –ib flag has 

  been deprecated). The PDF documentation is provided on the 

  product CD and also on the DataDirect Technologies Web site:



  http://www.datadirect.com/techres/jdbcproddoc/index.ssp



  The HTML versions of the books are installed in the help subdirectory 

  of your product installation directory.



* After you have started the installation process, as described in the 

  DATADIRECT CONNECT FOR JDBC INSTALLATION GUIDE (JDBCIG.PDF), a 

  progress bar is displayed on the screen. If you choose to cancel the 

  installation at this stage, files that have already been copied to 

  your machine will not be removed. You must delete these files 

  manually from the installation directory.



* The DataDirect Connect for JDBC installer accepts multiple product 

  keys. For details, refer to the DATADIRECT CONNECT FOR JDBC 

  INSTALLATION GUIDE (JDBCIG.PDF).



For UNIX Users

--------------

If you receive an error message when executing any DataDirect Connect 

for JDBC shell script (.sh files), including installer.sh, make sure 

that the file has EXECUTE permission. To do this, use the chmod 

command. For example, to grant EXECUTE permission to the installer.sh 

file, change to the directory containing installer.sh and enter:



chmod +x installer.sh





     Available DataDirect Connect for JDBC Drivers



See the DATADIRECT CONNECT FOR JDBC INSTALLATION GUIDE (JDBCIG.PDF) for 

a complete list of supported databases.



Drivers

-------

DB2 (db2.jar) 

Informix (informix.jar) 

MySQL (mysql.jar)

Oracle (oracle.jar) 

SQL Server (sqlserver.jar) 

Sybase (sybase.jar)





     Notes, Known Problems, and Restrictions



The following are notes, known problems, or restrictions with 

Release 3.7 of DataDirect Connect for JDBC.



Starting the Performance Tuning Wizard

---------------------------------------

When starting the Performance Tuning Wizard, security features set in 

your browser can prevent the Performance Wizard from launching. A 

security warning message is displayed. Often, the warning message 

provides instructions for unblocking the Performance Wizard for the 

current session. To allow the Performance Wizard to launch without 

encountering a security warning message, the security settings in your 

browser can be modified. Check with your system administrator before 

disabling any security features.



Distributed Transactions Using JTA

----------------------------------

If you are using JTA for distributed transactions, you may encounter 

problems when performing certain operations, as shown in the following 

examples:



SQL SERVER 7



1. Problem: SQL Server 7 does not allow resource sharing because it 

cannot release the connection to a transaction until it commits or 

rolls back.



  xaResource.start(xid1, TMNOFLAGS)

  ...

  xaResource.end(xid1, TMSUCCESS)

  xaResource.start(xid2, TMNOFLAGS) ---> fail

 

2. Problem:  Table2 insert rolls back. It should not roll back because 

it is outside of the transaction scope.



  xaResource.start(xid1, TMNOFLAGS)

  stmt.executeUpdate("insert into table1 values (1)");

  xaResource.end(xid1, TMSUCCESS)

 

  stmt.executeUpdate("insert into table2 values (2)");

 

  xaResource.prepare(xid1);

  xaResource.rollback(xid1);

 

SQL SERVER 7 and SQL SERVER 2000



1. Problem: Recover should not return xid1 because it is not yet 

prepared.



  xaResource.start(xid1, TMNOFLAGS)

  xaResource.recover(TMSTARTRSCAN) ---> returns xid1 transaction



This problem has been resolved in DTC patch QFE28, fix number 

winse#47009, "In-doubt transactions are not correct removed from the 

in-doubt transactions list".



This Microsoft issue is documented at 

http://support.microsoft.com/default.aspx?scid=kb;en-us;828748.



All Drivers

-----------

* The DataDirect Connect for JDBC drivers no longer accept connection 

  URLs in the format: 

       

     jdbc:<database_name>://<servername>:<port>



  For example, the following URLs are no longer valid:



     jdbc:db2://myserver:50000

     jdbc:informix://myserver:2003

     jdbc:oracle://myserver:1521

     jdbc:sqlserver://myserver:1433

     jdbc:sybase://myserver:5000

       

  Support for URLs in this format has been deprecated for several 

  releases, but the drivers have continued to accept URLs in this 

  format for backward compatibility. DataDirect Connect for JDBC 

  drivers cannot continue to accept URLs in this format because it 

  causes conflicts with the JDBC drivers provided by the 

  database vendors.



  The supported URL format for DataDirect Connect for JDBC drivers is:



     jdbc:datadirect:<database_name>://<servername>:<port>



  See the DATADIRECT CONNECT FOR JDBC USER'S GUIDE AND REFERENCE 

  (JDBCREF.PDF) for details on specifying connection URLs.



* The DataDirect Connect 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 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.



DB2 (All Platforms)

-------------------

* The ResultSetMetaData.getObject method returns a Long object instead 

  of a BigDecimal object when called on BIGINT columns. In versions 

  previous to DataDirect Connect for JDBC 3.5, the DataDirect Connect 

  for JDBC DB2 driver returned a BigDecimal object.



* 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 

  indicating that result set scrollability has been downgraded.



* 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.



DB2 (Windows/UNIX/Linux)

------------------------

* Except for DB2 v8.1 and higher for Linux/UNIX/Windows, Clob 

  data types are limited to a maximum length of 32714 bytes because 

  of DRDA listener limitations.



* Except for DB2 v8.1 and higher for Linux/UNIX/Windows, Blob 

  data types are not supported because of DRDA listener limitations.



DB2 (iSeries)

-------------

Except for DB2 V5R2 and higher for iSeries, Blob and Clob data types 

are not supported.



Oracle

------

* If you install the Oracle driver and want to take advantage of JDBC 

  distributed transactions through JTA, you must install 

  Oracle version 8.1.7 or higher.



* Because JDBC does not support a cursor data type, the Oracle driver 

  returns REF CURSOR output parameters to the application as 

  result sets. For details about using REF CURSOR output parameters 

  with the driver, refer to the DATADIRECT CONNECT FOR JDBC USER'S 

  GUIDE AND REFERENCE (JDBCREF.PDF).



* By default, values for TIMESTAMP WITH TIME ZONE columns cannot be 

  retrieved using the ResultSet.getTimestamp method because the 

  time zone information is lost. The Oracle driver returns NULL when 

  the getTimestamp method is called on a TIMESTAMP WITH TIME ZONE 

  column and generates a SQLException. For details about using the 

  TIMESTAMP WITH TIME ZONE data type with the driver, refer to the 

  DATADIRECT CONNECT FOR JDBC USER'S GUIDE AND REFERENCE (JDBCREF.PDF). 



* The Oracle driver describes columns defined as FLOAT or FLOAT(n) as a 

  DOUBLE SQL type. Previous to DataDirect Connect for JDBC 3.5, the 

  driver described these columns as a FLOAT SQL type. Both the DOUBLE 

  type and the FLOAT type represent a double precision floating 

  point number. This change provides consistent functionality with the 

  DataDirect Connect for ODBC Oracle driver. The TYPE_NAME field that 

  describes the type name on the Oracle database server was changed 

  from number to float to better describe how the column was created.



SQL Server

----------

* Microsoft SQL Server 7 and SQL Server 2000 Only: Although the 

  SQL Server driver fully supports the auto-generated keys feature as 

  described in the Microsoft SQL Server chapter of the DATADIRECT 

  CONNECT FOR JDBC USER'S GUIDE AND REFERENCE, some third-party 

  products provide an implementation that, regardless of the column 

  name specified, cause the driver to return the value of the identity 

  column for the following methods:



  Connection.prepareStatement(String sql, int[] columnIndexes)

  Connection.prepareStatement(String sql, String[] columnNames) 



  Statement.execute(String sql, int[] columnIndexes)

  Statement.execute(String sql, String[] columnNames)



  Statement.executeUpdate(String sql, int[] columnIndexes)

  Statement.executeUpdate(String sql, String[] columnNames)



  To workaround this problem, set the WorkArounds connection option 

  to 1. When Workarounds=1, calling any of auto-generated keys methods 

  listed above returns the value of the identity column regardless of 

  the name or index of the column specified to the method. If multiple 

  names or indexes are specified, the driver throws an exception 

  indicating that multiple column names or indexes cannot be specified 

  if connected to Microsoft SQL Server 7 or SQL Server 2000.



* If you want to take advantage of JDBC distributed transactions 

  through JTA, you must install JDBC XA Procedures. DataDirect provides 

  the following files to install the XA Procedures: sqljdbc.dll and 

  instjdbc.sql. Refer to the Microsoft SQL Server Driver chapter in 

  the DATADIRECT CONNECT FOR JDBC USER'S GUIDE AND REFERENCE 

  (JDBCREF.PDF) for details and file location.

  

  If you have multiple instances of Microsoft SQL Server on the same 

  machine, you can edit the instjdbc.sql script with a text editor to 

  specify a fully qualified path to the sqljdbc.dll file for a 

  particular instance. For example, if you want to install XA Procedures 

  for an instance named "MSSQL.2," modify the instjdbc.sql script 

  as shown: 



  /*

  **  add references for the stored procedures

  */



  print 'creating JDBC XA procedures'

  go



  sp_addextendedproc 'xp_jdbc_open', 

     'C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\sqljdbc.dll'

  go

  sp_addextendedproc 'xp_jdbc_open2', 

     'C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\sqljdbc.dll'

  go

  sp_addextendedproc 'xp_jdbc_close', 

     'C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\sqljdbc.dll'

  go

  sp_addextendedproc 'xp_jdbc_close2', 

     'C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\sqljdbc.dll'

  go

  sp_addextendedproc 'xp_jdbc_start', 

     'C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\sqljdbc.dll'

  ...



  NOTE: For Microsoft SQL Server 2005, you can use the SQL Server 

  Configuration Manager tool to view Microsoft SQL Server services 

  and determine the fully qualified path to the binn subdirectory of 

  each Microsoft SQL Server instance on a machine. Using the 

  Configuration Manager, right-click on a service and select Properties. 

  Select the Service tab. The path is shown as a value of the Binary Path 

  attribute. For Microsoft SQL Server 2000, you can use the SQL Server 

  Enterprise Manager. Refer to your Microsoft SQL Server documentation 

  for details.



  Once you modify the instjdbc.sql script, run it as described in the 

  DATADIRECT CONNECT FOR JDBC USER'S GUIDE AND REFERENCE (JDBCREF.PDF).



* NTLM authentication requires Microsoft SQL Server 2000, 

  Service Pack 3 or higher when connecting to 

  Microsoft SQL Server 2000. 



* In some cases, when using Kerberos authentication, Windows XP and 

  Windows Server 2003 clients appear to use NTLM instead of Kerberos to 

  authenticate the user with the domain controller. In these cases, 

  user credentials are not stored in the local ticket cache and cannot 

  be obtained by the SQL Server driver, causing the Windows 

  Authentication login to fail. This is caused by a known problem in 

  the Sun 1.4.x JVM; this problem is planned to be fixed in the 1.5 

  JVM. As a workaround, the "os.name" system property can be set to 

  "Windows 2000" when running on a Windows XP or Windows Server 2003 

  machine. For example:



  -Dos.name="Windows 2000"



* To ensure correct handling of character parameters, install 

  Microsoft SQL Server 7 Service Pack 2 or higher.



* Because of the way CHAR, VARCHAR, and LONGVARCHAR data types are 

  handled internally by the driver, parameters of these data types 

  exceeding 4000 characters in length cannot be compared or sorted, 

  except when using the IS NULL or LIKE operators.



* The SendStringParameterAsUnicode connection option is set to true by 

  default. Setting this option to true can negatively impact 

  performance if an application compares strings in SQL and the 

  data stored in the database is not Unicode. On the other hand, 

  setting this option to false can cause data corruption or unexpected 

  comparison results if the data is not stored in the default database 

  character set. Microsoft SQL Server allows you to define columns in a 

  table that uses a character set other than the default database 

  character set. When sending parameter data to the server, the driver 

  does not know that the character set is for the column being compared 

  or modified. Sending parameter data as Unicode will always work, but 

  is subject to the conversion and performance issues mentioned in the 

  Microsoft document: 

  http://support.microsoft.com/default.aspx?scid=kb;en-us;Q271566.



Documentation Errors

--------------------

* On page 470 of the DATADIRECT CONNECT FOR JDBC USER'S GUIDE AND 

  REFERENCE (JDBCREF.PDF), the example showing how to retrieve client 

  information contains an error. The last three lines of the example 

  should read: 

  

  DatabaseMetaData metaData = con.getMetaData();

  metaData.getClientInfoProperties();

  ...

  

  Instead of:

  

  DatabaseMetaData metaData = con.getDatabaseMetaData();

  metaData.getClientInfoProperties();

  ...



* On page 615 of the DATADIRECT CONNECT FOR JDBC USER'S GUIDE AND 

  REFERENCE (JDBCREF.PDF), the documentation incorrectly states 

  the class name of the DataDirect Spy driver. The correct class name 

  is com.ddtek.jdbcspy.SpyDriver.



* On pages 70-72 of the DATADIRECT CONNECT FOR JDBC USER'S GUIDE AND 

  REFERENCE (JDBCREF.PDF), the documentation incorrectly omits the 

  following required permissions in the security file of the Java 2 

  Platform:



  permission java.lang.RuntimePermission "getProtectionDomain";

  permission java.util.PropertyPermission "java.security.krb5.conf",  

    "read";

  permission java.util.PropertyPermission 

    "java.security.auth.login.config", "read, write";

  permission javax.security.auth.AuthPermission 

    "createLoginContext.JDBC_DRIVER_01";



* The DATADIRECT CONNECT FOR JDBC USER'S GUIDE AND REFERENCE 

  (JDBCREF.PDF) incorrectly states that the DB2, Informix, and Sybase 

  drivers support the following forms of the 

  Connection.preparedStatement() method:



  Connection.prepareStatement(String <sql>, int[] <columnIndexes>)

  Connection.prepareStatement(String <sql>, String[] <columnNames>)



  These forms are supported by the Oracle and SQL Server drivers only.





     Using the Online Documents



The DataDirect Connect for JDBC books are provided in PDF and HTML 

versions. The PDF versions are provided on the product CD and also on 

the DataDirect Technologies Web site:



http://www.datadirect.com/techres/jdbcproddoc/index.ssp



You can view the PDF versions using Adobe Reader.



NOTE: To download Adobe Reader from the Web, go to Adobe’s Web site 

at http://www.adobe.com.



The HTML versions of the books are installed in the help subdirectory 

of your product installation directory.





     DataDirect Connect(R) for JDBC Files 



When you extract the contents of the connectjdbc.jar file to your 

installer directory, you will notice the following files that are 

required to install DataDirect Connect for JDBC: 



BuildAdapters.jar          File used to create resource adapters

ddjdbc37.jar               File used to install the  drivers

fixes.txt                  File that lists fixes in this release                           

installer.bat              Batch file to start the GUI installer

installer.sh               Shell script to start the GUI installer

installer.properties	   Support file for the installer

Java Technology Restrictions notice.txt   

                           Copyright notice required by  

                           Sun Microsystems, Inc

JDBCInstaller.jar          File containing the installer                                          

LicenseTool.jar            File required to extend an evaluation 

                           installation

mysqllicense.txt           License agreement for MySQL

jdbcreadme.txt             This file 



When you install DataDirect Connect for JDBC, the installer copies all 

the following directories and files to the product installation 

directory (as determined by the user), represented by INSTALL_DIR.



To INSTALL_DIR/DB2/bind:

------------------------

*.bnd                      Bind files used for creating DB2 packages

DDJDBC_400.lst             List file for creating DB2 packages on 

                           DB2 for iSeries

DDJDBC_LUW.lst             List file for creating DB2 packages on

                           DB2 for Linux/UNIX/Windows 

DDJDBC_MVS.lst             List file for creating DB2 packages on

                           DB2 for z/OS



To INSTALL_DIR/Examples:

------------------------

JNDI_FILESYSTEM_Example.java  Example Java(TM) source files

JNDI_LDAP_Example.java        Example Java source files



To INSTALL_DIR/Examples/connector:

----------------------------------

ConnectorSample.ear       J2EE Application Enterprise Archive file 

                          containing the ConnectorSample application 

connectorsample.htm       "Using DataDirect Connect for JDBC Resource 

                          Adapters" document



To INSTALL_DIR/Examples/connector/graphics:

------------------------------------------

*.*                       Images referenced by the "Using DataDirect 

                          Connect for JDBC Resource Adapters" document 



To INSTALL_DIR/Examples/connector/src:

--------------------------------------

ConnectorSample.jsp       Source for the JavaServer Page used to access 

                          the ConnectorSample application



To INSTALL_DIR/Examples/connector/src/connectorsample:

------------------------------------------------------

ConnectorSample.java      Java source file defining the remote 

                          interface for the ConnectorSample EJB

ConnectorSampleBean.java  Java source file defining the home interface 

                          for the ConnectorSample EJB

ConnectorSampleHome.java  Java source file containing the 

                          implementation for the ConnectorSample EJB



INSTALL_DIR\Help: 

----------------



Help.htm                  HTML help system entry file

\*.*                      Support folders for the HTML help system 



To INSTALL_DIR/lib:

-------------------

db2.jar                   DataDirect Connect for JDBC DB2 Driver 

                          and DataSource classes

informix.jar              DataDirect Connect for JDBC Informix 

                          Driver and DataSource classes

mysql.jar                 DataDirect Connect for JDBC MySQL

                          Driver and DataSource classes

oracle.jar                DataDirect Connect for JDBC Oracle 

                          Driver and DataSource classes

sqlserver.jar             DataDirect Connect for JDBC SQL Server 

                          Driver and DataSource classes

sybase.jar                DataDirect Connect for JDBC Sybase 

                          Driver and DataSource classes

base.jar                  Classes that are used by and required by all 

                          DataDirect Connect for JDBC drivers

util.jar                  Classes that are used by and required by all 

                          DataDirect Connect for JDBC drivers

db2packagemanager.jar     DataDirect DB2 Package Manager jar file 

DDJDBCAuthxx.dll          Windows DLL that provides support for 

                          NTLM authentication (32-bit), where xx is the 

                          Build number of the DLL

DDJDBC64Authxx.dll        Windows DLL that provides support for 

                          NTLM authentication (Itanium 64-bit), 

                          where xx is the Build number of the DLL

DDJDBCx64Authxx.dll       Windows DLL that provides support for 

                          NTLM authentication (AMD64 and 

                          Intel EM64T 64-bit), where xx is the 

                          Build number of the DLL

DB2PackageManager.bat     Batch file to start the DataDirect DB2 

                          Package Manager

DB2PackageManager.sh      Shell script to start the DataDirect DB2 

                          Package Manager

JDBCDriver.policy         Security policy file listing permissions that 

                          must be granted to the driver to use Kerberos 

                          authentication with a Security Manager

JDBCDriverLogin.conf      Configuration file that instructs the driver 

                          to use the Kerberos login module for 

                          authentication

krb5.conf                 Kerberos configuration file





To INSTALL_DIR/lib/JCA:

-----------------------

resource.jar              J2EE Connector Architecture resource adapter 

                          components 



To INSTALL_DIR/lib/JCA/META-INF:

--------------------------------

db2.xml                   DB2 resource adapter deployment descriptor

informix.xml              Informix resource adapter deployment 

                          descriptor

mysql.xml                 MySQL resource adapter deployment descriptor

oracle.xml                Oracle resource adapter deployment descriptor

sqlserver.xml             SQL Server resource adapter deployment 

                          descriptor

sybase.xml                Sybase resource adapter deployment descriptor

MANIFEST.MF               Manifest file



To INSTALL_DIR/pool manager:

----------------------------

pool.jar                  All DataDirect Connection Pool Manager 

                          classes



To INSTALL_DIR/spy:

-------------------

spy.jar                   All DataDirect Spy classes



To INSTALL_DIR/SQLServer JTA/32-bit:

------------------------------------

instjdbc.sql              File for installing JTA Stored Procedures

sqljdbc.dll               File for use with JTA Stored Procedures 

                          (32-bit version)



To INSTALL_DIR/SQLServer JTA/64-bit:

------------------------------------

instjdbc.sql              File for installing JTA Stored Procedures

sqljdbc.dll               File for use with JTA Stored Procedures 

                          (Itanium 64-bit version)



To INSTALL_DIR/SQLServer JTA/x64-bit:

------------------------------------

instjdbc.sql              File for installing JTA Stored Procedures

sqljdbc.dll               File for use with JTA Stored Procedures 

                          (AMD64 and Intel EM64T 64-bit version)



To INSTALL_DIR/sun/lib:

-----------------------

jdbc2_0-stdext.jar        Redistributable Sun Microsystems 

                          components for the JDBC 2.0 Optional Package

jndi.jar                  Redistributable Sun Microsystems components 

                          for JNDI 1.2

jta-spec1_0_1B.jar        Redistributable Sun Microsystems components 

                          for JTA 1.0.1

/fs/*.*                   Redistributable Sun Microsystems components 

                          for the File System JNDI Provider

/ldap/*.*                 Redistributable Sun Microsystems components 

                          for the LDAP JNDI Provider



To INSTALL_DIR/testforjdbc:

---------------------------

Config.txt                Configuration file for DataDirect Test 

testforjdbc.bat           Batch file to start DataDirect Test

testforjdbc.sh            Shell script to start DataDirect Test

/lib/testforjdbc.jar      DataDirect Test classes



To INSTALL_DIR/wizards:

-----------------------

index.html                HTML file to launch the Performance Tuning 

                          Wizard applet

JDBCPerf.jar              Jar file containing the classes for the 

                          Performance Tuning Wizard applet



To INSTALL_DIR/wizards/logo:

----------------------------

ddlogo.gif                DataDirect Technologies logo in the 

                          Performance Tuning Wizard applet





In addition, installation creates the following files in 

INSTALL_DIR/lib if you choose to install the resource adapters:



db2.rar                   DB2 resource archive file

informix.rar              Informix resource archive file

mysql.rar                 MySQL resource archive file

oracle.rar                Oracle resource archive file

sqlserver.rar             SQL Server resource archive file

sybase.rar                Sybase resource archive file





     Third-Party License Requirements/Agreements



The DataDirect Connect for JDBC drivers include certain software 

products made available for distribution by Sun Microsystems, Inc. and 

are subject to the following limitation:

 

Java(R) Technology Restrictions. You may not modify the Java 

Platform Interface ("JPI", identified as classes contained within the 

"java" package or any subpackages of the "java" package), by creating 

additional classes within the JPI or otherwise causing the addition to 

or modification of the classes in the JPI. In the event that you 

create an additional class and associated API(s) which (i) extends 

the functionality of the Java Platform, and (ii) is exposed to third 

party software developers for the purpose of developing additional 

software which invokes such additional API, you must promptly publish 

broadly an accurate specification for such API for free use by all 

developers. You may not create, or authorize your licensees to create 

additional classes, interfaces, or subpackages that are in any way 

identified as "java", "javax", "sun" or similar convention as specified 

by Sun in any naming convention designation.



If DataDirect Connect for JDBC is licensed for the Microsoft SQL Server 

database the following shall apply:  DataDirect Connect for JDBC 

contains a licensed implementation of the Microsoft TDS Protocol. You 

may only use DataDirect Connect for JDBC to communicate data to and 

from Microsoft SQL Servers.  You must separately obtain a license from 

Microsoft or its channel partners for any Microsoft software products 

used by you.



The DataDirect Connect for JDBC driver for MySQL Enterprise was 

developed using the MySQL Protocol Documentation whose copyright is 

owned by, and licensed by DataDirect from, MySQL AB. If DataDirect 

Connect for JDBC is licensed for the MySQL database the following shall 

apply: You must purchase commercially licensed MySQL database software 

or a MySQL Enterprise subscription in order to use the DataDirect Connect 

for JDBC driver for MySQL Enterprise with MySQL software.





---------------------

End of JDBCREADME.TXT



