| || |
Tuxedo non-API calls
We were using Tuxedo just fine until the development team decided to bypass the Clarify/Tuxedo API and invoke Tuxedo directly. Now these calls fail when the recorder is active with Tuxedo, although they work fine normally.
If we switch to Winsock, the transactions work - however, trying to decipher all the bin calls isn't working too well. There's also the problem of the return data not being displayed in the script, so capture and customization is also a problem.
Is there a middle ground here, or some configuration setting we're missing?
Re: Tuxedo non-API calls
If you're not using the API then I guess that you are using TxRPC rather than ATMI. Is that right? I think that Performer just supports ATMI, so you may be out of luck there - best to check with Segue...