     README
     DataDirect Technologies
     DataDirect Connect for ODBC
     DataDirect Connect XE (Extended Edition) for ODBC
     UNIX and Linux Platforms
     Release 5.3 Service Pack 1
     November 2007


***********************************************************************
Copyright (c) 2007 DataDirect Technologies Corp. All rights reserved. 
 
DataDirect Connect is a registered trademark of DataDirect Technologies 
Corp. 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 information not included in the DATADIRECT 
CONNECT AND CONNECT XE FOR ODBC USER'S GUIDE.


CONTENTS

Changes for Service Pack 1 since Release 5.3
Release 5.3 Features
Available ODBC Drivers
Disk Space Requirements
Required Operating System Patches
Configuring Data Sources
Driver WorkAround Options
Notes, Known Problems, and Restrictions
Using the Online Documents
Installed Files
Third-Party Vendor License Agreement


     Changes for Service Pack 1 since Release 5.3

See fixes.txt for a detailed list of issues addressed since 
Release 5.3.

New Driver
----------
* MySQL Wire Protocol driver for the MySQL 5.0.x database.


New Database Version Support
----------------------------
* DB2 V9.1 for z/OS.
* DB2 V9.1 for Linux/UNIX/Windows Fixpack 2.
* Informix 11
* Oracle 11g


New Operating System Support
----------------------------
* Red Hat Enterprise Linux 5.0
* HP-UX 11i v3 (PA-RISC and IPF)


DB2 Wire Protocol Driver Enhancements
-------------------------------------
* DB2 V9.1 for z/OS new data type support
* DB2 V9.1 for z/OS native SQL procedure support


Oracle Wire Protocol Driver Enhancements
----------------------------------------
* Oracle 11g server result set cache support
* Oracle 11g XQuery support


     Release 5.3 Features


New Database Version Support
----------------------------
* DB2 V9.1 for Linux, UNIX, Windows
* DB2 UDB V5R4 for iSeries
* Sybase 12.5.4
* Teradata V2R6.2
	

New Operating System Support
----------------------------
* SUSE Linux Enterprise Server 10.0


DB2 Wire Protocol Driver Enhancements
-------------------------------------
* Support for SSL data encryption on iSeries
* Support for XML data type and XQuery statements
* Support for DB2 data encryption on Linux, UNIX, Windows and z/OS


Oracle Wire Protocol Driver Enhancements
--------------------------------------------
* Support for SSL data encryption
* Kerberos authentication


Sybase Wire Protocol Driver Enhancements
----------------------------------------
* Support for SSL data encryption


New Features
------------
* Support for IPv6
* New ODBC Data Source Administrator for UNIX/Linux


Enhancement Requests
--------------------
5.3 enhancements include the following requests:

DEF0000251     DEF0002638
DEF0002486     DEF0002907
DEF0002425     DEF0003045
DEF0002790



     Available ODBC Drivers

Drivers for all UNIX and Linux platforms have the same file name. 
They all have the extension .so, except for HP-UX (PA-RISC), which 
has the extension .sl.

See the DATADIRECT CONNECT AND CONNECT XE FOR ODBC INSTALLATION GUIDE 
for a complete list of supported databases and client requirements.

DataDirect Connect for ODBC Drivers for 
AIX, HP-UX (PA-RISC), and Solaris SPARC
---------------------------------------
DB2 Wire Protocol (ivdb223.xx)

dBASE (ivdbf23.xx)

FoxPro 3.0 DBC (Built into the dBASE driver)

Informix Wire Protocol (ivifcl23.xx)

MySQL Wire Protocol (ivmysql23.xx) 

Oracle Wire Protocol (ivora23.xx)

SQL Server Wire Protocol (ivmsss23.xx) 

Sybase Wire Protocol (ivase23.xx)

Text (ivtxt23.xx)

Oracle   (ivor823.xx)


DataDirect Connect for ODBC Drivers for HP-UX (IPF)
---------------------------------------------------
Informix Wire Protocol (ivifcl23.xx)

MySQL Wire Protocol (ivmysql23.xx)

Oracle Wire Protocol (ivora23.xx)

SQL Server Wire Protocol (ivmsss23.xx)

Sybase Wire Protocol (ivase23.xx)

Oracle (ivor823.xx)


DataDirect Connect for ODBC Drivers for Linux
---------------------------------------------
DB2 Wire Protocol (ivdb223.xx)

dBASE (ivdbf23.xx)

FoxPro 3.0 DBC (Built into the dBASE driver)

Informix Wire Protocol (ivifcl23.xx)

MySQL Wire Protocol (ivmysql23.xx)

Oracle Wire Protocol (ivora23.xx)

SQL Server Wire Protocol (ivmsss23.xx) 

Sybase Wire Protocol (ivase23.xx)

