MX 3.x)

ODBC/MX Client Overview

HP NonStop Open System Services ODBC/MX Client Driver—640328-001

1-7

Release Considerations and Restrictions

registered in different NonStop SQL user catalogs, using the same SQL/MX catalog

and schema names.

Release Considerations and Restrictions

Table 1-1. Release Considerations and Restrictions (page 1 of 2)

ODBC/MX client software An ODBC/MX client must be installed on a NonStop system.

Catalog and schema An ODBC client application can set the catalog and schema

information in the ODBCDSN file. For more information on the

ODBCDSN file, see ODBCDSN File Format

on page 2-3.

If an ODBC client does not set the catalog and schema for an

ODBC client data source, the MXCS server defaults to

NONSTOP_SYSTEM_NSK and

PUBLIC_ACCESS_SCHEMA, respectively.

Note:

•

catalog and schema names follow SQL/MX rules, and are

case sensitive

•

catalog and schema names that are defined by default

are not recognized by MXCS for client data sources

because they are not defined in the ODBCDSN file. You

must use the fully qualified object name.

SQL_QUERY_TIMEOUT

Option

An ODBC application can call SQLSetStmtOption with the

SQL_QUERY_TIMEOUT option to specify the number of

seconds to wait for a query to execute. The

SQL_QUERY_TIMEOUT option protects the MXCS server

and ODBC client from long running queries. If a query

exceeds the specified time before the data source returns the

result set, the OSS ODBC/MX Client Driver returns HYT00

(Timeout expired) to the ODBC client.

SQLCancel Function In an ODBC 2.0 application when the query is not running,

ODBC/MX implements the SQLCancel function as an

SQLFreeStmt with the SQL_CLOSE option.

If the query is running, ODBC/MX tries to stop the server. If

the attempt is successful, the client application receives an

error and must reconnect.

In an ODBC 3.0 application with a query (or queries) running,

ODBC/MX behaves as it does for a 2.0 application. In an

ODBC 3.0 application with no query running, ODBC/MX does

not implement the SQLCancel function. The application is

responsible for closing the cursor.