MX Release 3.2.1 (H06.26+, J06.15+)

A Migrating Applications from NonStop ODBC Server

You must migrate your NonStop ODBC Server applications if you plan to take advantage of the

compiler and executor features of SQL/MX for your applications. By migrating your applications,

you also take advantage of the ODBC 3.5 compliant API driver. Like SQL/MX (BSR X3.135-1992),

ODBC/MX is based on the ISO/IEC 9075-3 standard, documented by Microsoft in the ODBC

3.5 Programmer's Guide.

• Most ODBC applications can be seamlessly migrated from the NonStop ODBC Server

environment to the MXCS environment by duplicating the object names from NonStop ODBC

Server.

• In some cases, minor changes are required to configure the SQL/MX environment to match

the NonStop ODBC Server environment.

This section provides two checklists that describe necessary application modifications for migration

in both the server and the client environments.

Topic

“Server-Side Migration Steps” (page 56)

“Server: Duplicating NonStop ODBC Server Logical Database Object Names” (page 56)

“Server: Migrating NonStop ODBC Server Configuration Settings” (page 59)

“Server: Preserving User Alias Settings” (page 62)

“Client-Side Migration Steps” (page 62)

“Client: Modifying Applications” (page 62)

“Features Not Supported” (page 66)

“NonStop ODBC Server Migration Example” (page 66)

Server-Side Migration Steps

1. Install SQL/MX on the NonStop system (including MXCS). See SQL/MX Installation and

Management Guide for detailed instructions.

2. Start the MXCS service by using MXOAS. For detailed information, see “Starting an MXCS

Service manually” (page 20).

3. Duplicate the NonStop ODBC Server logical database object names to the SQL/MX

environment. For detailed information, see “Server: Duplicating NonStop ODBC Server Logical

Database Object Names” (page 56)

4. Migrate the NonStop ODBC Server configuration settings to MXCS. For detailed information,

see “Server: Migrating NonStop ODBC Server Configuration Settings” (page 59).

5. Preserve the user alias settings. For detailed information, see “Server: Preserving User Alias

Settings” (page 62).

For more information on migrating to SQL/MX Release 3.2 or later, see “Migrating from SQL/MX

Release 2.3.4 to SQL/MX Release 3.2” (page 24).

Server: Duplicating NonStop ODBC Server Logical Database Object Names

Database Object Names

Both products use three-part logical names to identify database objects, as follows:

database.owner-name.object-nameNonStop ODBC Server

catalog.schema.object-nameSQL/MX

56 Migrating Applications from NonStop ODBC Server