IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Under review
Workspace Db2 for z/OS
Created by Guest
Created on Apr 7, 2021

additional Db2 accounting info when SELECT FROM FINAL TABLE is used

When I use SQL UPDATE then the accounting information is very clear that UPDATE was used.

If I wrap that UPDATE with SELECT FROM FINAL TABLE on the outside then the accounting information does not clearly show UPDATE was used. This is tricky and almost misleading. The accounting output does show that SELECT was used (technically, the select or open/fetch count increases). The UPDATE counter is zero!

The information is indirectly available in the accounting via the ROWS_UPDATED counter. Basically, if I want to find how often I use SELECT FROM FINAL TABLE in my accounting then I must search and find SELECT (or OPEN/FETCH) greater than zero along with ROWS_UPDATED counter. then I know SELECT FROM FINAL TABLE was used. But I consider this a non-obvious method to find when this SQL syntax was used.

My idea is to add new accounting flag (IFCID) to indicate SELECT FROM FINAL TABLE was used. To make it obvious and clear that this SQL syntax was used.

Remember, the SELECT FROM FINAL TABLE syntax for DB2 is relatively new. But I really like it this relatively new SQL syntax and I encourage my developers to consider this SQL when they create application SQL or write data-zaps. I think it is very useful SQL...

I would find it easier to review if this SQL syntax was actually used if the information was more obvious in the accounting trace output!

you know... let us say I was asked to find which Db2 threads/programs did "update". In the past I would look at the accounting trace UPDATE counter. But now I have to remember to be more careful in my review of accounting history/

Obviously (to me)... my whole RFE also applies to SELECT FROM OLD TABLE too.

Needed by Date Dec 31, 2021