[This message was posted by Mahesh Kumaraguru of <[email protected]> to the "India" discussion forum at http://fixprotocol.org/discuss/54. You can reply to it on-line at http://fixprotocol.org/discuss/read/ee656fa0 - PLEASE DO NOT REPLY BY MAIL.]
RawData (96) must always be preceded by RawDataLength (95) so that the message parser knows where RawData ends and the next field begins. RawData (96) is shown to be present in Email, Logon, News & UserRequest but I do not see any reason why it cannot be used in other message types. Are you trying to send RawData as part of a standard FIX message or you wish to transmit RawData only without any standard FIX body content? Myself, Jim Northey & Russell Curry are already trying to extend non FIX message type 35=n^ to handle RawData http://fixprotocol.org/discuss/read/9fa4da31 You could add your requirements / comments to the above thread. For this example lets say the RawData I wish to transmit is Mahesh & Kalyan are studying FIXProtocol The length of the above String is 40 chars. Now lets construct a FIX message where ^ is SOH delimiter and 9999 is the new Tag to identify content type of non FIX messages 8=FIX.6.0^9=70^35=n^9999=3^95=40^95=Mahesh & Kalyan are studying FIXProtocol^10=123^ (Note that Body length & | Checksum in the message message may be wrong - random numbers out of my head) > Can anyone had idea that how to use RawData..? > > Thanks... In Advance... [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.
