Chris writes:
...
> It appears that if the dataset is not enabled for ddx, then the value
> returned in 'maximum capacity' for a call to dbinfo205 returns a '0'. Maybe
 
 
Personally, I think that's a bug, and have proposed that it be fixed.
 
 
How does this sound as a 202/205 solution:
 
   1) DBUTIL has a "SET basename CAPREP = <MAXimum | CURrent>" command.
 
      If MAXimum is specified, then DBINFO mode 202 returns the maximum
      capacity (which is, of course, the current capacity if the dataset
      doesn't have DDX or if it has already been expanded to the max)
 
      If CURrent is specified, then DBINFO mode 202 acts like it does today,
      returning the current capacity (ignoring DDX).
 
   2) DBINFO mode 202 would check the CAPREP flag, and report maximum
      capacity if the flag indicated it should, otherwise current capacity.
 
   3) THE DEFAULT MODE FOR THE FLAG IS "CAPREP = MAX"
 
In other words, as soon as the code is installed on your machine, 202
immediately starts reporting max capacity.  Why?  The "call avoidance"
strategy" principle: it solves the 202/205 problem for the majority of
the users correctly.
 
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html