Implementation issues of ODBC APIs
Learn about implementations issues when using IBM® i Access ODBC APIs.
Choose from the following topics for information regarding implementation of ODBC APIs.
Note: For a description and work-around for several
problems that can occur when using the IBM i Access ODBC driver
with Microsoft's ADO interface, search the Software Knowledge Base,
using ADO Stored Procedure Calls with MSDASQL as
a search string.
Note: By using the code examples, you agree to the terms of the Code license and disclaimer information.
- ODBC 3.x API notes
The following table lists IBM i Access ODBC 3.x APIs by their associated task and identifies considerations for each API. - Connection string keywords
The IBM i Access support for the ODBC driver has many connection string keywords that are used to change the behavior of the ODBC connection. - Version and release changes in the ODBC driver behavior
This topic describes new features supported by different versions of the ODBC driver and corresponding IBM i release. - ODBC API restrictions and unsupported functions
The way in which some functions are implemented in the IBM i Access ODBC Driver does not meet the specifications in the Microsoft ODBC Software Development Kit Programmer's Reference. - Signon dialog behavior
You have control over your IBM i Access for Windows signon dialog, userid, and password prompting. - ODBC data types and how they correspond to DB2 for i database types
The IBM i Access support for the ODBC driver maps data types between ODBC types and DB2® for i data types. - Working with the XML data type
These conventions can help you handle various aspects of using the XML data type in DB2 for iODBC functions. - Large objects (LOBs) considerations
Use LOBs with IBM i Access ODBC to store and access large text documents. - Connection and statement attributes
The IBM i Access ODBC specification defines several connection and statement attributes. - Connection pooling
Connection pooling is supported on an IBM i Access ODBC connections. - SQLPrepare and SQLNativeSQL escape sequences and scalar functions
The IBM i Access ODBC support includes escape sequences and scalar functions. - Distributed transaction support
Distributed transactions allow an IBM i Access ODBC application to coordinate units of work across multiple databases. - Cursor behavior notes
Cursor behaviors can affect how data is fetched when working with the IBM i Access ODBC driver. - Extended dynamic disabled error
The IBM i Access ODBC driver displays the Extended dynamic support disabled message when a SQL package is unusable. To correct the problem : - ODBC 64-bit Windows and Linux Considerations
Identify header files and data types when using the ODBC driver in an IBM i Access for Windows or IBM i Access for Linux environment. - Restrictions of the 64–bit IBM i Access for Windows ODBC Driver
MTS is not supported on the 64-bit IBM i Access for Windows ODBC driver. - SQLTables Description
There are multiple considerations when using IBM i Access ODBC driver SQLTables API. - Handle long-running queries
There are a number of ways to limit the amount of time a query runs with the IBM i Access ODBC driver. Listed below are a couple of options which can be enabled in ODBC. - Isolation level considerations
Run IBM i Access ODBC autocommit support to different isolation (commit) levels.
Parent topic: IBM i Access ODBC
Related reference:
Related information:
