If the client connection is actively in the middle of communications with the remote server, or in the middle of a transaction (or a nested transaction), the thread notifies the client that the connection has been lost by issuing a deadlock message. For example:
Msg 1205, Level 13, State 0 Server 'OpenSwitch' Your command (process id #8) was deadlocked with another process and has been chosen as deadlock victim. Re-run your command.
The message is used by an Adaptive Server to indicate that the current transaction has been aborted due to a resource contention issue, and should be restarted.
An Adaptive Server issues a return status of -3 to all
client applications running a stored procedure when a deadlock message
is issued. Because OpenSwitch cannot detect when a client is running
a stored procedure from within a language batch, the return status
of -3 is returned only to those clients that issued the RPC request
through the Open Client RPC mechanism.
