Tuxedo as a Transaction Processing Monitor › Retry

Retry

Before transactional behavior was supported, the CA Gen Runtime automatically retried PSteps that failed due to database lockout conditions. Several mechanisms exist to modify the default retry behavior of the runtime.

In a transactional environment, it is important to avoid the possibility of retrying an action that was already committed, so you should ensure that RETRY_LIMIT is set to 0. RETRY_LIMIT may be set in any or all of the following places:

• In the server environmental variable RETRY_LIMIT. (This variable controls all unless you override it.)
• In the tirdrtl.c (default retry limit) exit located in the $IEFH/src directory. (If present, this overrides the environmental variable settings.)
• In the action language. (PStep level control)

Set RETRY_LIMIT to 0 for all transactional processing.