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-6
Comparison of Configuration Terms
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.
Comparison of Configuration Terms
To configure the MXCS environment, use NSM/web or MXCI. The service does not
have to be started for you to configure MXCS data sources.
NonStop ODBC Server user aliases can be created in Safeguard at any time.
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.
NonStop ODBC Server
Configuration MXCS Configuration
Resource governing Same concept defined in the data source using the
Resource Management tab.
Trace Not Applicable
Query status Not Applicable
Control statements Same concept defined in the data source using the
Control tab.
Profiles (maps to resource
governing, resource accounting,
trace and default SQL values)
MXCS has no profile concept. The data source
configuration provides an equivalent concept for all
users connecting to the data source (by name).
User name aliases (and map to a
profile)
User aliases are not added to the ODBC
environment. To preserve the same alias name, add
them as Safeguard aliases. In addition, MXCS uses
Guardian user names and IDs.
Server class (map them to a profile
and user name)
Data source configuration (which includes control
statements, define names, and SET environment
variables).
SCS configuration The configuration parameters are provided as part of
the command line, as defined when starting the
MXCS service. Configuration parameters are not
stored and no check on overlapping parameters
occurs between multiple instances of the MXCS
service in the same system.
Network configuration The configuration parameters are provided as part of
the command line.
Map server class names to SCS
names
Not Applicable. All data source names (and
configuration values) are shared between all
ODBC/MX service instances in the same system.
Map user name aliases to SCS and
server class names
Not Applicable