Value SKPT Requests in ACCUM mode lost over 4 billion records

Document ID : KB000118746
Last Modified Date : 01/11/2018
Show Technical Document Details
Issue:
Changes made to EDM_SKELETON_POOL have effects on  the SKPT requests and loads using ACCUM mode daily. It appears that the requests are loosing values with time. Here is an example:
On this instance  day before requests was 4221779K and loads 148443 the next day requests was 174361K and loads 153982. The requests field lost over 4 billion! How can this be explained?
Resolution:
The values in question come from the DB2 QISE block in the statistics trace record. The SKPT requests and loads are from fields QISEKTG and QISEKTL, both of which are defined as fullword (DS F) fields. The maximum value for a fullword is a little over 4 billion, so it will eventually roll over. The best option here is to request that IBM make these fields doublewords. If IBM is not going to do it, then there is the option for CA Sysview/DB2 to create a separate, larger field for these values and track rollovers of the IBM field. This option is a more complicated option, and would need to be scheduled as a product enhancement.