[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/61d03b25 - PLEASE DO NOT REPLY BY MAIL.]
Lisa, I misunderstood your post that errata was for ApplVerID (1128) only and not for SenderCompID (49) and TargetCompID (56) which I assumed were already included in the extended tag ordering. Thanks for clarifying. Regards, K. Mahesh > Mahesh, > > My post you referenced confirmed that we were discussing it and if it > was ratified it would have been as noted in that post and published as > an errata. > > That said, even though at the time we were close to agreement (thus the > post prior to the ratification), but there was some last minute push > back - strong enough push back that the errata was never ratified by > the GTC Gov. > > Lisa > > > > Jim, > > > > I thought the order given in FIXT Header Mapping Table on Page 31 of > > 66 is correct. This was confirmed by Lisa Taikitsadaporn of Brook Path > > Partners at > > > > http://fixprotocol.org/discuss/read/090515da > > > > Regards, > > K. Mahesh > > > > > Mahesh, I don't believe that we reached this consensus on FIXT.1.1 > > > in terms of extending the tag order to SenderCompID, TargetCompID > > > and ApplVerID. There was considerable push back. > > > > > > > > > > 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.
