SQL/MX 3.2 Reference Manual (H06.25+, J06.14+)

SQL/MX Statements

HP NonStop SQL/MX Release 3.2 Reference Manual—691117-001

2-11

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.

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