Jerry,
        An 86% hit ratio is very low for ADSM...  Try bumping up the
bufpoolsize to a minumum of 16384 or possibly 32768.  The logpoolsize
seems a little low also.. if you do a  Q LOG F=D and notice any log pool
pct. wait, increase this also

>----------
>From:  Jerry Lawson[SMTP:jlawson AT THEHARTFORD DOT COM]
>Sent:  Friday, August 08, 1997 8:13 AM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Reply to ADSM MVS Server Perf
>
>---------------------------- Forwarded with Changes
>---------------------------
>From: INTERNET.OWNERAD at SNADGATE
>Date: 8/7/97 3:54PM
>To: Jerry Lawson at ASUPO
>*To: *ADSM-L at SNADGATE
>Subject: Reply to ADSM MVS Server Perf
>-----------------------------------------------------------------------------
>--
>In response to my original posting, Mike Stewart responded:
>
><snip - removed original message text - snip>
>
>*** Comments From: STEWAJM - Stewart, Mike; 08/07/97 12:54pm
>
>You might check your bufpoolsize.  If your devices are staying
>that busy you might be able to speed the process by
>reducing db activity.
>
>My db size is about 5 gb, and expiration processing takes
>about 30 minutes...that is on a 9672-R3 model, to give you
>a processor speed reference.
>
>Yes, ADSM is a _big_ CPU consumer.  Your processor consumption
>seems comperable to mine (assuming our processor speeds are
>comperable).
>
>** end of response ***
>
>I forgot to put processor information in the original note - the
>system is an Amdahl 5995M 8670 - an 8 engine processor with 60
>MIP engines.
>
>Our Bufferpool is set at 1536K, and our LOGP is set at 256K
>
>Bufferpool stats usually shows aaround and 86% buffer cache hit
>ratio.
>
>Jerry Lawson
>