Text (ivtxt23.xx)

Oracle   (ivor823.xx)


DataDirect Connect for ODBC Drivers for Solaris x86
---------------------------------------------------
DB2 Wire Protocol (ivdb223.xx)

MySQL Wire Protocol (ivmysql23.xx)

Oracle Wire Protocol (ivora23.xx)

SQL Server Wire Protocol (ivmsss23.xx)

Sybase Wire Protocol (ivase23.xx)


DataDirect Connect XE for ODBC Driver
-------------------------------------
Teradata (ivtera23.xx)


     Disk Space Requirements

The following disk space requirements assume a full installation of
all drivers and options.

DataDirect Connect for ODBC Drivers for 
AIX, HP-UX (PA-RISC), and Solaris SPARC
---------------------------------------
AIX      83 MB of available hard disk space.
HP-UX    82 MB of available hard disk space.
Solaris  77 MB of available hard disk space.

DataDirect Connect for ODBC Drivers for HP-UX (IPF)
---------------------------------------------------
81 MB of available hard disk space.

DataDirect Connect for ODBC Drivers for Linux
---------------------------------------------
72 MB of available hard disk space.

DataDirect Connect for ODBC Drivers for Solaris x86
---------------------------------------------------
59 MB of available hard disk space.

DataDirect Connect XE for ODBC Driver for 
AIX, HP-UX (PA-RISC), Linux, and Solaris SPARC
----------------------------------------------
AIX      29 MB of available hard disk space.
HP-UX    25 MB of available hard disk space.
Linux    29 MB of available hard disk space.
Solaris  26 MB of available hard disk space.


     Required Operating System Patches

For HP-UX 11 aCC Users Only
---------------------------
The ODBC drivers for HP-UX 11 aCC are supported on HP-UX 11.0
when running with HP-UX applications built using the HP aCC 
compiler version 3.05 or higher.

