Can we avoid commits to db when testing svcs using ud32

Question

Hi,
I have a test service that does some updates to db without any commits in it.
Even though I don't provide -t parameter when testing the service using ud32,
I noticed that the updates are committed to the db even though the service errors.
Is there any way to use ud32 and avoid these updates.
Thanks
Kishore

Answer 1

Kishore,
When ud32 is invoked with the "-t timeout" option, any error return from tpcall() will cause tpabort() to be called.
Therefore, if the service you are calling is located in a group with OPENINFO and TMSNAME parameters specified, no updates should be made to the database if the service call fails. When an OPENINFO string is specfiied, Tuxedo takes care of opening and closing the database and committing or aborting transactions via the XA interface. This is the preferred way to manage transactions in Tuxedo and is needed if transactions will span multiple databases. When using XA the application should not code any EXEC SQL COMMIT WORK or similar statements on its own.
XA is not the only way to manage transactions in Tuxedo. In a group without OPENINFO specified and without TMS processes, the application takes care of opening and closing the database and managing transactions. Transactions may be committed either via explicit statements in the application or implicitly according to the rules of SQL or whatever other database interface is being used. In this case, a tpbegin(), tpcommit(), or tpabort() done in the Tuxedo client will not have any effect since the database updates are being done outside of a Tuxedo global transaction.
I suspect that the latter case may apply to to your application and this may be why you are seeing database updates even though the service fails.
One option to debug is to
export TMTRACE=*:ulog:dye
before invoking ud32. This will write messages to the userlog showing each ATMI or XA call that was performed in the ud32 client or in the server.
Ed