MX 2.x)

ODBC/MX Client Overview

HP NonStop Open System Services ODBC/MX Client Driver—544990-002

1-7

Release Considerations and Restrictions

ANSI Names for SQL/MP Objects

ANSI names (also called alias names) are logical names that map to physical

Guardian names of existing SQL/MP objects.

To add ANSI alias names for SQL/MP tables, use NSM/web or the MXCI command

CREATE SQLMP ALIAS, which stores the alias name in the MP_PARTITIONS table in

the SQL/MX catalog. The SQL/MX catalog and schema names must exist before you

create the alias name. You can add alias names for NonStop SQL tables that are

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 3)

ODBC/MX client software An ODBC/MX client must be installed on an integrity NonStop

systems.

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.