The ODBC drivers require certain runtime library patches. HP-UX 
patches are publicly available from the HP Web site (www.hp.com) 
or FTP site (ftp://i3107ffs.external.hp.com). The required patch is:

PHSS_14577

HP updates the patch database regularly; therefore, the patch 
numbers in this file may be superseded by newer versions. If you 
search for any of the specified patches on an HP site and receive 
a message that a patch has been superseded, download and install 
the replacement patch.

DataDirect provides a shared library creation script named 
genclntsh816, described in the Oracle chapter of the DATADIRECT CONNECT 
AND CONNECT XE FOR ODBC USER'S GUIDE. This script is relevant for HP-UX 
11 PA-RISC only, not for IPF.

For Oracle Users Only
---------------------
If you are using Oracle 8.1.7, you must have the 8.1.7.1 server 
patch installed. Otherwise, you may receive the Oracle error:
"ORA-03120: two-task conversion routine: integer overflow"
when fetching LOB data.


     Configuring Data Sources

Data sources are stored in the system information file (typically, 
odbc.ini). For details on configuring this file, see the DATADIRECT 
CONNECT AND CONNECT XE FOR ODBC USER'S GUIDE.


     Driver WorkAround Options

DataDirect has included non-standard options for the drivers that 
enable you to take full advantage of packaged ODBC-enabled 
applications requiring non-standard or extended behavior.

To use these options, we recommend that you create a separate data 
source for each application. Edit the odbc.ini file with a text editor 
to create data sources. In the section for the data source you created, 
add the string WorkArounds= (or WorkArounds2=) with a value of n 
(WorkArounds=n or WorkArounds2=n). The value n is the cumulative value 
of all options added together.

Note that each of these options has potential side effects related 
to its use. An option should only be used to address the specific 
problem for which it was designed. For example, WorkArounds=2 causes 
the driver to report that database qualifiers are not supported, 
even when they are. As a result, applications that use qualifiers 
may not perform correctly when this option is enabled.

WorkArounds=1. If an ODBC driver reports that its 
SQL_CURSOR_COMMIT_BEHAVIOR or SQL_CURSOR_ROLLBACK_BEHAVIOR is 0, 1 is 
returned instead and statements are prepared again by the driver.

WorkArounds=2. Some applications cannot handle database qualifiers. If 
this option is on, the driver reports that qualifiers are not 
supported.

WorkArounds=8. If an ODBC driver cannot determine the number of rows 
affected by an INSERT, UPDATE, or DELETE, it may return -1 in 
SQLRowCount. This may cause an error in some products. Turning this 
option on causes the driver to return 1 instead.

WorkArounds=16. For SQLStatistics, if an ODBC driver reports an 
INDEX_QUALIFIER that contains a period, some applications raise a 
"tablename is not a valid name" error. Turning this option on causes 
the driver to return no INDEX_QUALIFIER.

WorkArounds=32. Turning this option on forces the driver to re-bind
columns after calling SQLExecute for prepared statements.

WorkArounds=64. This option results in a column name of C<position> 
where <position> is the ordinal position in the result set. For 
example, "SELECT col1, col2+col3 FROM table1" produces the column names 
"col1" and C2. SQLColAttributes/SQL_COLUMN_NAME returns an empty string 
for result columns that are expressions. Use this option for 
applications that cannot handle empty string column names. 

WorkArounds=256. Forces SQLGetInfo/SQL_ACTIVE_CONNECTIONS to be 
returned as 1.

WorkArounds=512. To prevent ROWID results, this option forces the 
SQLSpecialColumns function to return a unique index as returned from 
SQLStatistics.

WorkArounds=2048. Microsoft Access performs more efficiently when the 
output connection string of SQLDriverConnect returns DATABASE= instead 
of DB= for some data sources. This option forces DATABASE= to be 
returned.

WorkArounds=65536. This option strips trailing zeros from decimal 
results, which prevents Microsoft Access from issuing an error when 
decimal columns containing trailing zeros are included in the unique 
index.

WorkArounds=131072. This option turns all occurrences of the double 
quote character ("") into the accent grave character (`). Some 
applications always quote identifiers with double quotes. Double 
quoting causes problems for data sources that do not return 
SQLGetInfo/SQL_IDENTIFIER_QUOTE_CHAR = <double quote>.

WorkArounds=524288. The Microsoft Foundation Classes (MFC) bind all 
SQL_DECIMAL parameters with a fixed precision and scale, which causes 
truncation errors. Set this option to force the maximum 
precision/scale settings.

WorkArounds=1048576. Some applications incorrectly specify a precision 
of 0 for character types when the value will be SQL_NULL_DATA. This 
option overrides the specified precision and sets the precision to 256.

WorkArounds=2097152. Some applications incorrectly specify a precision 
of -1 for character types. This option overrides the specified 
precision and sets the precision to 2000.

WorkArounds=4194304. For PowerBuilder users, this option converts all 
catalog function arguments to uppercase unless they are quoted.

WorkArounds=536870912. This option allows for re-binding parameters 
after calling SQLExecute for prepared statements.

WorkArounds=1073741824. If your application assumes that ORDER BY 
columns do not have to be in the SELECT list, this assumption may be 
incorrect for data sources such as Informix. This workaround addresses 
that assumption.

WorkArounds2=2. Some applications incorrectly specify the 
ColumnSize/DecimalDigits when binding timestamp parameters. This 
workaround causes the driver to ignore the ColumnSize/DecimalDigits 
specified by the application and use the database defaults instead.

WorkArounds2=4. Microsoft Access uses the last native type 
mapping, as returned by SQLGetTypeInfo, for a given SQL type. This 
workaround reverses the order in which types are returned so that 
Access will use the most appropriate native type.

WorkArounds2=8. This workaround causes the driver to add the bindoffset 
in the ARD to the pointers returned by SQLParamData. This is to 
work around a MSDASQL problem.

WorkArounds2=16. This workaround causes the drivers to ignore calls 
to SQLFreeStmt(RESET_PARAMS) and only return success without taking 
other action. It also causes parameter validation not to use the bind 
offset when validating the charoctetlength buffer. This is to work 
around a MSDASQL problem.

WorkArounds2=24. If you are using a DataDirect Connect for ODBC flat-
file driver, such as dBASE, under MSDASQL, you must use this workaround 
for the driver to operate properly.

WorkArounds2=32. Microsoft Access requires "DSN" to be included in a 
connection string. This workaround appends "DSN=" to a connection 
string if it is not already included.

WorkArounds2=128. Some applications will open extra connections if 
SQLGetInfo(SQL_ACTIVE_STATEMENTS) does not return 0. This workaround 
causes SQLGetInfo(SQL_ACTIVE_STATEMENTS) to return 0 to avoid the 
overhead of these extra connections.

WorkArounds2=256. Workaround for MSDASQL. Causes the drivers to return 
Buffer Size for Long Data on calls to SQLGetData with a buffer size of 
0 on columns whose SQL type is SQL_LONGVARCHAR or SQL_LONGVARBINARY. 
Applications should always set this workaround when using MSDASQL and 
retrieving long data.

WorkArounds2=512. Workaround for Microsoft Query 2000. Causes the 
flat-file drivers to return old literal prefixes and suffixes for 
date, time, and timestamp data types. Query 2000 does not correctly 
handle the ODBC escapes that are currently returned as literal prefix 
and literal suffix.

WorkArounds2=1024. Workaround for ADO. ADO incorrectly interprets the 
SQLGetInfo(SQL_MULT_RESULT_SETS) to mean that the last result set 
returned from a stored procedure is the output parameters for the 
stored procedure. Setting this workaround causes the driver to return 
"N" for this SQLGetInfo call.

WorkArounds2=2048. Workaround for the ODBC cursor library. ODBC 3.x 
applications that use the ODBC cursor library receive errors on 
bindings for SQL_DATE, SQL_TIME, and SQL_TIMESTAMP columns. The cursor 
library incorrectly rebinds these columns with the ODBC 2.x type 
defines. Setting this workaround causes the drivers to accept these 
2.x SQL types as valid.

WorkArounds2=4096. The ODBC Driver Manager incorrectly translates 
lengths of empty strings when a Unicode-enabled application uses a 
non-Unicode driver. This workaround causes the DataDirect Connect64 for 
ODBC drivers to internally adjust the length of empty strings. Use this 
workaround only if your application is Unicode enabled.


     Notes, Known Problems, and Restrictions

The following are notes, known problems, or restrictions with Release 
5.3 Service Pack 1 of DataDirect Connect and Connect XE for ODBC for 
UNIX and Linux.

Library Search Path on UNIX/Linux
---------------------------------
The Library Search Path section of the UNIX/Linux chapter in the 
DATADIRECT CONNECT AND CONNECT XE FOR ODBC USER'S GUIDE instructs you 
to determine which shell you are using by executing the "echo $SHELL" 
command. This command returns the value of your login shell. For 
example, if your login shell is the Korn shell (ksh) and you later 
execute a Bourne shell (sh), the echo $SHELL command still returns a 
ksh value. To avoid errors in determining which shell script to run for 
setting the library search path, run the echo $SHELL command from your 
login shell.

New ODBC Administrator for UNIX/Linux
-------------------------------------
The new DataDirect ODBC Data Source Administrator for UNIX/Linux (the 
UNIX ODBC Administrator) allows you to configure data sources through 
the Motif Graphical User Interface. The use of the Administrator is 
fully described in the DATADIRECT CONNECT AND CONNECT XE FOR ODBC 
USER'S GUIDE. The Administrator only works with 5.3 drivers; it does 
not work with prior versions. Currently, the Administrator is only 
available for Linux platforms.

The Driver Configuration Help System and Firefox
------------------------------------------------
The UNIX ODBC Administrator displays driver Setup dialogs for 
configuring data sources. Currently, accessing the help system through 
the help buttons on the driver Setup dialogs is not supported with the 
Firefox browser.

For Linux Users of OpenMotif Versions Prior to 2.3
--------------------------------------------------
When running the UNIX ODBC Administrator on Linux with versions of 
OpenMotif prior to 2.3 using multi-byte locale settings, such as UTF-8, 
warning messages may appear because of a problem in OpenMotif. These 
messages will say that certain characters are not supported in the 
current font. You may also experience problems with being unable to 
type values into some fields on tabs of the ODBC administrator. If you 
experience such problems, we recommend that you set your locale to a 
single-byte codepage, such as en_US, to work around the problem. You 
can also upgrade your system to OpenMotif 2.3 or higher, where this 
issue has been resolved.

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 visit the Web site:

http://www.openssl.org/support/faq.html#USER1

On SUSE Linux Enterprise Server 10.0, attempts by the drivers to connect 
using SSL Encryption will not succeed due to a problem loading the SSL 
libraries.

SSL and the UNIX ODBC Administrator
-----------------------------------
The UNIX ODBC Administrator does not correctly save the encrypted 
truststore password, keystore password, and key password in the 
odbc.ini file when specifying them on the Security tab of the driver 
Setup dialog boxes for the DB2 Wire Protocol, Oracle Wire Protocol, and 
Sybase Wire Protocol drivers. To set these connection options, you must 
edit the odbc.ini file directly and use the appropriate connection 
string attributes to store these passwords in the file. You cannot use 
the driver Setup dialog boxes. See the DATADIRECT CONNECT AND CONNECT 
XE FOR ODBC USER'S GUIDE for details about the Security tabs and the 
odbc.ini file.

For Red Hat Linux 4.0 Users With x64 Processors
-----------------------------------------------
The default C++ runtime libraries included in Red Hat Enterprise Linux 
4.0 for x64 systems are incompatible with the DataDirect Connect for 
ODBC drivers. When trying to load the drivers with ivtestlib or connect 
with them, if you see messages such as:

"Error while loading shared libraries: libstdc++.so.5: cannot open 
shared object file: No such file or directory."

then you need an older version of the runtime libraries. Prior versions 
of these libraries can be downloaded from various Web sites, for 
example:

http://rpm.pbone.net/index.php3/stat/4/idpl/1824545/com/compat-
libstdc++-33-3.2.3-47.3.x86_64.rpm.html

ODBC Development on UNIX and Linux Platforms
--------------------------------------------
All of the Release 5.3 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 license.txt file in the /include directory for 
pertinent licensing information regarding the ODBC Core Components. 
Contact your local DataDirect Sales or SupportLink representative if 
you have any questions.

Developers using programming languages other than C++:
The ODBC 3.x 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 by non-C++ compiled 
applications. If you are not using C++, consult your compiler 
documentation for instructions on using C++ shared libraries with your 
application. Some known issues are listed below.

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.

ODBC Driver Manager
-------------------
Release 5.3 drivers require the 5.3 version of the ODBC Driver Manager.

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.

SQLDriverConnect
----------------
SQLDriverConnect using options other than SQL_DRIVER_NOPROMPT is 
supported only on systems that include the Motif libraries 
libivmback.xx and vscnctdlg.xx.

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

For AIX Users
-------------
Some IBM AIX C compilers, for example, xlc 3.1.4 do not support the use 
of C++ build binaries. C developers on AIX should consult their 
compiler documentation and verify that their AIX C compiler supports 
the use of C++ shared libraries or the application could be unstable.

Unexpected behavior may occur randomly if the LIBPATH variable 
exceeds 178 characters AND the ORACLE_HOME variable is relatively 
long. To resolve this, create a shorter symbolic link for 
ORACLE_HOME.

For dBASE Users
---------------
On UNIX and Linux platforms, dBASE table names (filenames) are 
case-sensitive and the case is retained in SQL commands. Column 
names are case-sensitive also, but are upper-case in SQL commands 
unless they are quoted with the identifier quote character.

For Informix Users
------------------
Restriction:  Some Informix error messages may contain more than one 
error. All errors displayed may not be valid.

For Oracle Users
----------------
If you are using Oracle 8.1.7, you must have the 8.1.7.1 server patch
installed. Otherwise, you may receive the Oracle error:"ORA-03120: 
two-task conversion routine: integer overflow" when fetching LOB data.

SQLProcedures and SQLProcedureColumns now include functions/procedures 
from Oracle packages. They are denoted in the result set as 
PackageName.ProcedureName for the PROCEDURE_NAME.

To use static scrollable cursors with result sets containing long 
columns, you must set EnableStaticCursorsForLongData (ESCLD) to 1 
(EnableStaticCursorsForLongData=1) in the data source entry of the 
Registry or in a connection string. The default setting is 0.

You must have a complete installation of the Oracle 8 client software 
for the Oracle (client) driver to operate properly when accessing 
remote Oracle 8 servers 8.0.5 or higher. Be sure that you have 
installed one of the following products:

Oracle 8.1.6:
     Oracle8i Client 8.1.6--Installation Type:  Programmer

Oracle 8.1.7:
     Oracle8i Client 8.1.7--Installation Type:  Programmer

NOTES: 
* On Linux, you must use the Oracle Net8 Client version 8.1.6.1.

For Microsoft SQL Server Users
------------------------------
The SQL Server Wire Protocol driver for UNIX and Linux supports 
SQL Server 7.0 and 2000.

Attempting to execute DDL statements that contain errors causes 
an implicit rollback of the current transaction if executing in 
manual commit mode. No warning occurs when this happens. This is a 
Microsoft SQL Server limitation, and there is no driver workaround.

NOTE:  When executing multiple statements in a stored procedure, the 
function SQLMoreResults ignores all statements other than Select 
statements. Because the SQL Server Wire Protocol and Sybase Wire 
Protocol drivers do not have a way to prepare statements, the driver 
does not send those statements to the server until SQLExecute is 
called. PREPARE does not return any of the normal errors that most 
of the drivers return. If, however, the user requests information 
about result columns, the driver will execute a Select statement and 
return warnings or errors at SQLNumResultCols, SQLDescribeCol, or 
SQLColAttributes time.

If you have problems with the catalog functions returning incorrect 
data, you may need to upgrade your catalog stored procedures. Make 
sure that you have installed the latest version of the stored  
procedures, which are available from your database vendor. Refer to 
your SQL Server documentation for more information.

The SQL Server Wire Protocol driver does not support multiple active 
statements on a single connection by default. See the Microsoft 
Knowledgebase document explaining how to enable multiple active 
statements on a single connection with SQL Server using server-side 
cursors at the following URL:

http://support.microsoft.com/support/kb/articles/q140/8/96.asp

The SQL Server Wire Protocol driver returns stored procedure names with 
the version number appended to them. For example, a procedure defined 
as "proc1" will be returned as "proc1;1".

For Sybase Users
----------------
You may experience a problem using catalog stored procedures when 
running the driver with Sybase Adaptive Server 11.5. Contact Sybase 
and ask for the latest version of their catalog stored procedures.

For Teradata Users
------------------
When compiling an application on AIX for use with the driver for the 
Teradata database, you must use the -brtl option. For example:

cc -o pgm pgm.o  brtl -lodbc

or

ld -o  pgm brtl  pgm.o -lodbc

For Text Users
--------------
Restriction:  When encountering an invalid file, you may receive 
duplicate or multiple errors from SQLError.


Using the Online Documents

The DataDirect Connect for ODBC 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/odbcproddoc/index.ssp

You can view the PDF versions using Adobe Reader.

NOTE: To download Adobe Reader, visit the Adobe Web site at 
http://www.adobe.com.

The HTML versions of the books are installed in the help subdirectory 
of your product installation directory.


     Installed Files 

The file list below depends on driver availability for each 
platform. See the previous section "Available ODBC Drivers" to 
determine which drivers are installed. This file list assumes a full 
installation of all drivers and documentation.

Setup copies the following files and subdirectories to the product 
installation directory, by default, /opt/odbc32v53:

ddextu
iculicense.txt        License agreement for ICU
IVODBC.LIC            DataDirect license file
mysqllicense.txt      License agreement for MySQL
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
ODBCREADME.TXT        This file
ODBCFIXES.TXT         List of fixes since last release

/adminhelp: [Linux only]

help.htm              Administrator HTML help system entry file 
/*.*                  Support folders for the HTML help system 

/bin:

ivtestlib             Test program to check that required libraries
                      are present and loadable
bind23                DB2 bind utility

/bind:

DDODBC_LUW.lst        DB2 list files for Linux/UNIX/Windows
DDODBC_400.lst        DB2 list files for iSeries
DDODBC_MVS.lst        DB2 list files for z/OS
DDOC510A.bnd
DDOS510A.bnd
DDOR510A.bnd
DDOU510A.bnd
DDON510A.bnd
DDOC510B.bnd
DDOS510B.bnd
DDOR510B.bnd
DDOU510B.bnd
DDON510B.bnd
DDOC510C.bnd
DDOS510C.bnd
DDOR510C.bnd
DDOU510C.bnd
DDON510C.bnd


/demo:

demoodbc              Standard demo executable
demoodbc.c            Source file for the standard demo program
demoodbc.txt          Short description of samples and the SQL files
driver_connect        Demo executable that uses Motif SQLDriverConnect
driver_connect.cc     Source file for the Motif demo program
driver_connect.txt    Short description of driver_connect
EMP.DBF               Sample dBASE file
EMP.DBT
empdb2.sql            File of SQL statements to use with DB2 to
                      populate the EMP table used by the demo
                      programs
empinformix.sql       File of SQL statements to use with Informix
                      to populate the EMP table used by the demo
                      programs
emporacle.sql         File of SQL statements to use with Oracle
                      to populate the EMP table used by the demo
                      programs
empsqlsrv.sql         File of SQL statements to use with SQL Server
                      to populate the EMP table used by the demo
                      programs
empsybase.sql         File of SQL statements to use with Sybase
                      to populate the EMP table used by the demo
                      programs
emptext.txt           Sample text table
Makefile              Make script for building the demo programs
QEDBF.INI             Schema information for the sample dBASE file
QETXT.INI             Schema information for the sample text file

/example:

example               Example executable
example.c             Source file for example program
example.h             Header file for example program
example.mak           Make file for example program
example.txt           Short description of the program

/help:

help.htm              HTML help system entry file [Linux only]
/*.*                  Support folders for the HTML help system 
drda_connect.txt      Help text for the DB2 Wire Protocol 
                      SQLDriverConnect dialog 
ifcl_connect.txt      Help text for the Informix Wire Protocol 
                      SQLDriverConnect dialog
informix_connect.txt  Help text for the Informix SQLDriverConnect
                      dialog
mysql_connect.txt     Help text for the MySQL Wire Protocol 
                      SQLDriverConnect dialog
oracle_connect.txt    Help text for the Oracle SQLDriverConnect dialog 
oraclewp_connect.txt  Help text for the Oracle Wire Protocol
                      SQLDriverConnect dialog
sqlsrv_connect.txt    Help text for the SQL Server Wire Protocol 
                      SQLDriverConnect dialog
teradata_connect.txt  Help text for the Teradata SQLDriverConnect 
                      dialog
tds_connect.txt       Help text for the Sybase Wire Protocol 
                      SQLDriverConnect dialog

/include:

license.txt           License agreement for non-Windows ODBC SDK
odbcinst.h            Include files
qesqlext.h
sql.h
sqlext.h
sqltypes.h
sqlucode.h
sqlunx.h

/lib:

The following /lib files have the same file name across platforms. They 
all have the extension .so, except for the HP-UX (PA-RISC) files, which 
have the extension .sl. Resource libraries for a driver end in r.xx; 
setup libraries for a driver end in s.xx. The resource and setup 
libraries are for use by the UNIX ODBC Administrator and are currently 
available ONLY on Linux platforms.

On HP-UX (IPF), only the following driver files are available: Informix 
Wire Protocol, MySQL Wire Protocol, Oracle Wire Protocol, SQL Server Wire 
Protocol, Sybase Wire Protocol, and Oracle.

On Solaris x86, only the following driver files are available: DB2 Wire 
Protocol, MySQL Wire Protocol, Oracle Wire Protocol, SQL Server Wire 
Protocol, and Sybase Wire Protocol.

On Linux, all the following driver files are available except the 
Informix driver.

ivase23.xx            Sybase Wire Protocol driver
ivase23r.xx
ivdb223.xx            DB2 Wire Protocol driver
ivdb223r.xx
ivdbf23.xx            dBASE driver
ivdbf23r.xx
ivifcl23.xx           Informix Wire Protocol driver
ivifcl23r.xx
ivinf23.xx            Informix driver
ivmsss23.xx           SQL Server Wire Protocol driver
ivmsss23r.xx
ivmsss23s.xx
ivmsssdlg23.xx        SQLDriverConnect Motif library for the SQL Server 
                      Wire Protocol driver only
ivmysql23.xx          MySQL Wire Protocol driver
ivor823.xx            Oracle driver
ivor823r.xx
ivor823s.xx
ivora23.xx            Oracle Wire Protocol driver
ivora23r.xx
ivssl23.so            SSL support file [AIX only]
ivtera23.xx           Teradata driver [Connect XE for ODBC only]
ivtera23r.xx
ivtera23s.xx
ivtrn23.xx            DataDirect sample translation shared object
ivtxt23.xx            Text driver
ivtxt23r.xx
libivcrypto23.xx      SSL support file [.a on AIX]
libivicu23.xx         Unicode conversion tables  [.a on AIX]
libivmback.xx         SQLDriverConnect Motif library for all drivers 
                      except Oracle Wire Protocol, Oracle, and 
                      SQL Server Wire Protocol [.a on AIX]
libivmbackw.xx        SQLDriverConnect Motif library for the Oracle 
                      drivers only [.a on AIX]
libivssl23.so         SSL support file [.a on AIX]
libodbc.xx            ODBC Driver Manager [.a on AIX]
libodbcinst.xx        ODBC Installer [.a on AIX]
odbc.so               ODBC Driver Manager (dynamically loadable) 
                      [AIX only]
odbccurs.xx           ODBC Cursor library 
odbcinst.so           ODBC Installer (dynamically loadable) 
                      [AIX only]
odbctrac.xx           ODBC Tracing library
vscnctdlg.xx          ODBC library for Motif operations

/locale/en_US/LC_MESSAGES:

The following /locale/en_US/LC_MESSAGES files have the same file name 
across platforms. They all have the extension .so, except for the HP-UX 
(PA-RISC) files, which have the extension .sl.

On HP-UX (IPF), only the following message files are available: 
Informix Wire Protocol, Oracle Wire Protocol, SQL Server Wire Protocol, 
Sybase Wire Protocol, and Oracle.

On Linux, all the following message files are available except the 
Informix driver.

On Solaris x86, only the following message files are available: DB2 
Wire Protocol, Oracle Wire Protocol, SQL Server Wire Protocol, and 
Sybase Wire Protocol.

ivase23.mo            Sybase Wire Protocol driver message file
ivase23.po            Sybase Wire Protocol driver message source
ivdb223.mo            DB2 Wire Protocol driver message file
ivdb223.po            DB2 Wire Protocol driver message source
ivdbf23.mo            dBASE driver message file
ivdbf23.po            dBASE driver message source
ivifcl23.mo           Informix Wire Protocol driver message file
ivifcl23.po           Informix Wire Protocol driver message source
ivinf23.mo            Informix client driver message file
ivinf23.po            Informix client driver message source
ivmback.mo            Motif library message file
ivmback.po            Motif library message source
ivmbackw.mo           Motif library message file
ivmbackw.po           Motif library message source
ivmsss23.mo           SQL Server Wire Protocol driver message file
ivmsss23.po           SQL Server Wire Protocol driver message source
ivmysql23.mo          MySQL Wire Protocol driver message file
ivmysql23.po          MySQL Wire Protocol driver message source
ivor823.mo            Oracle driver message file
ivor823.po            Oracle driver message source
ivora23.mo            Oracle Wire Protocol driver message file
ivora23.po            Oracle Wire Protocol driver message source
ivtera23.mo           Teradata driver message file [Connect XE for ODBC 
                      only]
ivtera23.po           Teradata driver message source [Connect XE for 
                      ODBC only]
ivtxt23.mo            Text driver message file
ivtxt23.po            Text driver message source
odbc.m                ODBC Driver Manager message file
odbc.po               ODBC Driver Manager message source 

/src/oracle:

genclntsh816          Oracle 8.1.6 shared library creation script 
                      [HP-UX 11 PA-RISC only]

/src/trn:

ivtrn23.exp           Translation shared library export file 
                      [AIX only]
Makefile              Make script for building translation library
readme.trn            Short description of translation library
translat.c            Sample translation shared library

/tools:

ddprocinfo            Processor Information utility
odbcadmin             ODBC Data Source Administrator [Linux only]

/wizards:

index.html
odbcperf.jar
/logo/*.*


     Third-Party Vendor License Agreement 

This DataDirect product includes ICU Version 3.2 which is subject to 
the following license agreement:

ICU License - ICU 1.8.1 and later ICU License - ICU 1.8.1 and later
COPYRIGHT AND PERMISSION NOTICE

Copyright (c) 1995-2003 International Business Machines Corporation and 
others
All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, and/or sell copies of the Software, and to permit persons
to whom the Software is furnished to do so, provided that the above
copyright notice(s) and this permission notice appear in all copies of
the Software and that both the above copyright notice(s) and this
permission notice appear in supporting documentation.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL
INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING
FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Except as contained in this notice, the name of a copyright holder
shall not be used in advertising or otherwise to promote the sale, use
or other dealings in this Software without prior written authorization
of the copyright holder.
-----------------------------------------------------------------------

This DataDirect product includes the OpenSSL Library which is subject 
to the following license agreements:

OpenSSL License

Copyright (c) 1998-2006 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without 
modification, are permitted provided that the following conditions are 
met:

1. Redistributions of source code must retain the above copyright 
notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright 
notice, this list of conditions and the following disclaimer in the 
documentation and/or other materials provided with the distribution.
 
3. All advertising materials mentioning features or use of this 
software must display the following acknowledgment:

"This product includes software developed by the OpenSSL Project for 
use in the OpenSSL Toolkit. (http://www.openssl.org/)"

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used 
to endorse or promote products derived from this software without prior 
written permission. For written permission, please contact openssl-
core@openssl.org.
 
 5. Products derived from this software may not be called "OpenSSL" nor 
may "OpenSSL" appear in their names without prior written permission of 
the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following 
acknowledgment:

"This product includes software developed by the OpenSSL Project for 
use in the OpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY 
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS 
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, 
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, 
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF 
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS 
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------------------------------------------- 

This DataDirect product includes cryptographic software written by Eric 
Young (eay@cryptsoft.com). This product includes software written by 
Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License
-----------------------
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights 
reserved.
 
This package is an SSL implementation written by Eric Young 
eay@cryptsoft.com). The implementation was written so as to conform 
with Netscapes SSL.

This library is free for commercial and non-commercial use as long as 
the following conditions are aheared to. The following conditions apply 
to all code found in this distribution, be it the RC4, RSA, lhash, DES, 
etc., code; not just the SSL code. The SSL documentation included with 
this distribution is covered by the same copyright terms except that 
the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in 
the code are not to be removed. If this package is used in a product, 
Eric Young should be given attribution as the author of the parts of 
the library used. This can be in the form of a textual message at 
program startup or in documentation (online or textual) provided with 
the package.

Redistribution and use in source and binary forms, with or without 
modification, are permitted provided that the following conditions are 
met:

1. Redistributions of source code must retain the copyright notice, 
this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright 
notice, this list of conditions and the following disclaimer in the 
documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this 
software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young 
(eay@cryptsoft.com)"

The word 'cryptographic' can be left out if the routines from the 
library being used are not cryptographic related :-).

4. If you include any Windows specific code (or a derivative thereof) 
from the apps directory (application code) you must include an 
acknowledgement:

"This product includes software written by Tim Hudson 
(tjh@cryptsoft.com)"

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR 
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 
DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR 
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 
POSSIBILITY OF SUCH DAMAGE.

The licence and distribution terms for any publically available version 
or derivative of this code cannot be changed. i.e. this code cannot 
simply be copied and put under another distribution licence [including 
the GNU Public Licence.]
-----------------------------------------------------------------------

If DataDirect Connect for ODBC is licensed for the Microsoft SQL Server 
database the following shall apply:  DataDirect Connect for ODBC 
contains a licensed implementation of the Microsoft TDS Protocol. You 
may only use DataDirect Connect for ODBC 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 ODBC 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 ODBC 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 ODBC driver for MySQL Enterprise with MySQL software.
-----------------------------------------------------------------------

All trademarks and registered trademarks mentioned herein are the 
property of their respective owners.


~~~~~~~~~~~~~~
End of README
