FIXT.1.1 field order in header

, ,
1

Imported from previous forum

2

[ original email was from John Prewett - jprewett@lavatrading.com ]
In the FIXT.1.1 specification it makes reference in the “FIXT Header Mapping Table” to the fact that SenderCompID is field 4, TargetCompID is field 5 and ApplVerID is field 6.

Nowhere else in the specification are these positional field requirements mentioned.

Is this just an error in the specification and the field order of these fields is actually unspecified?

I notice that FIXimate makes no mention of these fields having positional requirements.

3

John,

This question was raised previously at

http://fixprotocol.org/discuss/read/ca82b7da

The order (as of now) is

BeingString (8) - 1st position
BodyLength (9) - 2nd position
MsgType (35) - 3rd position
SenderCompID (49) - 4th position
TargetCompID (56) - 5th position
ApplVerID (1128) - must be 6th position if used

FIXimate not specifying the positional requirements is already raised at

http://fixprotocol.org/discuss/read/e617a96d

Regards,
K. Mahesh

In the FIXT.1.1 specification it makes reference in the “FIXT Header
Mapping Table” to the fact that SenderCompID is field 4, TargetCompID is
field 5 and ApplVerID is field 6.

Nowhere else in the specification are these positional field
requirements mentioned.

Is this just an error in the specification and the field order of these
fields is actually unspecified?

I notice that FIXimate makes no mention of these fields having
positional requirements.