Environment-Specific Information

The sections "For Windows Users" and "For UNIX and Linux Users" contain information specific to your operating environment.

The following sections refer to threading models. Refer to "Threading" in the DataDirect Connect64 for ODBC and Connect64 XE for ODBC Reference for an explanation of threading.

For Windows Users

Setup of the Drivers

The drivers must be configured before they can be used. See "Quick Start Connect" for information about using the Windows ODBC Administrator. See the individual driver chapters for details about driver configuration.

Driver Names

The prefix for all DataDirect Connect64 and Connect64 XE for ODBC driver file names is "DD." The file extension is .DLL, which indicates that they are dynamic link libraries. For example, the Sybase driver file name is DDASEnn.DLL, where nn is the revision number of the driver.

Refer to the readme file shipped with the product for the file name of each driver.

For UNIX and Linux Users

NOTE: The driver for the Teradata database is supported only in the HP-UX IPF environment.

AIX

HP-UX

Linux

Solaris

NOTE: Only the DB2 Wire Protocol, Oracle Wire Protocol, SQL Server Wire Protocol, and Sybase Wire Protocol drivers are available on Solaris x64.

AIX

If you are building 64-bit binaries, you must pass the define ODBC64. Demoodbc provides an example of this. See the installed file demoodbc.txt and "The demoodbc Application" for details.

You must also include the correct compiler switches if you are building 64-bit binaries. For example, to build demoodbc, you would use:

xlC_r -DODBC64 -q64 -qlonglong -qlongdouble -qvftable -o demoodbc  
  -I../include demoodbc.c -L../lib -lc_r -lC_r -lodbc 

HP-UX 11 aCC

If you are building 64-bit binaries, you must pass the define ODBC64. Demoodbc provides an example of this. See the installed file demoodbc.txt and "The demoodbc Application" for details. You must also include the +DD64 compiler switch if you are building 64-bit binaries. For example, to build demoodbc, you would use:

aCC -Wl,+s +DD64 -DODBC64 -o demoodbc -I../include demoodbc.c -L../lib -lodbc 

Linux

If you are building 64-bit binaries, you must pass the define ODBC64. Demoodbc provides an example of this. See the installed file demoodbc.txt and "The demoodbc Application" for details.

You must also include the correct compiler switches if you are building 64-bit binaries. For example, to build demoodbc, you would use:

g++ -o demoodbc -DODBC64 -I../include demoodbc.c -L../lib -lodbc -lodbcinst  
  -lc 

Solaris

If you are building 64-bit binaries, you must pass the define ODBC64. Demoodbc provides an example of this. See the installed file demoodbc.txt and "The demoodbc Application" for details.

You must also include the -xarch=v9 compiler switch if you are building 64-bit binaries. For example, to build demoodbc, you would use:

CC -mt -DODBC64 -xarch=v9 -o demoodbc -I../include demoodbc.c -L../lib -lodbc 
  -lCrun 

Setup of the Environment and the Drivers

On UNIX and Linux, several environment variables and the system information file must be configured before the drivers can be used. See "Quick Start Connect" for a brief description of these variables and information about using the DataDirect ODBC Data Source Administrator for UNIX/Linux. See the individual driver chapters for details about driver configuration. See "Configuring the Product on UNIX/Linux" for complete information about using the drivers on UNIX and Linux.

Driver Names

The DataDirect Connect and Connect XE for ODBC drivers are ODBC API-compliant dynamic link libraries, referred to in UNIX and Linux as shared objects. The prefix for all ODBC driver file names on UNIX and Linux is dd. The driver file names are lowercase and the extension is .so. This is the standard form for a shared object. For example, the Sybase driver file name is ddasenn.so, where nn is the revision number of the driver.

Refer to the readme file shipped with your DataDirect product for the file name of each driver.