|
5.0 Feedback
< Previous Next >
Re: Sequence number reset / usage of tag 141
Dennis Wiatzka / OMX <>
13 Mar 2008 2:42PM ETSequence Number Reset at Logon is only to ever be used in situations of 24 hour connectivity. The two parties (server and client) must agree upon a time during the 24 hour period at which time one side (again, agreed upon in advance which side will initiate) will initiate the resetting of sequence numbers by sending a Logon message with tag 141 = Y. Prior to sending the reset Logon, the initiator must check for unsent messages by sending a Test Request which should cause any unsent messages.
From the spec:
"One side will initiate the process by sending a TestRequest and wait for a Heartbeat in response to ensure of no sequence number gaps. Once the Heartbeat has been received, the initiator should send a Logon with ResetSeqNumFlag set to Y and with MsgSeqNum of 1. The acceptor should respond with a Logon with ResetSeqNumFlag set to Y and with MsgSeqNum of 1. At this point new messages from either side should continue with MsgSeqNum of 2. It should be noted that once the initiator sends the Logon with the ResetSeqNumFlag set, the acceptor must obey this request and the message with the last sequence number transmitted “yesterday” may no longer be available."
> Dear all: This is related to tag 141 available in 4.3. If the client
> drives sequence number reset, connects as well as logs on using sequence
> number 1 | tag 141=Y, the server will reset sequence numbers and will
> replu with logon | tag 141=Y.
>
> If the server drives sequence number reset, is the only option (A) for
> the server to wait for the client to connect and log on with next
> sequence number (tag 141=N or absent), exchange the heart beats and send
> another logon seq. num 1 | tag 141=Y and wait for response from client?
>
> Could the server, (B) replay to logon seq num = next | tag 141=N or
> absent with logon seq num 1 | tag 141=Y. This would reduce time it takes
> for resynch and sequence number reset, if driven by server.
>
> It seems option A follows FIX specs verbatim. Question 1) Is option
> B a valid option? 2) If Yes, then the server should not generate
> resend requests as result of client's first logon (prior to sequence
> number reset).
> 3) If Yes, the client then would need to send another logon with
> sequence number 1 | tag 141=Y
>
> Please confirm the understanding.
Re: Sequence number reset / usage of tag 141
Dennis Wiatzka / OMX 13 Mar 2008 2:42PM ET
|
