[This message was posted by Mahesh Kumaraguru of <[email protected]> to the "Transport Independence Framework" discussion forum at http://fixprotocol.org/discuss/49. You can reply to it on-line at http://fixprotocol.org/discuss/read/90566451 - PLEASE DO NOT REPLY BY MAIL.]
In FIX_Transport_1.1.pdf page 38 of 66 (March 2008) defines a Garbled message as [start quote] BeginString (tag #8) is not the first tag in a message or is not of the format 8=FIXT.n.m. BodyLength (tag #9) is not the second tag in a message or does not contain the correct byte count. MsgType (tag #35) is not the third tag in a message. Checksum (tag #10) is not the last tag or contains an incorrect value. [End quote] The following additions should be made to the above list of definitions of a garbled message SenderCompID (tag #49) is not the fourth tag in a message. TargetCompID (tag #56) is not the fifth tag in a message. ApplVerID (tag #1128) if present in message is not the sixth tag in a message. Non numeric Tag is present in the message, for example ^X=123^ (Request :- If this is not the correct forum for discussing FIX_Transport_1.1.pdf, please let me know the correct forum) Regards, K. Mahesh [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
