User Defined Transaction in Logical Data Service

Question

Hi
I have few physical data services created from database store procedures. I've corresponding logical services for each of the physical data services.
Now I've created a logical data service that calls 2 store procedures & trying to update this 2 store procs in a single transaction.
Also I dont have a read operation in my logical data services. In this case both store proc. should take part in a single transaction & should commit or rollback as per success/failure.
I tried testing this scenario & it fails. ALDSP was able to update first store proc. but there was an error in second store proc. so it should have rollback the entire transaction.
Is there any way that we can have user defined transaction in logical data service?
My Scenario:
InsertData(RequestA,RequestB) as response
res1 := call First Store Proc (RequestA) ;
res2 := call Second Store Proc (RequestB);
response := res1 + res2
So my question was is it possible to define user transaction before making calls & have commit/rollback define around it.
Apprecaite for your help!
Thanks
Pash

Answer 1

I have assumed that you realize you need XA drivers for this. What is the exception you see? Something about "mixed outcome"?
But in the case of store procedure, we cant drag & drop physical ds into logical ds. Why?Since your stored procedure updates, it should be defined in the physical ds as a "procedure" not a "function" - it sounds like it is. (procedure means it will update, function means it will not - not that it is a "stored procedure"). Because it updates it cannot be called by an xquery function because xquery is by definition read-only. It can only be called directly from the client, or from another procedure (which is XQSE, not Xquery). If you created a logical ds with a "procedure" - you could drop your procedure into that.
created a new library procedure in which i am calling 2 physical ds assuming it will be executed in a single transaction. But it does not. Please verify.
But it does not. Please verify.I won't verify it because it is not correct. It should be treated as though it is one transaction. And barring the bugs with JNDI/data source names and multi-data sources, I do not know how how it would not be. So either there is a misunderstanding or a new bug.
Either way you need to open a case with customer support to resolve this. When you open your case, the more information you provide them with (i.e the smallest possible dataspace that will reproduce the problem along with DML to create the stored procedures and the tables that they use, and also any/all exceptions/stack traces and server logs).
- Mike
ps. there are no means to explicitly create a transaction in ODSI.