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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Workspace Db2 for z/OS
Created by Guest
Created on Jun 24, 2020

Begin / End COMMIT instrumentation for DRDA, CICS/IMS

Complex CICS/IMS or DRDA transactions (involving multiple programs with an implicit Commit at the end) are incorrectly presented on the Omegamon Accounting Report/Trace. By design the costs of the tough SYNC (COMMIT) operation are added to the last invoked Db2 package and its SQLs. That leads to incorrect reports, forcing DBAdmins to be concerned about SQLs which 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 performance although there is no INSERT problem but the costs of the

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

We would like Begin/End COMMIT instrumentation implemented in Db2, that would allow for precise reporting of the COMMIT elapsed and performance times. Later the OMPE Accounting/SQLACTIVITY Reports based on that information will give us much clear particular package overhead as well as exact COMMIT processing costs.

Needed by Date Jun 24, 2020
  • Guest
    Jan 25, 2021

    Hello Janet ,


    According to my knowledge the problem appears on the border between Omegamon reports and the data Db2 prepares in the traces. Although OMPE SQLACTIVITY TRACE gives correct time for SYNC operation, unfortunately Omegamon can not generate correct OMPE ACCOUNTING REPORT/TRACE without changes in the traces/IFCIDs .
    Today OMPE ACCOUNTING generates misleading reports charging last invoked package with the costs of the COMMIT.

    Many sites worldwide base their analisys only on the Accounting because of its simplisity and because it is really tough to analyze SQLACTIVITY TRACE in a very large environment.

    Regards,
    Pawel Hryb

  • Admin
    Janet Figone
    Jan 15, 2021

    Thanks for the suggestion. We would like to understand some details. Db2 today writes the following instrumentation for local attached transaction. We believe this should be enough information. Do you need more information for CICS/IMS ? Performance trace IFCID 88/89 (Begin/End of SYNC requests), IFCID 70/71 (Begin/End of commit phase 2). IFCID 3, accounting for local application also report the commit time under QWACAWTE. “

    For DRDA, we agree that the commit instrumentation is missing other than commit received in DDF section and accounting trace only reports the commit process as “Force LOG WRITE”. We need to investigate how we can implement this for DRDA, but please confirm the question on the local application.

    Thank you.