Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Categories Usability
Created by Guest
Created on Apr 8, 2024

DB2 statements not directly with commit

At SQL scripts to attack DB2, we need something to just see the affected rows, or to preview the results of an update/delete/insert statement but not directly commiting the data, as at the Spufi, with some option to check in order to have this preview info before commit definively the data.

Idea priority Medium
  • Guest
    Reply
    |
    May 9, 2024

    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


  • Guest
    Reply
    |
    Apr 29, 2024

    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.

  • Guest
    Reply
    |
    Apr 8, 2024

    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