Skip to Main Content
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 Future consideration
Created by Guest
Created on Apr 15, 2020

More precise Accounting and SQLACTIVITY Reports with separate SYNC operation

Complex CICS/IMS transactions (involving multiple programs with an implicit Commit at the end) are incorrrectly presented on the Omegamon Accounting Report as well as on SQLActivity Report. By design the costs of the tough SYNC operation (two phase commit) are added to the last invoked Db2 package and it's SQLs. That leads to incorrect reports, forcing DBAdmins to concern about SQLs that are actually have no problems.
For example take the famous INSERT performance issue (usually executed as the last for a business transaction). Companies spend millions to improve an INSERT although there is no INSERT problem but the costs of the Two-Phase Commit.

There were two cases closed to establish that behaviour: TS002976436 and TS002533198.

Needed by Date Apr 16, 2020
  • Admin
    May Chu
    Jun 19, 2020

    Still under review - changed status to "Future Consideration"

    From prior discussions, this Idea could be changed/sent to Db2 requesting that Db2 take out / separate the SYNC processing time from the application packages and report it in a separate dummy package. From discussions with Db2, we understand this would likely be declined. We understand that Db2 would likely support implementing the COMMIT “START/END” for DRDA trans then OMPE would have subsequently to implement his SQL Act.Trace/Report with calculating and reporting the COMMIT processing times. This would be standard ‘currency support’ for OMEGAMON

  • Admin
    May Chu
    May 14, 2020

    We’ve been in discussion with the client and are considering opening a requirement to Db2