Jean Huot wrote:
>Note that EOF/FLMIT = 96%.  Is this a candidate for performance
>bottleneck??  If yes, to what % value should EOF/FLIMIT be??

Short answer:  No, KSAM files do not get slower depending on how full the
file might be.

Not quite as short an answer:
Unlike master sets in Image databases, neither NM nor CM KSAM files use a
hashing algorithm to manage the keys; instead, they use a B-tree
mechanism.  The performance implications are quite a bit different.  One of
those differences is that there is no performance loss for KSAM files based
on how full the file becomes.  Rather, it's on how balanced the B-tree is
and how many levels deep the B-tree becomes.  I don't know any simple way
to measure either of those attributes for the keys in a KSAM file.

--
Jeff Woods