Re: Attaching process to existing transaction

Mark van Holsteijn wrote: > > When using Tuxedo and Informix TP/XA you can get > multiple processes to do work within the same > transaction context, while the control of the > transaction is in the hand of the proces that > intiated the transaction. > My guess is there may be reasons that Pete Pkjones0 switches from ESQL/C to stored procedure and then back to ESQL/C again. In this case, I am not sure whether Tuxedo can help. We have simpler cases where we must call stored procedures and then ESQL/C. The simplest solution is to change everything to ESQL/C, if it is possible. If everything is in ESQL/C (or stored procedure), processes X, Y, and Z can all be in a single transaction without using Tuxedo. I am not against Tuxedo. In fact, we are in the process of purchasing Tuxedo. As far as I know the value of Tuxedo is to handle activities outside of database as part of a transaction. However, restrictions on the database side still applies -- in this case, the restriction is from Informix. To be more specific, the restriction is from the "system" command issued by stored procedure. I am firmlly believe that Informix should provide a better means to bridge stored procedure with ESQL/C. Do I misunderstand Tuxedo? Is Informix listening? Chao