No thoughts, just a similar experience for what it's worth: we tried the
same thing, and yes, it does take ages to finish (20 minutes on a system
with hardly any other activity) and it does need an excessive amount of
CPU cycles (as ADSM tends to do on OS/390). Conclusion: nice command,
but don't use it.
And if ADSM is able to halt everything else on OS/390, go talk to the
people responsible for balancing the workload on your system. ADSM, as
it eats up plenty of CPU if you let it, should have a reasonably low
priority. (You can always turn it up if you need to do an emergency
restore.)

Cheers,
Chris
>-----Original Message-----
>From:  Shelby Beach [SMTP:Shelby.Beach AT TEALE.CA DOT GOV]
>Sent:  woensdag 29 september 1999 1:30
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       SQL Query Against the VOLUMEUSAGE Table
>
>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