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 20GB
server that shows 3.5GB as the size, and utilization of 130%.  This machine is
an NT Server.

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

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

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

Jerry Lawson


________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: query filespace
06-24-96 12:53 PM

>One thing to be careful of with the query filespace command:
>
>        it only handles filespaces which are smaller than 2 GB!
>
>
>All file spaces which are over 2 GB in size are reported as 2GB capacity
>I have this problem on our Auspex Client which has serveral filespaces
>which are over 2GB. Everything backs up ok, but the "q fi" numbers are
>not even close.
>
>I'm running the 2.1.7 server on AIX box - I am not sure if this happens
>on all servers.

Clarification of this problem:

To the best of my knowledge, this problem occurs only for filespaces
whose capacity is greater than or equal to 4 GB.  For these filespaces,
Query Filespace displays capacity values that are 4 GB smaller
than the actual value.  For example, if the actual filespace size is
4,300,498,944 bytes, Query Filespace would display a value of
5.3 MB (4,300,498,944 - 4,294,967,296). Values for % utilization
will also be incorrect for such filespaces.

This problem existed on all server platforms and releases and has been
fixed for all servers.  As with any fix, the availability will vary
by platform and release.

Dave Cannon
ADSM Server Development