SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
S-43
Considerations—SET SESSION

SQLCI responds to the Break key based on the setting of the BREAK_KEY
session option:
The previous owner is usually the process from which you started the SQLCI
session. You can resume execution of the SQL or OBEY command.
An SQL command is a DDL, DML, DCL, PREPARE or EXECUTE command. If one
of these commands is rolled back, SQLCI uses ROLLBACK WORK to terminate
the current transaction and displays a message. The compiled form of the DDL or
DML command is discarded. The next time you execute the command, SQLCI
prepares it again and consequently causes a delay.
A DDL command that is not executing in a user-defined TMF transaction might
complete before you press the Break key. To determine whether the command
completed, you must examine the database. For example, you can use the FILES
command to determine whether an object you were dropping when you pressed
the Break key still exists. If you enter STOP sqlci-process-id at the command
interpreter prompt, TMF rolls back the current TMF transaction. Changes to
audited objects are undone, but changes to nonaudited objects are not undone.

An interactive SQLCI does not terminate after an error in the main level of input
despite ERROR_ABORT being set to ON. The main level of SQLCI input is the file
specified by the SQLCI run command IN, INV, or INLINE options, or implied by
their absence.
Interactive processing includes:

A user's home terminal TACL process

SQLCI / IN file, OUT file,.../
Executing Command
BREAK_KEY
ON
BREAK_KEY
OFF
BREAK_KEY
ON or OFF
SQL commands Command rolls
back; SQLCI
prompts.
Control returns
to previous
owner.
OBEY command Command
terminates;
SQLCI prompts.
Control returns
to previous
owner.
FC command Command
terminates and
SQLCI prompts;
BREAK_KEY
has no effect.
Other SQLCI commands
(whether or not within
user-defined transaction)
Command
terminates;
control returns to
previous owner;
BREAK_KEY
has no effect.