In some cases the basic GiAPA data collection and analysis will show that a job might have a performance problem, but a further analysis is needed to pinpoint the cause of the problem.

In many such cases one of these additional GiAPA tools will get the job done:

•          Front ends to IBM’s PEX (Performance Explorer), making it easier and quicker to use PEX, and offering reports giving additional analysis of the PEX data.

•          Tools to start collection of and analyze job trace data – the reports are particularly useful in cases where a job has an unsatisfactory performance without showing much use of resources.

•          Data base analysis.

•          Query and SQL optimizer message analysis for all jobs.

•          Tracking tool to tell WHO is using WHICH query WHEN and HOW.

Else you may have to turn to IBM tools – it is an iPerformance policy not to “re-invent the wheel” and thus not create tools to analyze problems that easily can be diagnosed with an existing tool.