HP3000-L Archives

June 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
B T Vikram Kumar <[log in to unmask]>
Reply To:
B T Vikram Kumar <[log in to unmask]>
Date:
Tue, 20 Jun 2000 08:48:00 +0530
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
Hi Ken,

Are you referring to the process abort after stalled transaction? Or is there
any other program aborts happening?.
To address the former, there is a new DBCONTROL Mode-18. If this call is made
before the start of transaction, when the tranasction grows to about 28 MB in
size, IMAGE will send out a softlimit warning message and inhibits any fresh
put/delete/updates. On receiving the message, application can either commit or
rollback the transaction and proceed. In this way, one can prevent individual
stalled transaction. However, if  there are too many large open transactions and
XM log size has not been increased, all the open transactions will get stalled
transaction message and get rolled back.
If you are referring to any other type of aborts please let me know.

Regards,
Vikram


Kenhp3000-L wrote:

> Hi Vikram
>
> When are you going to stop the program from ABORTING???
>
> UK Ken
>

ATOM RSS1 RSS2