|
General Q/A
< Previous Next >
Highest precedence between tag 126 and tag 432 for GTD orders
FIX Query
18 Mar 2010 7:30AM ET Hi,
We are planning to support both the tags 126 (UTCTimestamp) and 432 (LocalMktDate) since few buy connection support 126 for GTD orders whereas others support 432.
As per FIX 4.2 specification, tag 126 is conditionally required if TimeInForce = GTD and ExpireDate (432) is not specified and tag 432 is conditionally required if TimeInForce = GTD and ExpireTime (126) is not specified.
We seek help to take a call ‘for highest precedence’ about value that is reported with tag 126 and 432 in rare case scenario where buy side sends both these tags (126 and 432) with valid formatted values for MsgType = D/ G/ E etc.
Thanks in advance.
Highest precedence between tag 126 and tag 432 for GTD orders
FIX Query 18 Mar 2010 7:30AM ET
|
