A deadlock occurs when two or more transactions are in a simultaneous
wait state and each needs data that is held and locked by the other.
When a deadlock is encountered, the TurboIMAGE/XL intrinsic
DBLOCK returns an error to IMAGE/SQL.
IMAGE/SQL then aborts the IMAGE/SQL transaction that caused the deadlock.
Transaction priorities are not considered in determining which
transaction is aborted -- the IMAGE/SQL transaction that caused the deadlock
is aborted.
To avoid a deadlock situation during a connection, set the MAXIMUM TIMEOUT and
DEFAULT TIMEOUT.
You can set the DEFAULT and MAXIMUM TIMEOUT during the
START DBE NEW or change the value using SQLUtil. If
you do not set the timeout value, the default is unlimited time.
