[This message was posted by Mahesh Kumaraguru of <[email protected]> to the
"4.0 Session" discussion forum at http://fixprotocol.org/discuss/12. You can
reply to it on-line at http://fixprotocol.org/discuss/read/9512f9f1 - PLEASE DO
NOT REPLY BY MAIL.]
In FIX.4.0, Tag 9 (BodyLength) is of data type int. Definition of int data type
is
int: Sequence of digits without commas or decimals and optional sign character
(ASCII characters "-" and "0" - "9" ). The sign character utilizes one byte
(i.e. positive int is "99999" while negative int is "-99999").
Examples: 723 in field 21 would be mapped int as |21=723|.
-723 in field 12 would be mapped int as |12=-723|"
Mote there is no specification of max value.
Definition of BodyLength is
Message length, in bytes, forward to the CheckSum field. ALWAYS SECOND FIELD IN
MESSAGE. (Always unencrypted) Valid values : 0 - 9999
>From FIX.4.2 onwards Definition of BodyLength is
Message length, in bytes, forward to the CheckSum field. ALWAYS SECOND FIELD IN
MESSAGE. (Always unencrypted)
Thus in a FIX.4.2 Session a very large message can be accepted. I have come
across FIX.4.0, FIX.4.1 "lenient" FIX engines which accept messages longer than
9999 bytes.
> Thanks!
>
> I am now only concerned about size of Bodylength field, so as to know how
> much data to read from socket!
>
> What would be the maximum allowed value of Bodylength? (i.e. max size of FIX
> message)
[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.
