| 1. |
I already own a DB2 performance monitor - why do I need SoftBase Batch Analyzer?
Standard DB2 performance monitors only display currently running jobs and SQL statements. Batch Analyzer actually displays summaries of all DB2 batch job executions over 24 hour collection periods.
The difference here, is that Batch Analyzer can quickly identify all costly DB2 SQL statements that ran last night or last week, as opposed to hoping to be looking at the performance monitor when something bad happens. 
|
| 2. |
Where is Batch Analyzer most valuable - test or production DB2 subsystems?
Batch Analyzer is valuable in both test and production DB2 environments. For example, Batch Analyzer can quickly locate production SQL statements that have degraded in performance over time. Also, Batch Analyzer is very effective at identifying long running SQL statements when new applications are moved into production. Lastly, application developers find Batch Analyzer very useful for tuning the longest running SQL statements in programs they are developing or enhancing.
|
| 3. |
Do we have to make program or JCL changes to monitor our jobs with Batch Analyzer?
No - the newest release of Batch Analyzer, 4.1.0, features "Touch Free" collection which requires no changes to your batch or DB2 environments
|
| 4. |
Is Batch Analyzer yet another DB2 performance monitor?
Absolutely not! Batch Analyzer is designed to quickly identify the absolute worst performing SQL statements hidden in your DB2 production or test environments. Performance monitors cannot provide this type of proactive problem identification. Also, Batch Analyzer was built with application developers in mind. This product is easy enough to use to allow developers to find their own performance problems without having to enlist the aid of a DB2 DBA!
|
| 5. |
We already use CA/Platinum Detector™ or BMC Apptune™ to find expensive batch SQL statements - why do we need Batch Analyzer?
There are two reasons to use Batch Analyzer instead of Detector™ or Apptune™;- Batch Analyzer adds up DB2 performance by Job names, rather than just listing expensive SQL statements and then the Plan/Package they were located in. Job name is invaluable in locating an application group responsible for writing long-running SQL statements.
- Batch Analyzer is designed to be a continuously running solution which gathers ALL DB2 batch performance data over time. Batch Analyzer can answer key questions that both Detector™ and Apptune™ cannot address, such as how long did a job run last week or which DB2 for z/OS SQL statements are running progressively worse over time?
|
| 6. |
How hard is it to install Batch Analyzer? Who is involved in the installation process?
Batch Analyzer can be completely installed in 2 - 4 hours by a DB2 for z/OS DBA. Also, a DB2 System Programmer is needed for about 15 minutes to make a minor change to the DB2 for z/OS environment. Batch Analyzer can be gathering DB2 batch performance data at your shop in less than 1 day.
|
| 7. |
Does Batch Analyzer require any changes be made to DB2 itself?
No. Batch Analyzer does not require any internal DB2 changes or modifications.
|
| 8. |
Can Batch Analyzer be easily turned off in the event of problems?
Yes. Batch Analyzer can be stopped or started with a single command. Also, Batch Analyzer can be configured to collect performance data for specified Jobs or programs only.
|
| 9. |
Does Batch Analyzer recommend corrective action when it finds costly SQL statements?
No. Batch Analyzer does not currently recommend how to fix bad DB2 for z/OS SQL statements. DB2 DBA expertise or an EXPLAIN tool such as DB/IQ-QA is required for this functionality.
|
| 10. |
How long should Batch Analyzer hold performance data?
Batch Analyzer only stores summary data about Job, Step, and SQL performance. This summary data is far smaller than normal detailed performance traces. Most customers aggregate batch SQL performance data at least for a year. Also, SoftBase recommends archiving older performance data to tape or cartridge.
|
| 11. |
We're not experiencing any major batch SQL performance problems right now - why should we try Batch Analyzer?
How do you know that you don't have any expensive DB2 SQL statements hiding in batch Jobs and programs? Unless you sit at your performance monitor 24 hours per day, there really is no tool available that can run continuously over long periods of time and identify problem SQL statements. Why not give Batch Analyzer a try just for a few days? It only takes a couple of hours to set up and deploy - you might be surprised at what it shows you... |
