SQL/MX 2.x Reference Manual (H06.04+)

SQL/MX Statements
HP NonStop SQL/MX Reference Manual—540440-003
2-9
Considerations for ALTER SQLMP ALIAS
If you do not specify \node, the default is the Guardian node named in the
=_DEFAULTS define.
Considerations for ALTER SQLMP ALIAS
Usage Restrictions
If the specified alias does not exist or the specified Guardian file does not exist,
NonStop SQL/MX returns an error. If the ALTER SQLMP ALIAS statement specifies a
physical file name that is the same as the current alias mapping, NonStop SQL/MX
returns a warning.
Security of Alias
To alter an existing SQL/MP alias, you must own its schema or be the super ID.
Comparison With Previous Versions
In SQL/MX releases earlier than SQL/MX Release 2.x, the maximum length of the alias
name was 200 characters. Starting with these releases, the alias name is an ANSI
name.
The ALTER SQLMP ALIAS statement was not supported in product versions prior to
SQL/MX Release 2.x.
Late Bind
If you compile an application that uses an SQL/MP alias and later you change the
SQL/MP alias to map to a different SQL/MP table, the SQL/MP table definition is no
longer compatible with the definition used at compile time. As a result, you must
manually recompile applications that use the alias. If the late bind does not find the
SQL/MP table underlying the SQL/MP alias or if the SQL/MP table was moved,
NonStop SQL/MX returns an error.
For more information, see the SQL/MX Programming Manual for C and COBOL.
Examples of ALTER SQLMP ALIAS
•
This example changes the physical name of an SQL/MP table:
ALTER SQLMP ALIAS SAMDBCAT.PERSNL.EMPLOYEE
\MYSYS.$SAMDB.PERSNL.NEWEMP