Unlocking the Database

During Debugging, the COMMIT statement, which indicates the end of a Logical Unit of Work ( LUW), may occur after a significant number of debugging steps. Any database locks that are set are maintained for the whole of this time (see also Debugging in Production Clients).

There may be occasions when you want to interrupt your testing without actually ending the debugging session. In this case, you should release the database locks. Otherwise other users cannot make any changes to the database until the test run is complete.

To do this, choose  Debugging  Database  Commit (Unlock)  to unlock the database and permanently write the changes to the database. Remember that this could, in certain circumstances, lead to database inconsistencies.

If you want to undo all of the database changes that have been made since the last commit, choose  Debugging  Database  Rollback .

You can check the last statements transferred to the database by choosing  Goto  System  System Areas  after you have started the Debugger, and entering OSQL in the Area field.