[This message was posted by Mikael Brannstrom of Nordic Growth Market <mikael.brannst...@ngm.se> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/1a1c5d9b - PLEASE DO NOT REPLY BY MAIL.]
Hi Mahesh, Revision 0.4 of the logon extension contains proposed changes to the FIXT 1.1 documentation. It seems that revision 0.2 is the one that is posted. See my answers below. > 1) If the incoming message has a sequence number less than expected and the > PossDupFlag is not set, it indicates a serious error. It is strongly > recommended that the session be terminated and manual intervention be > initiated. As of today, manual intervention is the only way. The proposal is to have _automatic_ recovery as an option, which would work as follows: terminate the connection and Logon again with ResetSeqNumFlag=Y. After a Logon with reset it is recommended that snapshots are requested for any state that need to be in sync between the parties, e.g. Order Mass Status Request for orders, and so on. > 2) Sending a Logon without a Logout will fall under the category of second > connection attempt while a valid FIX session is already underway I cannot see how the proposal contradicts this. The Logon with ResetSeqNumFlag=Y is _never_ sent while logged in, it is only sent when initiating a new FIX connection. In that sense it is the 24-hour-connectivity Logon with reset that is odd, since it is sent when already logged in. > Since Business objects at the counterparty's trading application would stay > alive based on other criteria, for example : An Order with TIF=GTC stays > alive thru multiple logouts and logons, an order with TIF=DAY would stay > alive thru multiple logouts and logons thru the day. > > FIX Engine Session behaviours would have to be turned upside down to > accommodate this propasal. Business level objects can always be recovered by requesting snapshots, e.g. Order Mass Status Request, Trade Capture Report Request, Market Data Request, Security List Request etc. You only need to remember _if_ you reset, in which case snapshots are needed as well. In the proposed documentation changes in revision 0.4, it says that it is recommended to request snapshots whenever logon with reset has been made. I also pulled in you comment from http://fixprotocol.org/discuss/read/519fd8a9: > NGM's Logon reset MsgSeqNum to 1 using ResetSeqNumFlag = Y can occur anytime, > present FIX Logon reset happens only at prefixed bilaterally agreed uopn time. The "NGM Logon reset" can only occur at Logon when initiating a FIX connection. It is just like a normal Logon but with the ResetSeqNumFlag=Y. I hope my answers straightened things out. Regards Mikael Brännström, NGM [You can unsubscribe from this discussion group by sending a message to mailto:unsubscribe+100932...@fixprotocol.org] -- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to fix-proto...@googlegroups.com. To unsubscribe from this group, send email to fix-protocol+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
