Linux ODBC/MX Client Driver for SQL/MX Release 3.2 (H06.25+, J06.14+)

4 Driver compatibility and considerations
The driver is compatible with the following:
• ODBC 3.5
• SQL-92 features supported by SQL/MX
For more information about SQL/MX supported scalar and string functions, see the SQL/MX
Reference Manual for Release 3.x .
These subsequent sections list the driver compatibility for the following:
• “Driver considerations” (page 22)
• “ODBC data types” (page 23)
• “Unsigned data types” (page 24)
• “Partial DATE or TIME values” (page 25)
• “Microsoft escape clauses” (page 26)
• “Stored Procedures” (page 26)
• “Transaction and cursor behavior” (page 26)
• “Timestamp values with fraction” (page 27)
Driver considerations
Table 3 (page 22) lists the driver considerations.
Table 3 Driver considerations
ConsiderationItem
A Linux ODBC client application must be installed on the Linux workstation.Linux ODBC/MX client application
An application can set the catalog and schema information in the MXODSN
file. If the application does not set the catalog and schema for the client data
Catalog and schema
source, then MXCS, by default, uses NONSTOP_SYSTEM_NSK and
PUBLIC_ACCESS_SCHEMA.
NOTE: Catalog and schema names follow SQL/MX rules and are case
sensitive.
An application can call SQLSetStmtOption ODBC API with the
SQL_QUERY_TIMEOUT option to specify the wait time for query execution.
SQL_QUERY_TIMEOUT option
The SQL_QUERY_TIMEOUT option protects MXCS and the application from
long running queries. If a query exceeds the specified time before the data
source returns the result, the driver returns HYT00 (Timeout expired) to the
application.
For an ODBC 2.0 application, when the query is not running, the driver
implements the SQLCancel API as an SQLFreeStmt with the SQL_CLOSE
SQLCancel API
option. If the query is running, MXCS tries to stop the ODBC server. If the
attempt is successful, the application receives an error and must reconnect.
For an ODBC 3.x application with a query (or queries) running, the behavior
is the same as for a ODBC 2.0 application. For an ODBC 3.x application
with no queries running, the driver does not implement the SQLCancel API.
The application is responsible for closing the cursor.
This API does not support pattern value arguments for table names, and
returns keys information for a specified table name in the SQL/MX catalog.
SQLPrimaryKeys API
This API does not support pattern value arguments for table names, and
returns an optimal set of columns that the SQLSpecialColumns API uniquely
SQLSpecialColumns API
22 Driver compatibility and considerations