Articles & Content
Topic: 2007 EU
Subtopic: DB2 for z/OS
DATE: 2007-11-6 (16:45 - 17:45)
SPEAKERS: Bryce Krohn (Krohn Enterprises, Inc.)
In the everyday world of running a large DB2 installation, many questions need to be answered. Online monitors are great tools for the short-term identification of problems, but cannot help identify trends, or help answer the question: "What happened two weeks ago?" - there is too little data.On the other hand, the detail in SMF and RMF records can provide these answers, but finding them can be a daunting task - there is too much data.A performance database, which is a summary of these millions of records, is a great tool (with the right amount of data) to answer the longer term questions, as well as identifying trends.This presentation describes how my client's data sharing installation (15 members across 9 LPARs), uses a DB2 performance database - how it is built, updated, and used. The major user-defined report ("the Zeroes Report") will be discussed. In addition, future plans for additional user-defined additions to the performance database will be outlined.
EXP. LEVEL: Intermediate,Advanced
In a large DB2 shop, questions like, "Why did the performance of my transaction get so slow last week?" can be difficult to answer. Online monitors have too little data, and SMF and RMF have too much data to search through.
My clients performance database, which extracts and summarizes DB2 SMF data and loads it into DB2 tables, provides reports which can be used to track performance and look for problem resolution. SQL queries are easy to write for special scenarios.
My client's main user-defined report is the "Zeroes Report". It is currently a 107 line report, produced using REXX/DB2. It is formatted for rules of thumb from IBM, or based on user experience. Each line is produced by a simple REXX routine.
Since the database doesn't answer all questions, my client has added user-defined data to the performance database to answer additional questions regarding virtual storage usage(from IFCID 255 records), and data set extent information for DBA use.
Future plans for my client's performance database include: Developing better trending data for items like locking timeouts, CPU usage by plan/package/transaction, adding RMF data, adding displays such as DISPLAY GBP MDETAIL & GDETAIL, and XCF data.
This file is being provided by IDUG. We would encourage you to join IDUG to get full access to all of our files and resources. Joining IDUG is FREE and signing up is simple. Click here to join! or login!Click to Download
NOTE: These are only open to members of IDUG. If you are not a member, please CLICK HERE for more information.