Roy relates the royally right stuff when he writes:

> However, if I were you, I wouldn't start from here :-)
>
>  It is seldom a good idea to create Image Master datasets, except maybe
>  for codes and other unique non-linked items.
>
>  Three reasons: (i) the sort of thing you have found above; (ii) you have
>  to lock the entire dataset when adding or deleting entries - you can't
>  use a record level lock; (iii) you may have to deal with migrating
>  secondaries[1].
>
>  You will not find this advice in the Image manual :-(
>
>  Instead, create your datasets as Detail datasets and use Automatic
>  Masters to hold the ends of your key chains (so to speak).

I'll even go further than Roy. I've long ago come to the conclusion that it's
never a good idea to use Manual Masters. Databases, if they are to be
designed for long-term efficiencies and maintainability, should only be
composed of Detail Datasets with Automatic Masters.

Wirt Atmar

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *