Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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 https://ideas.ibm.com



Status Future consideration
Created by Guest
Created on Feb 12, 2026

Rework Distributed activity reporting for Db2 acctg data in OMPE Batch reporting

As per Matthias' request, I am opening an aha idea for this.

In Db2 accounting records you have a DRDA section where you see all the remote access involved in the thread or the rollup record.

In an accounting trace report all is well, but when I run an accounting report report the output is very confusing.

So let’s use an easy example to illutrate:

There are two accounting records involved – a normal dealloc one and a rollup one  (the ‘normal one is some dummy tran as it does not do anything but that’s not important)

 Acctg trace

* Not a rollup thread

---- DISTRIBUTED ACTIVITY ------------------------------------------------------------------------------------------------------- 
REQUESTER      : ::172.24.245.174    COMMITS(1) RECEIVED:         0    BYTES SENT     :        10    CONVERSAT.INITIATED:       0 
PRODUCT ID     : JDBC DRIVER         ROLLBCK(1) RECEIVED:         0    BYTES RECEIVED :        10    NBR RLUP THREADS   :       1 
PRODUCT VERSION: V4 R25M0            SQL RECEIVED       :         0    THREADS INDOUBT:         0                                 
PRODUCT LEVEL  : 23                  MESSAGES SENT      :         1    ROWS SENT      :         0                                 
METHOD         : DRDA PROTOCOL       MESSAGES RECEIVED  :         1    BLOCKS SENT    :         0                                 

 

rollup record

---- DISTRIBUTED ACTIVITY -------------------------------------------------------------------------------------------------------   
REQUESTER      : ::172.24.245.174    COMMITS(1) RECEIVED:         5    BYTES SENT     :     28771    CONVERSAT.INITIATED:       0   
PRODUCT ID     : JDBC DRIVER         ROLLBCK(1) RECEIVED:         0    BYTES RECEIVED :      7401    NBR RLUP THREADS   :       5    
PRODUCT VERSION: V4 R25M0            SQL RECEIVED       :        23    THREADS INDOUBT:         0                                   
PRODUCT LEVEL  : 23                  MESSAGES SENT      :        28    ROWS SENT      :       182                                   
METHOD         : DRDA PROTOCOL       MESSAGES RECEIVED  :        28    BLOCKS SENT    :         9                                   

 

In the accounting report output, I see the following and it is very difficult to see whether the data are the totals or averages.
(I annotated a bit and put A=avg and T=total based on what I see in the individual acctg recs)

 

Acctg report <--

REQUESTER      : ::172.24.245.174    CONV.INITIATED     :    0.00 A?   MESSAGES SENT    :     14.50 A   ROWS SENT    :   91.00 A
PRODUCT ID     : JDBC DRIVER         #COMMIT(1) RECEIVED:       5 T    MESSAGES RECEIVED:     14.50 A   BLOCKS SENT  :    4.50 A
PRODUCT VERSION: V4 R25M0            #ROLLBK(1) RECEIVED:       0 T?   BYTES SENT       :  14390.50 A   #DDF ACCESSES:       2 T? (#records) #rlup thds ?)
PRODUCT LEVEL  : 23                  SQL RECEIVED       :   11.50 A    BYTES RECEIVED   :   3705.50 A   #RLUP THREADS:       6 T
METHOD         : DRDA PROTOCOL                                         #THREADS INDOUBT :         0              

 

  • I am guessing that the values with a decimal point somewhere are averages and the others are totals. Is that correct ?
  • Would it be possible to make this more clear ? (either by adding ‘avg. ‘ or so, or putting them under a heading that indicates avg and total (see below).

When I look at the averages they seem to be averaged over the sum of #DDF ACCESSES values (basically the number of accounting records where this requester appeared)

  • Would it not be better to average over #RLUP THREADs ?

That’s like the number of #occurrences. That is used as denominator for the calculations for the other accounting counters, so would be more in line with that.

Would a layout like like this make sense ?

 

                                   Average                         Average                      Total                      
REQUESTER      : ::172.24.245.174  ----------------------------    ---------------------------- ----------------------------
PRODUCT ID     : JDBC DRIVER       CONV.INITIATED     :    0.00    MESSAGES SENT    :     14.50 #COMMIT(1) RECEIVED:       5
PRODUCT VERSION: V4 R25M0          SQL RECEIVED       :   11.50    MESSAGES RECEIVED:     14.50 #ROLLBK(1) RECEIVED:       0
PRODUCT LEVEL  : 23                ROWS SENT    :   91.00          BYTES SENT       :  14390.50 #THREADS INDOUBT :         0
METHOD         : DRDA PROTOCOL     BLOCKS SENT  :    4.50          BYTES RECEIVED   :   3705.50 #DDF ACCESSES:             2
                                                                                                #RLUP THREADS:             6
Needed By Quarter