Yes, Roy can split rabbits with the best of them.  You should hear him in
French or better yet, Flemish.

However, I can help but wonder how many people actually use HWMPUT in
reality.  This is one of those later additions to IMAGE that slipped in
almost unannounced.  If you do use HWMPUT, what benefit do you think it
brought to you?  I can think of a few reasons to use it, but I would love to
hear from actual users with actual production reasons.

Denys

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of F. Alfredo Rego
Sent: Friday, November 24, 2006 7:06 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Adager question

At 10:45 PM +0000 11/24/06, Roy Brown wrote:

>In message <p0624080bc18c210fc53d@[192.168.2.64]>, F. Alfredo Rego
<[log in to unmask]> writes

...

>>Adager will go the extra mile and I will cruise DOWN the dataset,
>>starting at the HWM, to see if all the entries in the FreeEntry List
>>"AT and ABOVE" your suggested capacity are free.  If they are, Adager
>>will quickly rebuild the FreeEntry list and I will place the HWM at
>>your suggested capacity.  Actually, there is no reason to stop there
>>and I can keep cruising down (below your suggested capacity) until I
>>hit a "defined" entry, which will in turn define the new HWM.  From
>>my perspective, there is no reason to have free entries immediately
>>below the HWM (if you have not explicitly enabled HWMPUT via DBUTIL).

...

>It seems churlish to quibble in the face of such virtuoso generosity, but
may I offer a few gentle suggestions for amendments to your spec?

...

>If someone has set HWMPUT, and then reduces the dataset capacity to the
HWM, they might as well not have HWMPUT set. For that dataset at least, all
the free capacity, if any, will be in the FreeEntry List, so Image will be
forced to behave exactly as it would if HWMPUT were not set...

Point well taken, Roy.  Thank you very much.

The discriminant, all along, was this parenthetical note:
         (if you have not explicitly enabled HWMPUT via DBUTIL).

I didn't want to be TOO redundant mentioning this discriminant all over
the text, and perhaps I left a few instances in an implicit mode.

Thanks to your comments, I have made a note to issue EXPLICIT messages
in all contexts related to REDUCING the capacity of datasets that
use the concept of a HighWater Mark (all details as well as MDX masters)
within databases that have HWMPUT enabled.

I have always admired Roy's accurate and precise use of (any) language.


  _______________
 |               |
 |               |
 |            r  |  Alfredo                  http://www.adager.com

 |          e    |                            
 |        g      |  F. Alfredo Rego                   
 |      a        |  Manager, R & D Labs           
 |    d          |  Adager Corporation
 |  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
 |               |
 |_______________|

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *