It would be a major step forward if the stall process returned an ERROR rather than ABORTING the calling process!!!

<Raw nerve showing>

Ken Vickers

LINKWAY Development and Support
__________________________________
Computing Solutions Limited
International Toll Free 00 800 00 3000 00
Tel. +44 1905 794400
Fax. +44 1905 794464
mailto:[log in to unmask]
http://www.csllink.com
__________________________________


Vikram after Leonard:
Hello,

The stalled transaction error is due to the fact that, cureently there is a limitation
on the maximum size allowed for a transaction, which is 4MB. This in turn is dependent
on the size of the largest object that can be created. Another limitation is the
Transaction Manager (XM) Log size, which is a maximum of 64 MB currently. Since, IAMAGE
uses XM, along with other MPE subsystems, the combined logsize at any instance cannot
exceed the half log size (taking into account rollback requirements). When any of these
limits were reached, it used to abort, and leave the database in a corrupted state.
Sometimes back, a patch was provided, to ensure transaction rollback, leave the DB in a
consistent state before process abort. There is a SIGIMAGE Enhancement request for this,
and lab is currently working on this to provide a solution. (An article on this is
coming in HP3000 Advisor).

<snip>