More than 1 transaction in a Oscript module

I would like to know if it is possible to control more than 1 transaction in a Oscript module.

In the following sample code, can I commit the first update (Column_A in Table_A) and rollback the second update (Column_B in Table_B) in one Oscript module ?

Boolean CommitFlg
String strSQL

/* Transaction 1 */
prgCtxOfAdmin.fDbConnect.StartTrans()
strSQL = "Update A Set Column_A = 1 FROM Table_A AS A WHERE DataID = :A1"
dynResult = CAPI.Exec( prgCtxOfAdmin.fDbConnect.fConnection, strSQL,DataID )
CommitFlg = True
prgCtxOfAdmin.fDbConnect.EndTrans( CommitFlg )

/* Transaction 2 */
prgCtxOfAdmin.fDbConnect.StartTrans()
strSQL = "Update B Set Column_B = 1 FROM Table_B AS B WHERE DataID = :A1"
dynResult = CAPI.Exec( prgCtxOfAdmin.fDbConnect.fConnection, strSQL,DataID )
CommitFlg = False
prgCtxOfAdmin.fDbConnect.EndTrans( CommitFlg )

Find more posts tagged with

Comments

Hiroomi_Nakazawa

The reason I asked above question is,

it only worked in the following 2 cases

1) using Builder in a debug mode

2) using livelink AP serives with thread log and SQL log on

But it did not work in the following 2 cases ( Rollback did not work and all transactions have been comitted)

3) using Builder in normal mode (no debug)

4) using livelink AP serives without thread log and SQL log on

HFCDev

It is most likely that you are experiencing a race condition. With Builder in debug mode, you slow down the processing so that one transaction can complete before the other begins. Turning off debuging speeds up the process. I don't quite understand your example and what you are trying to accomplish. It has also occurred to me that you may have started a transaction outside your code, that is, you may have a nested transaction (i.e. a start Trans before your code, and an End Trans after) which may explain this behaviour.

-Hugh Ferguson