DB2 statements not directly with commit

Thank you for taking the time to share your enhancement suggestion. We deeply value feedback from our customers, as it plays a crucial role in shaping and improving our products. Your request aligns closely with our product strategy, and we are pleased to share that it has been planned for inclusion in a future release. We appreciate your input and continued support!

Hi, thanks for the suggestion, however by selecting the "Rollback changes on completion" option, we will always receive the rollback at the end, and developers may not realise that the SQL has not been applied.

What we are asking for is an option, that once the SQL is executed and the results are displayed, asks if you want to commit or rollback or nothing (cancel), like when in the SPUFI we select AUTOCOMMIT ...... ===> NO

The following section of IDz 16 documentation https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=zos-creating-running-sql-scripts describes Running SQL statements.  There is a Tip on the page that mentions To set options for the Run SQL commands, select the Run SQL Options menu item. The context-sensitive helps describe the options available on the Run SQL Options page.

The Run SQL Options page contains the ability to set an Action when script runs successfully 
- Commit after each statement
- Commit on completion
- Roll back changes on completion

Selecting the Roll back option prior to Run SQL should satisfy this Idea request.

This sounds like SELECT from FINAL/OLD TABLE (UPDATE/DELETE ...);

and then in your SPUFI Script - code ROLLBACK; after the Select.

This is buried kind of deep in the SELECT syntax diagram through multiple layers of pages. It is referred as data-change-table-reference and includes OLD TABLE and FINAL TABLE

See the Application Programming Manual

https://www.ibm.com/docs/en/db2-for-zos/13?topic=data-selecting-values-while-updating

https://www.ibm.com/docs/en/db2-for-zos/13?topic=tables-selecting-values-while-deleting-data