Gavin Scott wrote:
>
[Lot's of XM guru stuff snipped.]
>
> NM KSAM files are always attached to XM, Image attaches all of the files
> that make up your database to XM for you (and surrounds its own internal
> multi-file updates with XM transactions to guarantee database integrity),
> CM file types (RIO, etc.) cannot be attached to XM, message files cannot
> (unfortunately),

Since we have NM message files, I suppose the decision to not being able
to attach them to XM is rather arbitrary; though I would perfer to "not
attached" as the default behaviour. (room for enhancement...)

>
> Generally once a file is attached to XM, it's not possible to unattach it.

I think a simple STORE/RESTORE will do the trick, even IMAGE and NM KSAM
files are "unattached" after an RESTORE, but get "reattached" on the
first
open of the file(s).
For IMAGE there is the AUTODEFER option in DBUTIL, but that should
REALLY,
REALLy only be used on a DBLOAD (or any similar situation where you can
easily fallback to the previous state, or repeat the batch loading job).

Goetz