Processing considerations

Because Accounting is one of the most frequently used report sets, consider the effects on batch resources. To reduce processing time when producing Accounting reports and traces, only ask for the information that you really need.

Before producing a report or trace, consider how much detail you need.

Use the short (default) layouts of reports and traces whenever possible. In most instances these provide enough detail for monitoring and problem determination.

A detailed report that uses all input data that was gathered for a long period uses a lot of system resources. The result is pages of information that you are probably not interested in.

To avoid unnecessary processing overhead and to save time:
  • Consider carefully how detailed a report you need.
  • Filter the input data – preferably by using the GLOBAL command.
  • Disable OMEGAMON for Db2 Performance Expert internal sort if appropriate.
  • Define groups for identifiers that you want reported as a single entry.
  • Specify a REDUCE INTERVAL only to report by intervals or to produce several reports with different time spans.
  • Define exception thresholds only for fields that you are interested in.
  • Specify DPMOUT or keep a Save data set only if you are sure that you want to report the data again.