Stephen Bruno <[log in to unmask]> writes:

<snip>
>
> 4    A final batch process was then executed, which performed DBPUTs of
the
> records removed
>      from Step 2 above, back into the dataset.  Again, we would also
anticipate
> that the highwater
>      mark would remain, unchanged, however . . .
>
>      Dataset stats:      Capacity  Entries         Highwater Mark
>                     600,000        201,263         354,071
>
> There was no execution of an Adager Repack or a DBGeneral Re-org or a
complete
> unload/load on
> the dataset, but yet the highwater mark was lowered.  What else could
attribute
> to this and would this
> cause any performance degradation?
>

The behavior you describe is consistent with the HWMPUT feature of Image
which allows you to add entries to your detail datasets at the high-water
mark, rather than re-using the delete space chain. You can see the setting
of this flag in DBUTIL.


>>show opsdb.pred flags
  For database OPSDB.PRED

  Maintenance word is not present.

  Access is enabled.
  Autodefer is disabled.
  Dumping is disabled.
  Rollback recovery is disabled.
  Recovery is disabled.
  ILR is disabled.
  Mustrecover is disabled.
  Logging is disabled.
  Prefetch is disabled.
  Indexing is disabled.
  HWMPUT is disabled.    <<<<<<<<<<<-------------------------HWMPUT setting
  Use of lock table for deadlock detection is enabled.
  Restart is disabled.
  Database last stored on WED, FEB  2, 2000, 11:23 AM.
  Database has not been modified since last store date.
  Shadowing is disabled.
  Use of Dependency SEMaphore(DSEM) is disabled.
  Subsystem access is READ/WRITE.

HTH.

Doug.

Doug Werth                             Beechglen Development Inc.
[log in to unmask]                               Cincinnati, Ohio