NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
C-67
Considerations—CONTINUE
process or directly or indirectly modify DEFINEs) between error 1619 and a
CONTINUE statement:
The SQLCI process also acts as if you specified SET BREAK_KEY OFF, returning
control to the previous Break key owner (usually TACL) if you hit the Break key.
(This allows you to return to TACL to execute other commands prior to continuing
the DDL operation, then type PAUSE to return to SQLCI and execute a CONTINUE
statement.) In addition, SQLCI prompts with a dedicated-operation-in-progress
prompt (D>) instead of the normal SQLCI prompt to remind you that an operation in
progress is waiting for a CONTINUE statement.
An SQLCI process that does not use a terminal as an IN file (for example, one
which reads SQLCI commands from a disk file) also protects you from modifying
DEFINEs but does not protect you from terminating the SQLCI process.
Terminating the SQLCI process while an operation in progress is waiting for a
CONTINUE statement (either by reaching the end of the IN file or by executing an
EXIT command) leaves SQL objects in the inconsistent state described earlier in
this consideration.
A host language process does not protect you against either modifying DEFINEs or
terminating the process unless you explicitly code such protection into the program.
Make sure that a host language process that receives warning 1619 responds with a
CONTINUE statement before terminating or taking any action that modifies a
DEFINE.
ADD DEFINE ALTER DEFINE CATALOG DELETE DEFINE
EXIT SET DEFMODE SYSTEM VOLUME
Note. SQL does not prohibit you from executing a transaction between receiving warning
1619 and executing a CONTINUE statement, but you must complete the transaction prior
to executing the CONTINUE statement. Attempting to execute a CONTINUE statement
within a transaction causes SQL to roll back both the operation you attempted to
CONTINUE and any other operations included in the transaction.