Currently CSY Database lab is considering an enhancement to increase the
transaction size for dynamic t ransactions (ie, transactions with a
structure like DBXBEGIN - DBPUT/ DBDELETE/ DBUPDATE - DBXEND/ DBXUNDO).
And also to give some sort of user control over the transaction. One
feature, which is being planned to implement is that, to issue a warning
to user when transaction size reaches a pre-defined soft limit. once
this warning is issued, users can have two options. Option #1: User is
forced to commit or rollback (DBXEND/ DBXUNDO). Option #2: Don't force
anything, user may chose to rollback/ commit or ignore the message. If
it is ignored, ultimately the transaction size may exceed the maximum
possible value and get a stalled transaction (i.e. compulsory rollback
and process abort). What we are seeking is your prefernce of the above
two options, based on your valuable experince. Your feedback on this
will help the lab in deciding on an implementation strategy and coming
up with the solution.

You may choose to post yor reply to 3000-L or mail privately to
[log in to unmask]

Thanks in advance

Regards,
Vikram
CSY Database Lab