|
Transport Independence Framework
< Previous Next >
Tag ordering in FIXT.1.1 messages
Mahesh Kumaraguru <>
18 Jan 2010 10:54PM ET Hi Clive,
I would recommend having all mandatory fields before any optional fields.
Regards,
K. Mahesh
>
> Hi
>
> To support overriding of the default FIX message (application) version
> specified in the logon message it is necessary that the ApplVerID
> (1128), ApplExtID (1156) and CstmApplVerID (1129) if they occur, do so
> in the message header before any of the application message fields that
> are versioned outside of the FIXT.1.1 specification. If this is not the
> ccase a FIX parser is unable to parse the FIX message correctly.
>
> At the moment we have used the rule that these fields if they occur
> should appear directly after SenderCompID and TargetCompID... that is
> how we construct outbound FIX messages. Inbound we are more relaxed with
> our validation to cater for the 2 situations below...
>
> The FIXT.1.1 spec (March 2008) is ambiguous.. in the Standard Message
> Header section, page 17 the versioning fields are shown directly after
> the MsgType (35) field. Whilst in the section FIXT Header Mapping Table
> (page 31), ApplVerID is specified to be at position 6 if present, i.e.
> after the SenderCompID and TargetCompID tags.
>
> I am ambivolent over which option is selected, but this does need to be
> tied down. Is the simple option to use the recommendation per the FIXT
> Header Mapping Table?
>
> I think some arguments were put forward for having all the delivery
> fields before the versioning information (e.g. DeliverTo and
> OnBehalfOf tags)?
>
> Thanks
>
> Clive Browning
>
> Rapid Addition Ltd
>
Tag ordering in FIXT.1.1 messages
Mahesh Kumaraguru 18 Jan 2010 10:54PM ET
|
@FIXProtocol
