ODBC Server Reference Manual
Managing Customized Catalogs
HP NonStop ODBC Server Reference Manual—429151-002
7-51
INDEX Statements
AS logical-objectname
specifies the logical name for the index; logical-objectname can be in any of
the following formats:
object-name
logical-user-name.object-name
database-name.logical-user-name.object-name
database-name..object-name
Any value you specify for database-name must be a customized NonStop ODBC
Server database. If you omit database-name, the default is the default database
defined in the current profile. If the current profile does not specify a default
database, then database defaults to MASTER unless a USE DATABASE
statement is in effect.
The NonStop ODBC Server fully qualifies logical-objectname before
performing the INDEX operation. Any optional values you omit are determined by
the user profile of the current process.
For ADD INDEX, the NonStop SQL/MP base table must also be mapped in the
specified NonStop ODBC Server database.
The logical-objectname you specify cannot currently be mapped to a different
Guardian file name. If you specify logical-user-name, it must map to the owner of
nssql-filename. If this association does not currently exist, it is automatically
created when you execute ADD INDEX.
Considerations – ADD INDEX
The ADD INDEX statement:
•
Creates new mapping entries in ZNUOBJ and ZNUIX for the specified index table
•
Adds a mapping entry to ZNSUS, if logical-user-name is not currently mapped
to the owner of nssql-filename
•
Generates an error if nssql-filename is already mapped in the appropriate
object file
•
Generates an error if nssql-filename is not a valid NonStop SQL/MP index
•
Generates an error if the index table you specify is not registered in the NonStop
SQL/MP database
•
Generates an error if the corresponding base table is not registered in this
NonStop ODBC Server database
•
Generates an error if you are not authorized to modify the current user catalog
•
Generates an error if database-name is not a customized NonStop ODBC Server
database
•
Generates an error if logical-objectname is already mapped to a different
Guardian file name