I work for an unamed software company supporting programs written on
HP3000.  We have never utilized HP logging correctly from what I have
heard.  We have been noticing that we are getting alot of calls
regarding the TRANSACTION MANAGER.  Actual message reads:
STALLED TRANSACTIONS.....log is full....or something to that nature.
Because we use a Third Party Index in addition to our Image indexes
the normal practice would be either one of two things:

a.) Turn off Transaction Manager for the OMNIDEX keys and re-index
them.

b.) RELOAD the affected datasets and then re-index them leaving XM on.

Is there a way to avoid these errors, and is there a better way to
deal with thm?

-emania