Is there a way to limit a CICS transaction execute?

[BobP]

Hi,

Is there a way to limit the time a CICS transaction can execute in CICS? If yes, could you please guide how to do that?

[BobP]

I'll try to explain more. We've CICS Test regions. These test regions can execute some of the transaction using Tibco and APIs and we don't have any control on that. These 'interfaces' don't have the visibility of mainframe transaction they just wait for the "result set". If they don't get the result, they just initiate the API again and that brings many of the very long executing translocation in our CICS regions and they use lot of CPU or many a times some times abended instances of the transactions lies out there and SYSVIEW shows problem. Is there a way to avoid such situation?