Bruce writes:

> Glenn Cole writes:
>
>  >what remains the "best" use for KSAM?
>
>  I use it when I need to set up a "temporary" data base as a process step
>  within a larger task. Since they can be created dynamically with a single
>  intrinsic call, and they can live in a job-temporary domain, they fill
>  this role much better than IMAGE.

Roger that. We do exactly the same thing, except we tend to keep our data --
occasionally for long periods of time -- thus our KSAM datasets are kept in
the permanent domain. Moreover, we index the first 16 dataitems, regardless
of their type, so that we can get truly high speed retrievals.

KSAM has a lot of advantages over IMAGE because of its very flexible
structure. Security/long-term reliability isn't one of them. But when you
need to build auxiliary datasets off to the side, on the fly, it fills a role
that you simply can't accomplish with IMAGE.

Wirt Atmar