SQL/MX Connectivity Service Manual for SQL/MX Release 3.2 (H06.25+, J06.14+)

You must modify:
• SQL statements (to comply with SQL/MX syntax)
• NonStop ODBC Server-specific syntax commands
ODBC API calls
ODBC 2.x compliant applications do not need to be migrated to support the new 3.x functions.
The Microsoft ODBC driver manager allows version 2.x applications to run using version 3.x
-compliant drivers and vice versa. It automatically maps version 2.x application functions to version
3.x-compliant drivers, version 3.x application functions to version 2.x-compliant drivers, and it
performs mapping between 2.x and 3.x functions and parameter options.
ODBC/MX includes a 3.5-compliant ANSI driver; it does not include a Unicode API. However,
the driver manager automatically provides the mapping between the Unicode API and the ANSI
API.
Table 9 (page 63) shows how ODBC 2.x calls map to ODBC 3.x, and whether NonStop ODBC
and ODBC/MX support each call.
Table 9 ODBC API Mapping Between 2.x and 3.x Versions
2. x Calls Supported by
ODBC Server?
3. x Calls Supported by
ODBC/MX?ODBC 3.x Calls*ODBC 2.x Calls*
YYSQLAllocHandleSQLAllocConnect
YYSQLAllocHandleSQLAllocEnv
YYSQLAllocHandleSQLAllocStmt
YYSQLBindColSQLBindCol
YYSQLBindParameterSQLBindParameter
YYSQLBrowseConnectSQLBrowseConnect
NNSQLBulkOperationsNo equivalent
YYSQLCancelSQLCancel
YYSQLColAttributeSQLColAttributes
NYSQLCloseCursorNo equivalent
NYSQLColumnPrivilegesSQLColumnPrivileges
YYSQLColumnsSQLColumns
YYSQLConnectSQLConnect
NYSQLCopyDescNo equivalent
YYSQLDataSourcesSQLDataSources
YYSQLDescribeColSQLDescribeCol
NYSQLDescribeParamSQLDescribeParam
YYSQLDisconnectSQLDisconnect
YYSQLDriverConnectSQLDriverConnect
NYSQLDriversNo equivalent
YYSQLGetDiagFieldSQLError
NYSQLGetDiagRecNo equivalent
YYSQLExecDirectSQLExecDirect
YYSQLExecuteSQLExecute
Client: Modifying Applications 63