MX Release 3.2 (H06.25+, J06.14+)

Setting MXCS Service Attributes

The MXCS service is started differently from NonStop ODBC Server, which uses a configured value

for SCS. For detailed information on starting MXCS, see “Starting an MXCS Service manually”

(page 21).

Server: Preserving User Alias Settings

MXCS uses Safeguard aliases or Guardian user names; it does not use NonStop ODBC Server

user alias definitions. In addition, MXCS does not associate user names with object names as part

of the three-part name unless the you configure them that way. SQL/MX schema names can be

any user-defined logical name. NonStop ODBC Server profile information is stored only by data

source name (server class), and all users share access to all data sources in any instance of the

association server in the same NonStop system.

The NonStop ODBC Server environment maps existing Guardian user names with user name

aliases. Use these aliases in NonStop ODBC Server to identify:

• The owner (schema) of object names in a given database (catalog).

• 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. For more details on how to add a user alias, see

the Safeguard documentation.

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.

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

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” (page 62).

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

an automatic mapping for ODBC API calls between a SQL/MX Release 2.x application and a

SQL/MX Release 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 TSQL 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.

NOTE: You do not need to migrate the ODBC API calls from a SQL/MX Release 2.x application

to a SQL/MX Release 3.x application because the Driver Manager already provides the version

mapping.

62 Migrating Applications from NonStop ODBC Server