There have been a several posts regarding the Query Filespace command.
Here's one from early December.  I believe that someone from client
development posted something regarding the client fix, but I don't recall
the answer.

 1. At one time, the Query Filespace command did not correctly display
    information on filespaces larger than 4GB.  This was fixed about
    six months ago.  The server level with the fix will vary by platform
    and release.  For the Version 2 MVS and AIX servers, the fix came out
    in server level 9.
 2. There is also a problem where the ADSM clients do not send correct
    information to the server for large filespaces (I believe this problem
    occurs with filespaces larger than 2 GB).  I do not know whether this
    problem has been fixed.  Perhaps someone from client development can
    provide an answer.

If you are using the API, all you need is the server fix.  If you
use an ADSM client you will need fixes for both the client and server.

Dave Cannon
ADSM Development
------------------------------- Referenced Note ---------------------------
     OK, here is the deal... I do a 'q file sunbox' and of the 44GB of 22,
     OK, here is the deal... I do a 'q file sunbox' and of the 44GB of 22,
     concat'ed 4GB disks (mirrored) I only get back roughly the file space
     for ONE disk....

     when I do a 'q occ sunbox' I get roughly the 35GB of files that's out
     on the disk(s)....

     Most of our scientific unix users are having cows because of this....

     have I missed something on this list already about this...?

     any info would be GREATLY appreciated...

     later
          Dwight
                many thanks in advance
                                      Cook