MX 2.x)

ODBC/MX Client Overview

HP NonStop ODBC/MX Driver for Windows—527888-004

1-8

Release Considerations and Restrictions

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

ODBC driver manager ODBC/MX requires the Microsoft ODBC 3.5.1 (or later) driver

manager. If you do not already have the 3.5.1 driver

manager, ODBC/MX installs it for you.

ODBC/MX client software An ODBC/MX client can be installed in the same workstation

as a NonStop ODBC Server client or other ODBC client

software.

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

for an ODBC client data source by using the ODBC/MX Setup

window in the Microsoft ODBC Data Source Administrator.

See Installing the Client Components

on page 2-1 for more

information.

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 through the Microsoft

ODBC Data Source Administrator. You must either define

the catalog and schema names using the Microsoft

ODBC Data Source Administrator, or 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 ODBC/MX driver returns HYT00 (Timeout

expired) to the ODBC client.