Stan Sieler ([log in to unmask]) wrote:
: Another benefit of "SET basename CAPREP = MAX" is that Query's FO SETs and
: FO setname commands would immediately start reporting maximum capacity.
: I should have added:
:    4) QUERY's FO SETS will be unchanged, and continue to use DBINFO mode 202,
:       which is (of course) affected by "SET basename CAPREP = MAX"
:    5) QUERY's FO setname command will be changed, with the addition of
:       one extra line after the "CAPACITY:" line, so that the last few
:       lines of output look like:
:            CAPACITY: 10000             ENTRIES:0
:            MAXIMUM CAPACITY: 111,234,567,890
 
I've already updated Query (for a future to-be-released version) to use
DBINFO 205 (and revert to DBINFO 202 if not available) for the FO command.
Rather than add another line I squished the capacity line a bit to give
 
      CAPACITY: 1015         ENTRIES: 14           MAXIMUM CAPACITY: 1015
 
as an example.  As you can see, if a dataset is not enabled for DDX the
two capacities are the same.  So sometime soon there should be a patch for
Query that will at least show users both values.
 
Is that OK??
 
James (An I/O is a  terrible thing to waste) Overman
HP Support Technology Lab  Roseville, CA