Debbie,
        We've got our BUFPOOLSIZE set to 131072 and are running ADSM V2.1.5.13
with a 14 GB database - this gives us a cache hit ratio > 99%.  I'd bump
the settings up in 4096 increments until you get the the cache hit ratio
in the 98-99% range.  Prior to V2.1.5.13, we were running with a
bufpoolsize of 65536 and couldn't go any higher (ADSM wouldn't come up).
 Since we have plenty of memory on the AIX server, I just went ahead and
doubled it.

Tim Pittson
tpittson AT himail.hcc DOT com



Date:    Tue, 28 Oct 1997 18:24:02 -0400
From:    Debbie Yoder <dyoder AT GPU DOT COM>
Subject: ADSM Database Cache Hit Percent

Hello Everyone,

We are trying to increase our ADSM database cache hit percent. Our ADSM
previously was running with a cache hit percent of only 83.44%. This
percent was based upon a BUFPOOLSIZE number of 10240K. We increased the
BUFPOOLSIZE number (in 11 increments of 1024K) to a current value of
21504K. This new value still only is giving us a cache hit percent of
around 96.13%.

I attended 2 sessions at the IBM International Storage Symposium in
August,
and they said to shoot for a cache hit percent of 98 or 99%. Is there
any
kind of max limit to the BUFPOOLSIZE specified? or should we just keep
increasing it until we reach 98 or 99%? (we realize that a trade-off is
server memory).

We are running ADSM MVS server level 2.1.0.13.
Any/all help will be greatly welcomed and appreciated.

Debbie Yoder
GPU Energy