Hey Marc. It's not just one table -- the system log tables (starting with SL2) have the data you're looking for. You can find this in the System Log Folder inside the CMOD GUI, but I suspect you're talking about quering from the command line.
Some background:
CMOD was created before DB2 had native support for automatic table segmentation. In the modern versions of DB2, you can, for example, split a customer database by first letter of last name, or an accounting database by year, to reduce the size of individual tables, and/or in some situations, increase the parallelism of some applications by splitting those tables across different systems.
How it works:
Because DB2 didn't have this feature originally, OnDemand does it's own 'table segmentation', based on the number of rows in a database table. You set the maximum number of rows, then when a table grows to that size, it 'closes' the current table, and opens a new one. In OnDemand, this helps performance stay close to linear for the most frequent searches -- "last 90 days" or "last 9 months". Tables that contain data outside the selected date range aren't even searched. This is also why Application Groups require at least one date field.
How to search tables:
First, search the arsag table to find your Application Group. Then use the agid to search the arsseg table. Once you search the arsseg table (preferably with a range of dates) you'll get a list of the tables that contain the data you're looking for. The last step is to query the actual table itself.
Hope that helps.
-JD.
P.S. - This was an interesting exercise for me to write up... I wonder if anyone would be interested in having me do a presentation / video / webinar on this.
