Confirmation panels

If there is a CONFIRM parameter on a command, you can specify YES or NO (or use the default in your profile).

If the command modifies the database and the CONFIRM parameter is YES, a confirmation panel like the following one is displayed:
Figure 1. Example of a confirmation panel
                       RUN CONFIRMATION
Your RUN command modified this number of rows in the
database:         1
Do you want to make this change?
1 1. YES - Make the changes permanent in the database.
  2. NO  - Roll back the changes to the last COMMIT operation 
           or to the beginning of the query. The database that you are 
           using with QMF determines the rollback rules. 

If the query contains multiple SQL statements, your response to the confirmation panel applies to all statements in the query unless the query contains multiple COMMIT statements. If the query does not contain multiple COMMIT statements, the answer that you provide in response to the single prompt applies to all changes that are made by all SQL statements in the query. If the query contains multiple statements that change the database and these statements are of different types, the confirmation prompt asks about only one type of statement. For example, if the query contains a DROP statement and an UPDATE statement, the confirmation prompt refers to the UPDATE statement only; however, your response to the prompt applies to both the DROP and UPDATE statements in this case.

If the query contains multiple SQL statements and multiple COMMIT statements, a confirmation panel is displayed for every COMMIT statement. However, if a COMMIT statement follows SQL statements that change only a database catalog, a confirmation panel is not displayed for that COMMIT statement.

Many QMF confirmation panels for changes to the database are actually prompting you to do a commit (by entering YES to keep the changes) or a rollback (by entering NO). Because the changes were already made to the database, the database manager holds locks on the data until you reply YES or NO on the confirmation panel.

If you are connected to DB2® Server for VSE and VM, the tables you are working with might be in a nonrecoverable dbspace. If so, any changes you make are committed to the database immediately; you cannot execute a rollback. Therefore, if a table is in a nonrecoverable dbspace, specifying NO on the confirmation panel will not prevent the changes from taking place.