On Thursday, March 26, 1998 11:26 PM, emania [SMTP:[log in to unmask]] wrote:
> 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?
>

As I understand the problem, "Stalled Transactions" occurs when you write "too
many" transactions within a single XM transaction.  With TPI, this does not
normally occur unless you are using DBX... for logical transaction integrity.
 If you are not using DBX... calls, you problem have a very large IMAGE record
with several indexes.  If this is the case, about the only workaround is to
remove some of the indexes.

If you are using DBX... calls, you might try to adjust the IMAGE calls, so the
actual XM transaction is smaller.  This is not always possible, since you may
not be able to adjust the definition of a logical transaction.

Generally, XM with IMAGE and TPI works like this with DBX... calls.

DBXBEGIN                A begin transaction record is written to XM.
DBupdate calls  A transaction record for the IMAGE update
(DBPUT,DBDELETE,          is written to XM.  Additionally, since
DBUPDATE)                 you have TPI on the data set, a
                          transaction record is written for each
                          TPI update.
                     (Of course, you probably have *many* IMAGE
                      calls within this DBX transaction)
DBXEND               An end transaction record is written to XM.
(DBUNDO will roll back the transactions in XM to the DBXBEGIN)

If you do not use DBX... calls, a begin transaction record is written just
prior to the IMAGE update transaction, and an end transaction record is written
just after the last TPI transaction.

Hope this helps.

LB