At 2:08 PM +0000 11/22/06, [log in to unmask] wrote:

>Anyone know why when I try to change a dataset capacity in ADAGER it's telling me that the minimum acceptable capacity is higher than I'm trying to set it at?
>Present : 9763397
>New ?5500000
>The minimum acceptable capacity is 9763396

1) Mea culpa
   --------- 

If you are dealing with a DETAIL dataset (or a MASTER
dataset with dynamic expansion -- MDX), I'll change this unhelpful
Adager message to something like this:

  The minimum acceptable capacity is 9763396 (the HighWater Mark),
  even though the number of entries is xyzz.

  The HighWater Mark ("HWM") is equal to the highest entry number
  since the creation of this dataset, or since its last repack, or
  since its last erasure.  If you have deleted entries from this
  dataset, they have been incorporated into the FreeEntry List,
  which IMAGE uses to "recycle" entries before increasing the HWM
  (unless you have explicitly enabled HWMPUT via DBUTIL).

  If the number of entries is less than the HWM, one way to lower
  the HWM down to the number of entries is to repack (reorganize)
  the dataset.


2) Even better 
   -----------

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).


So:
--

Thank you for bringing these issues to my attention.  As a direct
result of your question, I will make Adager's message much more
explicit, precise, and helpful.  At the same time, to flex my
programming muscles, I will add more intelligence to Adager's
approach and I will REDUCE the HighWater Mark to its lowest
possible value WITHOUT having to repack the dataset (if you have
not explicitly enabled HWMPUT via DBUTIL).



Of course, I should have done this 28 years ago (but then, again,
HP implemented HWMPUT more recently than 28 years ago).

Better late than never,

  _______________
 |               |
 |               |
 |            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 *