Enterprise Server XA Reconnect

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 execute an xa-ping to test and verify the connection to the target resource manager. If the ping fails, the XA reconnect code will attempt an XA reconnect using the XA APIs.

Note: The XA reconnect mechanism attempts to reconnect to all XA entries marked as "enabled" at the start up of the enterprise server region. [3]

To prevent the reconnect attempts:

Remove the XA manager from the enterprise server region definition.

Alternatively:

Set the XA manager as disabled before starting the enterprise server region.

XA reconnect can operate in single or multiple reconnect modes depending on the configuration of the ES_XA_RECONNECT and ES_XA_%xaname%_OPTIONS environment variables: