SQL/MX Connectivity Service Manual (SQL/MX 2.x)

Migrating Applications from NonStop ODBC Server
HP NonStop SQL/MX Connectivity Service Manual—524944-008
A-14
Modifying Pass-Through Commands
SYSINDEXES SYSTYPES
SYSMESSAGES SYSUSERS
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. .
Features Not Supported
The following NonStop ODBC Server features are not supported:
•
DBLib messages using the TDS transport. To work around this, you can use an
intermediate gateway to convert TDS messages to ODBC calls.
•
IPX/SPX and Named Pipes network protocols. To work around this, you can use
an intermediate gateway to convert protocols to TCP/IP.
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.
NonStop ODBC Server
Pass-Through Commands MXCS Equivalents
SQL commands for sending SQL/MP
commands
Change the syntax to SQL/MX syntax.
UTIL commands for executing ODBC
utility commands
Not supported. However, you can add new
table logical names using the CREATE
SQLMP ALIAS command and drop table
logical names using the DROP SQLMP
ALIAS command.
SET commands for setting environment
variables
If the SQL/MX language supports the
commands, they can be sent directly.
CONTROL statements defined in SQL/MX
can also be sent (no special syntax is
required).