User's Guide

Part II. Tutorials

Chapter 5. Using ISQL

The Stop button is used to cancel a command.

A Stop operation stops current processing and prompts for the next command. If a command file was being processed, you are prompted for an action to take (Stop command file, Continue, or Exit ISQL). These actions can be controlled with the ISQL ON_ERROR option (see "SET OPTION statement").

Reported errors

When an abort is detected, one of three different errors will be reported depending upon when the abort is detected.

1. If the abort is detected when ISQL is processing the request (as opposed to the database engine), then the following message is displayed:

        ISQL command terminated by user

   stops processing immediately and the database transaction is left alone.

2. If the abort is detected while the database engine is processing a data definition command (CREATE, DROP, ALTER, etc.), the following message appears:

        Terminated by user -- transaction rolled back

   Since data definition commands all perform a COMMIT automatically before the command starts, the effect of the ROLLBACK is to just cancel the current command.

   This message also occurs when the database engine is running in bulk operations mode executing a command that modifies the database (INSERT, UPDATE, and DELETE). In this case, ROLLBACK cancels not only the current command, but everything that has been done since the last COMMIT. In some cases, it may take a considerable amount of time for the database engine to perform the automatic ROLLBACK.

3. If the cancel is detected by the database engine while processing a standard data manipulation command (SELECT, INSERT, DELETE, etc.) and the engine is not running in bulk operations mode, then the following message is displayed.

        Statement interrupted by user.

   The effects of the current command are undone, but the rest of the transaction is left intact.