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

ManualsBrandsHP ManualsServerHP Integrity NonStop J-Series

select 'SELECT ''CREATE SQLMP ALIAS '' || T_DBNAME || ''.'' '

|| '|| T_UNAME || ''.'' || T_OBJNAME || '' '' || '

|| 'N_OBJNAME || '';'' '

|| 'from \TEST.$data02.startup.znsdb, '

|| trim(N_CATALOG) || '.ZNUOBJ WHERE '

|| 'N_CATALOG = ''' || N_CATALOG || ''';'

from \TEST.$data02.startup.znsdb;

where the ZNSDB table is in the system catalog and contains a list of NonStop ODBC Server

databases, and \TEST.$DATA02.STARTUP is the catalog you are migrating to SQL/MX.

The same query is repeated for each of the NonStop ODBC Server customized catalogs to provide

a complete mapping of NonStop ODBC Server objects to the SQL/MX environment. The generated

MXCI commands have this form:

CREATE SQLMP ALIAS MASTER.DBO.TABLES \TEST.$DATA02.STARTUP.TABLES;

Accessing Migrated Names

After the names have been migrated to SQL/MX, you can access them through both MXCI and

client applications.

Server: Migrating NonStop ODBC Server Configuration Settings

You do not need to migrate the existing NonStop ODBC Server configuration to MXCS. No exact

correspondence exists between their settings. MXCS supports the same highly scalable and available

servers as NonStop ODBC Server and achieves the same functionality even when specific settings

do not match between products.

While NonStop ODBC Server configuration is performed through the NOSCOM program on the

NonStop system, MXCS uses MXCI or NSM/web (a management console) to enter the required

configuration parameters.

NOTE: If both products are used at the same time (co-exist) in the same system, the port number

defined for both products must be different, and the MXCS port range should not overlap the

NonStop ODBC Server port number.

Comparison of Configuration Terms

MXCS ConfigurationNonStop ODBC Server Configuration

Same concept defined in the data source using the Resource

Management tab.

Resource governing

Not ApplicableTrace

Not ApplicableQuery status

Same concept defined in the data source using the Control

tab.

Control statements

MXCS has no profile concept. The data source configuration

provides an equivalent concept for all users connecting to

the data source (by name).

Profiles (maps to resource governing, resource accounting,

trace and default SQL values)

User aliases are not added to the ODBC environment. To

preserve the same alias name, add them as Safeguard

User name aliases (and map to a profile)

aliases. In addition, MXCS uses Guardian user names and

IDs.

Data source configuration (which includes control

statements, define names, and SET environment variables).

Server class (map them to a profile and user name)

The configuration parameters are provided as part of the

command line, as defined when starting the MXCS service.

SCS configuration

Configuration parameters are not stored and no check on

overlapping parameters occurs between multiple instances

of the MXCS service in the same system.

Server: Migrating NonStop ODBC Server Configuration Settings 59