NonStop SQL/MP Reference Manual

Table Of Contents
NonStop SQL/MP Reference Manual142115
N-2
NAME Option
NAME Option
The NAME option specifies an operation name for an operation started by a statement
that includes the NAME option. Use the operation name in subsequent CONTINUE
statements or to identify EMS messages sent by the operation (see REPORT Option
on
page R-3).
operation-name
is an SQL identifier to be the name for the operation. operation-name should
normally be unique on the node so that messages from the operation are not
confused with messages for other operations using the same name. Uniqueness is
not required for the operation to work correctly. If you omit the NAME option, the
name of the operation is the first two words of the statement that initiated the
operation concatenated by an underscore (for example, ALTER_TABLE).
Considerations—NAME Option
The operation name appears in EMS messages as the token ZSQL-TKN-OP-TYPE
and ZAUD-TKN-OP-TYPE. For more information about EMS messages sent by
NonStop SQL/MP, see the NonStop SQL/MP Messages Manual.
Examples—NAME Option
The following CREATE INDEX statement uses the NAME option to name the
index-creation operation CREATE_INDADV:
CREATE INDEX INDADV ON STUDENTS (ADVISOR,CLASS)
WITH SHARED ACCESS NAME CREATE_INDADV COMMIT BY REQUEST;
Name Resolution
Name resolution is the mapping of a name in an SQL statement to a particular table,
view, index, program, partition, collation, catalog, or EDIT file. Name resolution
includes mapping DEFINEs to physical names and fully qualifying partially qualified
physical names using the current default node, volume, subvolume, and catalog names.
The time at which name resolution occurs depends upon the statement and upon whether
a CONTROL QUERY BIND NAMES AT EXECUTION directive was in effect at the
time the statement was compiled or prepared (compiled by executing a PREPARE or
EXECUTE IMMEDIATE statement). Names in an INVOKE statement in a host
language program are always resolved during host language compilation, along with
names in host language statements that are not SQL statements.
By default, SQL resolves names in a static SQL statement at program startup, resolves
names in a prepared statement at the time the PREPARE or EXECUTE IMMEDIATE
executes, and resolves names in a non-prepared SQLCI statement at the time you enter
the statement. However, if a CONTROL QUERY BIND NAMES AT EXECUTION
NAME operation-name