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

CREATE SQLMP ALIAS TEST_DATA07_SAMDBCAT.DBAGRP_PRSNL.VIEW207

\TEST.$DATA07.INVENT.VIEW207;

CREATE SQLMP ALIAS TEST_DATA07_SAMDBCAT.DBAGRP_PRSNL.VIEW207N

\TEST.$DATA07.INVENT.VIEW207N;

CREATE SQLMP ALIAS TEST_DATA07_SAMDBCAT.DBAGRP_PRSNL.VIEWCS

\TEST.$DATA07.INVENT.VIEWCS;

CREATE SQLMP ALIAS TEST_DATA07_SAMDBCAT.DBAGRP_PRSNL.VIEWCUST

\TEST.$DATA07.INVENT.VIEWCUST;

Adding User Alias Names To Safeguard

To preserve the NonStop ODBC Server user alias names, map the following user alias and Guardian

user names to Safeguard aliases:

Guardian User IDGuardian User NameUser Alias

255,255SUPER.SUPERDBO

100,100DBAGRP.PERSNLDBAGRP_PERSNL

50,1SQLUSR.USER1ODBCUSR1

50,2SQLUSR.USER2ODBCUSR2

The following commands add the same aliases in Safeguard (through Safecom) by using a simple

security form:

Add alias DBO, SUPER.SUPER, password xxx

Add alias DBAGRP_PERSNL, DBAGRP.PERSNL, password xxx

Add alias ODBCUSR1, SQLUSR.USER1, password xxx

Add alias ODBCUSR2, SQLUSER.USER2, password xxx

where xxx is the password assigned by the system administrator to match the one used by the

Guardian user ID.

For detailed information on how to add and configure system security, see the Safeguard Reference

Manual.

Running and Configuring MXCS

To create an MXCS service configuration equivalent to the NonStop ODBC Server configuration,

you must first start the association server using the following command (the example uses a different

process name in addition to a different port number to let both products run in the same system):

MXOAS /name $mxoad, nowait, cpu 0, pri 140/ -PN 24000 -TCP $ZTC0

Using NSM/web or MXCI, add a data source (called NSOADMIN to match the same name, but

not required) and specify the following values:

NSOADMINData Source Name

1Min Servers

5Max Servers

1Avail Servers

System definedConnection timeout

System definedIdle timeout

NoneResource accounting

ManualStart mode

NonStop ODBC Server Migration Example 75