We also see a tremendous amount of CPU resources allocated to our MVS ADSM 
servers. And I can only join Christo by stating that it's not only
reclamation but it's actually any process like Migration or Expire Inventory 
which is associated with heavy DB access load.
We were initially quite happy with the 2.1.10 maintenance, which eliminated our 
daily 'Q Occ' CPU cruncher (for billing purposes) of about
60+MIPS over a 90 minutes period. But then we noticed another CPU usage problem 
NOT related to DB access. Tape allocation processing had been
changed by IBM in 2.1.10, and a new tape mount wait loop caused high CPU usage  
during outstanding tape mounts. This has been fixed now to some
extend in 2.1.12.
ADSM's CPU usage is our biggest concern in the current environment. It's far 
beyond DFHSM or other comparable subsystems/address spaces. The
product will only regain widespreaded acceptance in the MVS world, when IBM can 
make significant improvements in this area. The 'Q Occ'
improvement is at least encouraging.

/----------------------------------------------------------------\
| Hans Beierle                      Internet: hbeier AT eds DOT de      |
| EDS Informationstechnologie       Voice: ++49 6142 803170      |
| und Service (Deutschland) GmbH    FAX:   ++49 6142 803030      |
| Eisenstr. 56 (N15)                                             |
| D-65428 Ruesselsheim, Germany                                  |
\----------------------------------------------------------------/



Christo Heuer wrote:
>
> Eric,
>
> I've also noticed this high CPU utilization, but not only during
> reclamation but any function ADSM does. At this stage our ADSM server has
> the highest CPU usage of any product we're running! It even uses more than
> DFHSM that does about 20 times more work.
>
> Maybe the ADSM development can explain why the number of I/O's compared
> with the CPU usage is so out of proportion.
>
> As there are no parameters that I know about that you can control this
> weird behaviour with we're starting to run into problems with our capacity
> people......
>
> Regards
> Christo Heukr
>
> ----------
> > From: Eric van Loon <evanloon AT KLM DOT NL>
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: CPU utilization reclamation process
> > Date: Thursday, February 20, 1997 1:23 PM
> >
> > Hi there!
> > We are running ADSM/MVS 1.2.10. Each morning at 6:00 AM (most tape units
> are available at that time) I update the storage pool to kick-off
> reclamation. The CPU utilization goes sky-high at that moment. ADSM uses at
> that point as much CPU as our DB/2 does!!! I cannot think of a reason why
> reclamation should be so CPU bound.
> > Is there a way to influence this? Thanks for any reply!
> > Kindest regards,
> > Eric van Loon

--
=========================================================================