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.
|Who would benefit from this IDEA?||I think everybody. Companies will spend their efford tuning appropriate Packages/SQLs, saving their money, generating less complains about unprecise Db2 reports.|
How should it work?
1) Db2 should implement the Begin/End COMMIT instrumentation, to make possible proper reporting.
2) On the base of 1) OMPE ACCOUNTING Reports will be chaged taking into the account the separate costs of the COMMIT processing. It's very much possible the Accounting Report/Trace should be redesigned generating Dummy package information for implicit COMMIT.
3) On the base of 1) OMPE SQLACTIVITY Report will contain info about costs of the COMMIT processing, that would lead to much closer numbers between ACCOUNTING and SQLACTIVITY Reports.
|Priority Justification||Inadequate/misleading reporting in OMPE reports based on missing COMMIT IFCIDs. Not having this information makes it difficult to zoom in on performance issues as it is hard to identify how much of the time is to be attributed to executing regular SQL and how much is related to COMMIT processing.|
|Customer Name||PKO Bank Polski|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions