How can I use RawData field..?

, ,
1

Imported from previous forum

2

Can anyone had idea that how to use RawData…?

Thanks… In Advance…

3

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…

4

Hi Mahesh,
Actually I want to send some string which may be used in session creation in logon message.

But I am unable to put RawData in any category…
Some doc says it’s part of Header while some doc says it’s part of Message Body.
Moreover is it only used in FIX 4.2?

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…

5

Hi Kalyan,

RawData and RawDataLength have been part of FIX message body since FIX.4.0 (Refer page 17/67 of FIX40.doc) and continue to be part of body into the latest version (Refer page 21/66 of FIX_Transport_1.1.pdf). I have not checked every version in between and assume that these fields have stayed as part of message body. Can I have the URLs / locations of documents where these fields are mentioned to be part of message body.

Regards,
K. Mahesh

Hi Mahesh,
Actually I want to send some string which may be used in session creation in logon message.

But I am unable to put RawData in any category…
Some doc says it’s part of Header while some doc says it’s part of Message Body.
Moreover is it only used in FIX 4.2?

6

Hi Kalyan,

correction - Can I have the URLs / locations of documents where these fields are mentioned to be part of message header.

Regards,
K. Mahesh

7

Hi Mahesh,

Finally it worked. I am able to send the rawdata now.
Thanks to “www.quickfixj.org” :slight_smile:

Below is the link for your information:
http://www.quickfixj.org/confluence/display/qfj/Implementing+Custom+Logons

Hi Kalyan,

correction - Can I have the URLs / locations of documents where these fields are mentioned to be part of message header.

Regards,
K. Mahesh

8

Kalyan,

Happy to hear that sending RawData finally worked.

I would say that you should consider the FIX specifications @ http://fixprotocol.org/specifications/ as the correct interpretation of FIXProtocol. QuickFIX/J accepting RawData as part of Message Header cannot be taken as correct interpretation / implementation of FIXProtocol.

Regards,
K. Mahesh

Hi Mahesh,

Finally it worked. I am able to send the rawdata now.
Thanks to “www.quickfixj.org” :slight_smile:

Below is the link for your information:
http://www.quickfixj.org/confluence/display/qfj/Implementing+Custom+Logons

Hi Kalyan,

correction - Can I have the URLs / locations of documents where these fields are mentioned to be part of message header.

Regards,
K. Mahesh

9

Hi Mahesh,
what kind of data you want to transmit in the FIX message? If it is the additional fields, that you don’t find in the FIX message and want to use, I recommended to use Custom Fields for that.
And even the use for “Text” in the message body instead of “RawData” is more advisable.

Kapil K Lalwani

Kalyan,

Happy to hear that sending RawData finally worked.

I would say that you should consider the FIX specifications @ http://fixprotocol.org/specifications/ as the correct interpretation of FIXProtocol. QuickFIX/J accepting RawData as part of Message Header cannot be taken as correct interpretation / implementation of FIXProtocol.

Regards,
K. Mahesh

Hi Mahesh,

Finally it worked. I am able to send the rawdata now.
Thanks to “www.quickfixj.org” :slight_smile:

Below is the link for your information:
http://www.quickfixj.org/confluence/display/qfj/Implementing+Custom+Logons

Hi Kalyan,

correction - Can I have the URLs / locations of documents where these fields are mentioned to be part of message header.

Regards,
K. Mahesh