Implementation issues of ODBC APIs

Learn about implementations issues when using ODBC APIs.

Choose from the following topics for information regarding implementation of ODBC APIs.

• ODBC 3.x APIs Notes
  The following table lists ODBC 3.x APIs by their associated task and identifies considerations for each API.
• Connection string keywords
  The iSeries Access ODBC driver has many connection string keywords that can be used to change the behavior of the ODBC connection.
• Version and release changes in the ODBC driver behavior
  This topic describes version and release changes in the ODBC driver behavior.
• ODBC API restrictions and unsupported functions
  The way in which some functions are implemented in the iSeries Access for Windows^® ODBC Driver does not meet the specifications in the Microsoft^® ODBC Software Development Kit Programmer's Reference.
• Signon dialog behavior
  The signon dialog behavior has been simplified from the behavior seen in previous iSeries Access for Windows^® ODBC drivers. The signon dialog behavior is based on how your data source is set up and which ODBC API (SQLConnect, SQLDriverConnect, SQLBrowseConnect) your application uses to connect.
• ODBC data types and how they correspond to DB2 UDB database types
  The ODBC driver maps data types between ODBC types and DB2^® UDB types. The following table shows this mapping.
• Large objects (LOBs) considerations
  Use LOBs with iSeries Access for Windows^® ODBC to store and access large text documents.
• Connection and statement attributes
  The ODBC specification defines several connection and statement attributes.
• Connection pooling
  Connection pooling refers to the behavior where ODBC connections are left open after the application has requested to disconnect them. Connections that are in the pool can be reused by the same application avoiding the time consuming operation of creating a brand new connection.
• SQLPrepare and SQLNativeSQL escape sequences and scalar functions
  ODBC has escape sequences and scalar functions that can be used to avoiding having to code directly to the syntax of a particular DBMS's version of SQL.
• Distributed transaction support
  Distributed transactions allow an application to coordinate units of work across multiple databases.
• Cursor Behavior Notes
  Cursor behaviors can affect how data is fetched when working with the iSeries Access ODBC driver.
• Extended dynamic disabled error
  The Extended dynamic support disabled message is seen when a SQL package is unusable for some reason.
• Restrictions of the 64–bit iSeries Access for Windows ODBC Driver
  MTS is not supported on the 64-bit iSeries Access for Windows^® ODBC driver.
• SQLTables Description
  The following is a discussion about SQLTables description.
• Handle long-running queries
  There are at least two ways you can handle long running queries through ODBC.
• Commitment control considerations
  Run ODBC autocommit support to different commit levels.