HP Integrity NonStop H-Series - Manual (Page 37)

4 Compatibility and considerations
The drivers are 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 compatibility of the drivers for the following:
•
“Considerations” (page 37)
•
“ODBC data types” (page 38)
•
“Unsigned data types” (page 39)
•
“Partial DATE or TIME values” (page 40)
•
“Microsoft escape clauses” (page 41)
•
“Stored Procedures” (page 41)
•
“Transaction and cursor behavior” (page 41)
•
“Timestamp values with fraction” (page 42)
Considerations
Table 5 lists the considerations.
Table 5 Considerations
Consideration Item
An ODBC client application must be installed on the client workstation. ODBC/MX client application
An application can set the catalog and schema information in the MXODSN
file on Linux or ODBCDSN file on OSS. If the application does not set the Catalog and schema
catalog and schema for the client data source, and no default catalog and
schema are defined in MXCS for the server data source, then MXCS, by
default, uses NONSTOP_SYSTEM_NSK and PUBLIC_ACCESS_SCHEMA.
NOTE: By default, catalog and schema names are case insensitive and
follow SQL/MX rules. Case sensitive catalog and schema names can be
specified within quotes.
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
Considerations 37