DBGeneral apparently doesn't maintain the DDX increment as an even divisor
of the difference between max and initial capacities.  Adager has a problem
with this during its consistency check because it enforces that rule, and
it will ask you to correct the DDX capacity specs to conform.  We stopped
using DBGeneral for any database transformations some time ago until
Bradmark could fix this, but we also use their Superdex product, and the
index dataset (SI) it creates is DDX-enabled, so we have to fix that set
with Adager whenever we rebuild our Superdex indexes.

Lee Gunter
Regence Blue Cross Blue Shield of Oregon / Regence HMO Oregon

mailto:[log in to unmask]
voice...503-375-4498    fax.....503-375-4401
==========================================================
The opinions expressed, here, are mine and mine alone, and do not
necessarily reflect those of my employer.




From: [log in to unmask] on 12/31/97 09:32 AM

Please respond to [log in to unmask]


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: B trees and Express 3 problems




>I've seen this happen when a third-party tool other than Adager was used
>to expand a master dataset.
>
>If this is the problem, you could try asking Adager for a free demo...
>they recognize and fix this particular problem automatically, I believe.
>
>SS

This appears to be the problem.  We use DBGeneral which apparently, a few
revs. back, didn't maintain some DDX capacity info correctly.  Technical
support (thanks Tim) at Bradmark straightened it out and is sending a new
version (7.2).

Thanks Stan for your timely help!!

Gary


Gary Jackson
Nevada CSOS
(530) 478-6407 - voice
(530) 478-6410 - fax