Setting the UTM_ABORT_WITH_EXCEPTION environment variable causes the following:
A core is created on Unix and Linux systems when an application crashes
The debugger is activated when this happens on Windows systems.
It is recommended that you only set this environment variable when the start parameter STXIT contains the value OFF.
Default: the environment variable is not set.
CAUTION!
The following applies for transactions which have already completed the first phase of the "two-phase commit", i.e. are in the "prepare-to-commit" status: If you have specified STXIT=OFF, then no transactions will be rolled back when an error occurs.A lock will remain until the next warm start of the application.The transaction is then handled by the UTM recovery in conjunction with the DB system.In other words, depending on the original progress of the joint transaction, this transaction is either rolled back in a coordinated manner in a warm start or successfully completed.Transactions which are not yet in the termination phase are generally automatically rolled back by the DB system (e.g. Oracle) if openUTM crashes.