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.
|Who would benefit from this IDEA?||Companies using CICS/IMS environment concerning about their performance (especially INSERT performance)|
How should it work?
As far as the last invoked program has no COMMIT statement it couldn't be charged by the implicit Commit. That creates a mess. An implicit Commit should be presented as a separate operation on the higher report levels (CORRNAME/PLAN/CONNECT/etc.).
It presented correctly in the SQLACTIVITY TRACE as the separate SYNC operation and should remain separated in the other reports.
|Priority Justification||Too many Companies are fooled by incorrect reports|
|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 "firstname.lastname@example.org" 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