Paul continues the thread:

> In addition it seems that the error is caused only by the
> fact that the 'FORCED' option is being used.  I got the
> same error when I issued the 'dropindex' command against
> my test database with 'interleaved' sets even though ALL
> the B-tree files were present.

Yup;  that is what I would expect.   Remember:

(1)  This is an undocumented feature.
(2)  I expect "FORCED" is a good description of what happens:
      It's telling DBUTIL to try and complete this action for *every*
      specified dataset regardless of whether the file exists or not;
      and regardless of file type (MASTER or DETAIL).
(3)  Unless you do something that is really not legitimate like I
      did, the "FORCED" qualifier should never be necessary.

> This goes against what many of us have practiced for years
> and even against what is published in the Image manual.

Do you mean intermixed MASTERs and DETAILs (I think) ??..
Or that the undocumented "FORCED" feature should be
smarter and skip over DETAILs (maybe) ??....

:-)
Ken Sletten