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-4
CREATE SQLMP ALIAS Command
CREATE SQLMP ALIAS Command
Using SQL Scripts to Automate Name Mapping
You can simplify the process of adding logical names based on NonStop ODBC Server 
names by running an SQL statement in MXCI that produces a script with SQL 
statements. You can edit the script and use MXCI to execute it to create the alias 
names. 
Figure A-1. Mapping NonStop ODBC Server Name Components to ODBC/MX
CREATE SQLMP ALIAS catalog_name.schema_name.object_name 
Guardian_file_name;
catalog_name logical name of an existing SQL/MX catalog (database name 
in NonStop ODBC Server)
schema_name logical name for an existing SQL/MX schema (owner name in 
NonStop ODBC Server)
object_name logical name for the object name (table or view)
Guardian_file_n
ame
physical name (fully qualified) of the object name (table or 
view)
ODBC_DATA02_CAT
 T_DBNAME
DBO
 T_UNAME
EMPLOYEE
 T_OBJNAME
 \ODBC.$DATA02.PERSNL.EMPLOYEE
 N_OBJNAME
ZNSDB ZNUOBJ
 MXCS_DATA02_CAT.DBO.EMPLOYEE \MXCS.$DATA02.PERSNL.EMPLOYEE
;
 CREATE SQL/MP ALIAS
NonStop(TM) MXCS
NonStop(TM)
ODBC Server
VST003.vsd










