I believe you'll find the select statement for doing that to be rather nasty
(i.e. takes a tremendous amount of time to the point of being impractical).
I don't recall the select statement but a quicker way to determine size of
active files is to do an "export node * filedata=allactive preview=yes" and
extract the relevant value from the activity log.

e.g. on a tsm server with 4 client nodes, roughly 153,000 files and only 4GB
of data it took 12 minutes to complete.. you can see the output below:

06/13/02   20:52:57  ANR0609I EXPORT NODE started as process 2.

06/13/02   21:05:07  ANR0986I Process 2 for EXPORT NODE running in the
                      BACKGROUND processed 155674 items for a total of
                      3,760,983,998 bytes with a completion state of SUCCESS
at
                      21:05:07.


tsm: SERVER1>q occ

Node Name  Type Filespace   FSID Storage    Number of  Physical   Logical
                Name             Pool Name      Files     Space     Space
                                                       Occupied  Occupied
                                                           (MB)      (MB)
---------- ---- ---------- ----- ---------- --------- --------- ---------
---------
DB2        Bkup /DS50          6 BACKUPPOOL         2     24.04     DB2        
Bkup /DS50          6 BACKUPPOOL         2     24.04     24.04
GWICHMAN.- Bkup \\gwichma-     1 BACKUPPOOL    27,322  1,230.12  1,230.12
 NT              n1\c$
GWICHMAN.- Bkup \\gwichma-     2 BACKUPPOOL    10,847    662.53    662.53
 NT              n1\d$
GWICHMAN.- Bkup /              1 BACKUPPOOL   115,576  2,129.38  2,129.38
 RH73
GWICHMAN.- Bkup /boot          2 BACKUPPOOL        34      9.12      9.12
 RH73

tsm: SERVER1>



Regards,

Gerald Wichmann
Senior Systems Development Engineer
Zantaz, Inc.
925.598.3099 (w)