Fixed length Integer

, ,
1

Imported from previous forum

2

I have a couple of questions.

  1. Is it valid if integer tag coming with preceeding zeros - 34=00000025 ?
  2. And is it valid if integer tag coming with fixed length - 9=0058 ?

ex) Recv 8=FIX.4.2 9=0058 35=0 34=00000025 52=20110329-08:25:38.809 49=ABC 56=XYZ 10=015

Thank you for the help in advance.

Shawn in NJ

3

Hi Shawn,

some commercial engines use something like 9=0058 so this should be OK.

See also volume 1 of the FIX specification, section data types:
Here is explicitly stated, that both “int” and “float” types may contain leading zeros.

Cheers, Jörg

I have a couple of questions.

  1. Is it valid if integer tag coming with preceeding zeros - 34=00000025 ?
  2. And is it valid if integer tag coming with fixed length - 9=0058 ?

ex) Recv 8=FIX.4.2 9=0058 35=0 34=00000025 52=20110329-08:25:38.809 49=ABC 56=XYZ 10=015

Thank you for the help in advance.

Shawn in NJ

4

Jörg
I’ve got it.
Thanks a lot.

Shawn

Hi Shawn,

some commercial engines use something like 9=0058 so this should be OK.

See also volume 1 of the FIX specification, section data types:
Here is explicitly stated, that both “int” and “float” types may contain leading zeros.

Cheers, Jörg

I have a couple of questions.

  1. Is it valid if integer tag coming with preceeding zeros - 34=00000025 ?
  2. And is it valid if integer tag coming with fixed length - 9=0058 ?

ex) Recv 8=FIX.4.2 9=0058 35=0 34=00000025 52=20110329-08:25:38.809 49=ABC 56=XYZ 10=015

Thank you for the help in advance.

Shawn in NJ

5

some commercial engines use something like 9=0058 so this should be OK.

Do you know why they do it? By having that value fixed-length, they reuse the same buffer over and over to send a message (i.e. an order). This beats crap out of guys who doesn’t use the same approach in terms of performance. Applicable on exchanges where FIX is a native protocol. So, good for them.