[This message was posted by Mahesh Kumaraguru of <[email protected]> to the "5.0 SP2 Feedback" discussion forum at http://fixprotocol.org/discuss/121. You can reply to it on-line at http://fixprotocol.org/discuss/read/3fa8bc2b - PLEASE DO NOT REPLY BY MAIL.]
John, This question was raised previously at http://fixprotocol.org/discuss/read/ca82b7da The order (as of now) is BeingString (8) - 1st position BodyLength (9) - 2nd position MsgType (35) - 3rd position SenderCompID (49) - 4th position TargetCompID (56) - 5th position ApplVerID (1128) - must be 6th position if used FIXimate not specifying the positional requirements is already raised at http://fixprotocol.org/discuss/read/e617a96d Regards, K. Mahesh > In the FIXT.1.1 specification it makes reference in the "FIXT Header > Mapping Table" to the fact that SenderCompID is field 4, TargetCompID is > field 5 and ApplVerID is field 6. > > Nowhere else in the specification are these positional field > requirements mentioned. > > Is this just an error in the specification and the field order of these > fields is actually unspecified? > > I notice that FIXimate makes no mention of these fields having > positional requirements. [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 -~----------~----~----~----~------~----~------~--~---
