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

Object Naming and Mapping
ODBC/MX can access SQL database objects as follows:
• with an alias, for SQL/MP objects that have an alias name (See ANSI Names for SQL/MP
Objects).
ANSI Name Type
ODBC/MX supports only ANSI name types for NonStop SQL objects.
Using the client interface at a client workstation, you can configure the default catalog and schema
names used to qualify the table names in queries.
The name format is as follows:
catalog.schema.object-name
ANSI names have a maximum of 128 characters for each part of the name (not including the dots).
ANSI Names for SQL/MX Objects
ANSI names for SQL/MX objects are registered in SQL/MX metadata residing in SQL/MX format
tables.
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
An OSS ODBC/MX client must be installed on a NonStop
system.
ODBC/MX client software
An ODBC client application can set the catalog and
schema information in the ODBCDSN file. For more
Catalog and schema
information on the ODBCDSN file, see ODBCDSN File
Format.
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.
An ODBC application can call SQLSetStmtOption with the
SQL_QUERY_TIMEOUT option to specify the number of
SQL_QUERY_TIMEOUT Option
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
18 ODBC/MX Client Overview