[This message was posted by Mahesh Kumaraguru of <[email protected]> to the "4.4 Changes" discussion forum at http://fixprotocol.org/discuss/17. You can reply to it on-line at http://fixprotocol.org/discuss/read/b909ef55 - PLEASE DO NOT REPLY BY MAIL.]
Hanno, John, As of FIX.5.0, the following Standard Header fields must be ordered as: BeingString (8) - 1st position (Mandatory) BodyLength (9) - 2nd position (Mandatory) MessageType (35) - 3rd position (Mandatory) SenderCompID(49) - 4th position (Mandatory) TargetCompID(56) - 5th position (Mandatory) ApplVerID (1128) - must be 6th position if used You are right regarding repeating groups and Length fields. But still my question is if the following message is received 8=FIX.4.4^9=123^35=D^55=MAX^48=ABCD12345678^22=1^11=98765^54=1^60=20090305-11:02:03^49=MAHESH^34=123^38=100^52=20090305-11:03:04^40=1^56=FPL^10=123^ Would it be treated as a malformed FIX.4.4 message because the header tags (49, 34, 56, 52) are intermixed with body tags? I fully agree "A programmer has to come up with some sequence so why not just take the standard one." 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 -~----------~----~----~----~------~----~------~--~---
