>Dave -

>Could you provide a little more clarification on this item.  Specifically, I
>just went to MVS Version 2.1.7, but still see the problem - I have a 20G
>server that shows 3.5GB as the size, and utilization of 130%.  This machne is
>an NT Server.

>1.  Does the client code need to be refreshed as well to pick up the fix

I put out a later append yesterday in which I explained that
Query Filespace has problems related to both the client and server.
If you are using the API, you should only need the server fix.  If you are
using ADSM clients, you will need fixes for both the client and server.

>2.  Is information in the DB correct, or will I need to to have an incremental
>backup run before the data shows correctly?

If you have been using an ADSM client, capacity information in the
database is probably incorrect for filespaces larger than 2 GB.  This
information can be refreshed after the client is fixed.

>3.  Will this also correct the GUI displays that also show less than the full
>size of the drive?

I would rather let someone from Client Development answer this.

>Jerry Lawson

Dave Cannon
ADSM Server Development