|
4.3 Changes
< Previous Next >
Re: Tag order
John Prewett / Lava Trading
6 May 2005 11:10AM ET> I have a beginners question: Have any of you ever heard about Tag 96(Password) having to come immediately tag 95(RawDataLength)during the logon message (35=A) or you will get a reject?
>
> Thanks
Hi Josh,
I recommend reading the specification documentation for the specific version of FIX you are interested in. In this case the FIX.4.3 documentation at the beginning of volume 1 lists the various data types including a description of the data type "data" as follows:
=========================
* data: Raw data with no format or content restrictions. Data fields are always immediately preceded by a length field. The length field should specify the number of bytes of the value of the data field (up to but not including the terminating SOH). Caution: the value of one of these fields may contain the delimiter (SOH) character. Note that the value specified for this field should be followed by the delimiter (SOH) character as all fields are terminated with an “SOH”.
==========================
Fields of type "data" are "always immediately preceded by a length field". Failure to do this should result in a session level reject message.
Tag 96 is of type data and must be immediately preceeded by tag 95.
Incidentally, tag 96 is not Password as you indicated. It is actually called RawData. The Password field is tag 554 and is of data type string.
I hope this helps.
JohnP
Tag order Josh Hoffberg / Chicago Mercantile Exchange 6 May 2005 10:45AM ET Re: Tag order Josh Hoffberg / Chicago Mercantile Exchange 6 May 2005 10:50AM ET Re: Tag order
John Prewett / Lava Trading 6 May 2005 11:10AM ET
|
