Command trigger for every change

fiquebem

We're running TS 6.5.0 on Solaris 9.

Say, do the old-fashioned command triggers have anything to do with the new-fangled TS Events Subsystem? Can these two coexist with impunity?

Anyway, we'd like to store a DCR's content in Oracle whenever the user clicks Save. I know we could use the dreaded FormAPI, but we're already using command triggers here and are thinking of continuing to do so.

So I have a trigger for the "ModifyFSE" event. However, if a DCR was already modified, a DCR Save does not seem to be recognized as a ModifyFSE event. iwevents.log shows nothing in such cases -- we have to Submit the file first and modify it again to see the ModifyFSE event in iwevents.log.

Can I turn on any additional logging in iw.cfg? Currently I have:

log_createfse=on
log_renamefse=on
log_modifyfse=on
log_destroyfse=on

Incidentally, does the OD 6.0.1 DAS rely on any of the old-fashioned event-handling at all? The manual says that the following must be added to iw.cfg:

log_syncdestroy=yes
log_syncrevert=yes
log_renamefse=yes
log_setea=no
log_deleteea=no

I'm wondering if that makes any difference.

Thanks,

S.