Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 (

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

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

Status Not under 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
  • Guest
    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

  • Guest
    May 14, 2020

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