MX 2.x)

Migrating Applications from NonStop ODBC Server

HP NonStop SQL/MX Connectivity Service Manual—524944-008

A-10

Client-Side Migration Steps

•

User profile information (default database name, default schema name, default

location for the creation of objects, default security, trace configuration, accounting

configuration, resource governing configuration, SQL access mode, cursor mode,

SQL dialect, maximum statement caching, control statements).

•

The mapping between SCS and Server class names.

To preserve the user aliases in the NonStop ODBC Server environment, you must add

those user alias names to the Guardian Safeguard system. See the Safeguard

documentation for more details on how to add a user alias.

To preserve a user alias name as the second part of the name (schema name), you

must explicitly add the tables by using that logical name. MXCS does not automatically

link between the Safeguard system and the MP_PARTITIONS name.

Client-Side Migration Steps

1. Install the ODBC/MX client interface. For additional information, see the ODBC/MX

Driver for Windows Manual.

2. Modify your ODBC applications then execute the ODBC applications through the

new ODBC/MX driver. For detailed information, see Client: Modifying Applications

on page A-10

Most ODBC applications do not need to be modified because the Microsoft driver

manager provides an automatic mapping for ODBC API calls between a 2.x application

and a 3.x driver. You might need to make changes when using features that are

specific to NonStop ODBC Server (for example, pass-through commands or using T-

SQL and some Microsoft SQL Server-like system tables).

Client: Modifying Applications

To migrate ODBC-compliant applications that do not use or require specific NonStop

ODBC Server features, simply redefine the client data sources to use the ODBC/MX

driver. When redefining client data sources, you may use the same name to replace

the previous data source definition, but you must delete the old definition and create

the new definition with that same name.

To migrate ODBC applications that use specific NonStop ODBC Server features, you

must replace the existing proprietary features with equivalent ODBC/MX features. .

You must modify:

•

SQL statements (to comply with SQL/MX syntax)

•

NonStop ODBC Server-specific syntax commands

Note. No action is required if you use Guardian user IDs to connect to the MXCS environment.

Note. You do not need to migrate the ODBC API calls from a 2.x application to a 3.x

application because the Driver Manager already provides the version mapping.