About logon

, ,
1

Imported from previous forum

2

Darl all

  i want to kown when i went to logon fix what should i do 
  the first i send msgtype =A (logon message) 
  then i received msgtype = 5 and next msgtype = A and then     
  msgtype =2
  
  i am confoused   
  i just want to kown how to logon fix step by step
3

[ original email was from Noah Zucker - noah.zucker@transacttools.net ]
> i want to kown when i went to logon fix what should i do the first

i send msgtype =A (logon message) then i received msgtype = 5 and
next msgtype = A and then msgtype =2

i am confoused i just want to kown how to logon fix step by step

During the logon process, FIX engines implementations will (among other things) check the sequence number of the first message they receive from a particular counterparty. Keeping incoming and outgoing sequence numbers in synch is a key part of the FIX protocol that protects data integrity.

MsgType=2 is a “ResendRequest,” which usually indicates that your counterparty Fix Engine received a higher sequence number than expected. In order to continue the session, your application should respond to the ResendRequest by re-sending the messages specified by the range of the ResendRequest’s “BeginSeqNo” (tag 7) and “EndSeqNo” (tag 16) fields.

Note that FIX protocol allows you choose exactly which messages you re-send, i.e. you may not want to resend HeartBeat (msgtype=0) or Order messages (msgtype=D, which may be outdated). When skipping over these messages, you can send instead a “SequenceReset” message (msgtype=4) instead. Finally, re-sent application messages should have their “PossDupFlag” (tag 43) set to “Y”

After you have filled the “gap” specified by the ResendRequest, you should be able to proceed with normal messaging. You should also be sure to read the FIX 4.0 Specification (available for download on this web site - http://fixprotocol.org/specifications/ ) and search through this forum for more information.

Regards,

Noah Zucker
TransactTools - New York