The XA reconnect CICS transaction, CRCN, has been replaced by XA reconnect code executed in a Service Execution Process (SEP). The XA reconnect processing is invoked before each new transaction by executing an xa-ping to test and verify the connection to the target resource manager. If the ping fails, the XA reconnect code attempts an XA reconnect using the XA APIs.
To prevent the reconnect attempts:
Alternatively:
XA reconnect can operate in single or multiple reconnect modes depending on the configuration of the ES_XA_RECONNECT and the ES_XA_%xaname%_OPTIONS environment variables: