HP3000-L Archives

April 2005, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mike Hornsby <[log in to unmask]>
Reply To:
Mike Hornsby <[log in to unmask]>
Date:
Wed, 13 Apr 2005 10:01:59 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
**Jay Willis wrote:

 >What to look for in a Howmessy report that would indicate that a
dataset needs to be re-packed, >or capacity change needed to be done?
 >We'd rather not do a detpack on a regular basis - just when one is
indicated.

We have a free updated Data Base Loading Program called DBLOADSX at:
http://www.beechglen.com/mpe/downloads.html
The elongation statistics must take into account the prefetching performed to correctly reflect the number of
IOs that are actually generated.

In my experience, the first thing I look for is not in the detail datasets, but the max blocks in the master
datasets. For non integer key types, a large max blocks value can indicate a clustering problem.

<plug>
As part of Beechglen's support service we include a Performance Monitor and an Image dataset capacity monitor.
The performance monitor can summarize the IO being generated by Program and by Session/Job id. IMHO, this is the
best method to work backwards to database tuning tasks. The dataset capacity monitor projects fill rates and suggests
capacity changes. It also monitors the amount of free disc space required to repack or resize the largest dataset.
</plug>

Cordially,
Mike Hornsby
Beechglen Development Inc.
513-922-0509

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2