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-9
Setting MXCS Service Attributes
•
protocol name
•
IOP process name
•
SCS process name
•
Multilan specific parameters
MXCS supports only the TCP/IP protocol for remote clients and file system for local
clients on NonStop servers. All parameters required by the network are defined in the
command line when you start the association server.
The following table describes the network parameters available in both products:
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 the
MXCS Service on page 2-4.
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).
NonStop ODBC Server MXCS
Protocol TCP/IP is the only protocol supported, no
definition required
Network service name (NET_NAME) Port number defined by the -PN parameter (it is
not required to add it to the Services file)
IOP Process Name TCP/IP process name defined by the -TCP
parameter
Services file name Not Applicable
Keep alive Not Applicable
OOB Inline Not Applicable
Linger Not Applicable
Reuse address Always allowed