NonStop SQL/MP Reference Manual

Table Of Contents
NonStop SQL/MP Reference Manual142115
M-16
Considerations—MODIFY LABEL
CHECKONLY
specifies that file labels specified by target-spec should be checked to see if
they contain node numbers that match the criteria specified in the REPLACE clause.
No file labels are modified. The CHECKONLY option lets you estimate the effect of
running the MODIFY LABEL command before actually modifying the file labels.
The amount of information written to the current OUT file depends on whether
LISTALL or NO LISTALL is specified.
Considerations—MODIFY LABEL
You must be logged on as the super ID to execute a MODIFY LABEL command
unless you specify the CHECKONLY option. If the MODIFY LABEL
CHECKONLY option is specified, the user must have authority to read the SQL
objects and object programs.
NonStop SQL/MP uses the TMF subsystem to protect the integrity of the database
during the MODIFY operation. MODIFY LABEL commands are not allowed inside
a user-defined transaction.
One system-defined transaction is used for each SQL object file label modified. If
an error occurs while MODIFY LABEL is in the middle of modifying a file label of
an SQL object, the changes made to that particular label are backed out. Changes
made to other file labels by the same instance of the MODIFY LABEL command
are not backed out. Thus, if an error occurs, some labels might have been changed
and others might not have been.
SQL object program file labels are not modified within a TMF transaction. This
means that if an error occurs while modifying the file label of an object program
file, the label could be left in an inconsistent state.
The MODIFY LABEL command is one of a set of commands that uses the
MODIFY DICTIONARY utility. The other related commands are MODIFY
CATALOG Command on page M-4 (to change node names in SQL catalogs) and
MODIFY REGISTER Command on page M-22 (to register user-defined catalogs in
the local system catalog).
To minimize unnecessary searching, make your target-spec clause as specific
as possible. For example, if SQL objects reside only on subvolumes whose names
begin with SQL, specifying $VOL1.SQL*.* is more efficient than specifying
$VOL1.*.*. The MODIFY LABEL command would not have to search for SQL
objects on other subvolumes.
Multiple MODIFY commands (including LABEL, CATALOG, and REGISTER
commands) can be executed concurrently on the same node as long as each
command is processing a different set of files or catalogs. For example, if the node
number is changed on a node that has an SQL database spread out over five
volumes, five MODIFY LABEL commands can be started concurrently, each
specifying a different volume to be modified. Note that in such a case, because the
node name did not change, it would not be necessary to execute any MODIFY
CATALOG commands.