I agree with Chris.
I see the same effects with ADSM 3.1.2.40 on OS/390 2.6. Unfortunatly
nothing can be done, it is the Database.

Maybe TIVOLI's ADSM 3.7 announced today will bring us a relief....

Let's hope the Database gets better.

_________________________________________________

Kind Regards
Andreas Buser

Tel: ++41 61 285 73 21  Fax: ++41 61 285 70 98

Email: Andreas.Buser AT Basler DOT ch

Address:
Basler Versicherungsgesellschaft
Andreas Buser
Abt. Informatik
Aeschengraben 21
4002 Basel
Switzerland



                    Shelby Beach
                    <Shelby.Beach@TEA        An:     ADSM-L AT VM.MARIST DOT EDU
                    LE.CA.GOV>               Kopie:
                    Gesendet von:            Thema:  SQL Query Against the 
VOLUMEUSAGE Table
                    "ADSM: Dist Stor
                    Manager"
                    <[email protected]
                    .EDU>


                    29.09.99 01:30
                    Bitte antworten
                    an "ADSM: Dist
                    Stor Manager"





I was wondering if anyone has tried anything like this:

select node_name from volumeusage where volume_name='693099'

My question is does this just take a long time or is something broken ?
When I
sent this to my ADSM server on OS/390,
ADSM's CPU utilization went to 100% and essentially everything else came to
a
screeching halt. Any thoughts ?

Thanks.
Shelby