In some cases, S2F38 responds to S2F37 without leaving S2F0. What is the cause?
The reason why the response to S2F37 message is S2F0 (Abort Transaction) message instead of S2F38 occurs when the corresponding message is received while ControlState is Offline.
Other messages are the same.
If an S * F0 response is sent, make sure ControlState is Online