Within Sysview Performance Management Option for Db2 for z/OS (IDB2), 95% of archive data is missing in a busy system
with a lot of activity on a particular day. What could be the reason?
It appears there was a IDB2 data collector which had minimal activity for the first 16 days that it was up, and then the activity exploded,
and this data collector was not set up to handle it. Between September 23rd and October 9 there were a TOTAL of 181,000 thread accounting records received.
Then, another 137,000 records on October 9th in 30 minutes (between 11:30 AM and 12:00 PM). The conclusion here was that the archive job
was being submitted so frequently that the process stopped working correctly, possibly due to delays in the running of the offload.
If this level of activity is to be expected here is what is required:
A) Increase the size of the accounting file, which is only large enough to hold about 20,000 records
B) Turn on compression of the history data using the parameter HISTORY-COMPRESSION=YES