SQL/MX Connectivity Service Manual for SQL/MX Release 3.2 (H06.25+, J06.14+)

Table 9 ODBC API Mapping Between 2.x and 3.x Versions (continued)
2. x Calls Supported by
ODBC Server?
3. x Calls Supported by
ODBC/MX?ODBC 3.x Calls*ODBC 2.x Calls*
NNSQLSetScrollOptionSQLSetScrollOption
YYSQLSetStmtAttrSQLSetStmtOption
YYSQLSpecialColumnsSQLSpecialColumns
YYSQLStatisticsSQLStatistics
NYSQLTablePrivilegesSQLTablePrivileges
YYSQLTablesSQLTables
YYSQLEndTranSQLTransact
* Function names in italics are converted between both versions.
Modifying SQL Statements
NonStop ODBC Server uses Core SQL statements for ODBC connections and T-SQL statements for
DBLib clients. Core SQL language is a subset of the ANSI-92 standard.
ODBC/MX supports all DML SQL statements that are defined in SQL/MX and are compliant with
the ANSI-92 standard. In addition, SQL/MX supports ODBC extensions for function calls and
datetime literals.
ODBC/MX supports all DDL statements as defined in SQL/MX.
Grant and Revoke statements are supported as defined in SQL/MX.
Migrating SQL Server Objects
To migrate T-SQL system table objects, you must define them in the ODBC/MX environment. The
following T-SQL system table names are used by DBLib and have no ODBC/MX equivalents:
SYSOBJECTSSYSCOLUMNS
SYSPROTECTSSYSDATABASES
SYSTYPESSYSINDEXES
SYSUSERSSYSMESSAGES
NOTE: HP recommends that an ODBC-compliant application use the ODBC Catalog APIs to
retrieve catalog information instead of selecting data from Microsoft SQL Server system tables.
If NonStop ODBC Server is running, you can migrate the system tables objects by adding the
logical name mappings for those tables into the MP_PARTITIONS table; use the ANSI names to
select the tables. To prevent the name mappings from getting out of sync, use this method only if
your NonStop ODBC Server environment is not creating or dropping tables.
Modifying Pass-Through Commands
MXCS does not support the NonStop ODBC Server pass-through syntax. To migrate, you must
make syntax changes to achieve the same behavior.
The following table lists the MXCS equivalents for pass-through commands.
Column HeadMXCS EquivalentsNonStop ODBC Server Pass-Through Commands
Change the syntax to SQL/MX syntax.SQL commands for sending SQL/MP commands
Not supported. However, you can add new table logical
names using the CREATE SQLMP ALIAS command and drop
UTIL commands for executing ODBC utility commands
Client: Modifying Applications 65