This error is thrown out when the transaction log becomes full. Image
transactions are covered by transaction manager (XM). All the open
transactions are logged by XM on a log file. Currently, XM supports a single
transaction of size can be upto 4 MB. Also there is a definite limit for the
XM log. When a single transaction exceeeds 4 MB or when the XM log become full
XM, informs IMAGE accordingly. IMAGE will rollback all the open transactions
which is the best option to do at this point, and abort the process (in this
case ISQL), after showing the stalled transaction message.

However, with the next release of MPE/iX, there are better options to handle
such situations.

Regards,
Vikram

Russell Bevers wrote:

> We received the following error when attempting to perform a large-scale
> update to an IMAGE/SQL database.
>
> Could find nothing about transaction accumulated log data threshold in any
> of our ALLBASE/SQL books.  Can this be adjusted?  If so, how?
>
> Better yet why no DBERR?
>
> **** STALLED TRANSACTION: EXCEEDED ACCUMULATED LOG DATA THRESHOLD
> ABORT: ISQL.PUB.SYS
> NM SYS   a.00a88288 dbg_abort_trace+$24
> NM PUB   171.0041c2f0 m_ma:marspa+$4dc
> NM PROG  611.0005fc54 PROGRAM+$4344
> Program terminated in an error state. (CIERR 976)
>
> Thanks in advance for any help.
>
> -Russell