| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| IIB9: ESQL TransactionMode |
« View previous topic :: View next topic » |
| Author |
Message
|
| akil |
 Posted: Fri Aug 28, 2015 7:09 am Post subject: IIB9: ESQL TransactionMode |
 |
|
Partisan
Joined: 27 May 2014
Posts: 338
Location: Mumbai
|
Hi
Version 9.0.0.2
I've a Compute Node with the Transaction Mode set as Commit, and the dataSource specified as DS1.
In the ESQL code of the compute node, I am referring to a different datasource, DS2. ( INSERT INTO Database.{dataSource}.{schemaName}.MYTABLE. ... )
The transaction mode of the ESQL Insert statement is 'Automatic' & not 'Commit' , which was specified in the Compute Mode.
Once I change the dataSource of the Compute Node to be DS2, then the Transaction Mode of the ESQL statement changes to Commit.
So it seems that the transaction mode property of the compute mode sets it on the dataSource that is specified in the properties, and is not applicable to other dataSources that are used in the ESQL code.
Is this the expected behaviour ?
How can I specify the TransactionMode for dataSources that are used in the ESQL code, given that they are different than the once specified in the Compute node?
_________________
Regards |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Aug 28, 2015 7:23 am Post subject: Re: IIB9: ESQL TransactionMode |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| akil wrote: |
| Is this the expected behaviour ? |
| akil wrote: |
| How can I specify the TransactionMode for dataSources that are used in the ESQL code, given that they are different than the once specified in the Compute node? |
Redesign your logic such that different data sources with different transactional requirements are in different Compute nodes. That's probably a better design practice anyway - clearer and gives a more straightforward roll back path.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| akil |
| Posted: Fri Aug 28, 2015 7:30 am Post subject: |
|
|
Partisan
Joined: 27 May 2014
Posts: 338
Location: Mumbai
|
Hi
That's what we usually do, what happened in this case was that during the BAR applyoverride command, someone made a mistake, and the dataSource property of the computeNode got out of sync with the dataSource that was specified in the ESQL ..
It took sometime to figure out that this was the cause .. hence the question ..
_________________
Regards |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
