Imported from previous forum
Hi, we have a disagreement with a FIX counterparty regarding usage of tag 122 (OrigSendingTime).
The specs say:
"Required for message resends. If data is not available set to same value as SendingTime."
We believe that a Sequence Reset is not a message resend (it’s actually even saying that there are no messages to resend), but our counterparty argues that it is and that the value in tag 122 should be set to the same as SendingTime.
Has anybody come across this issue? Some opinions on the interpretation of the specs on this point would be greatly appreciated to help us resolve this disagreement.
Many thanks,
Marc Maestracci
Goldman Sachs
There are 3 test cases related to OrigSendingTime which are documented in the "FIX Session Level Test Cases and Expected Behaviors" (in Volume 2 of FIX 4.3 or on the FIX website "FPL Organization", "Global Technical", "Archive"). Those test cases are 2e, 2f, and 2g.
According to 2g, one should "Send a Reject (session-level)" in response to a message with "PossDupFlag set to Y and OrigSendingTime not specified".
The "Standard Header" definition states "If data is not available set to same value as SendingTime" for OrigSendingTime.
> Hi, we have a disagreement with a FIX counterparty regarding usage of tag 122 (OrigSendingTime).
>
> The specs say:
> “Required for message resends. If data is not available set to same value as SendingTime.”
>
> We believe that a Sequence Reset is not a message resend (it’s actually even saying that there are no messages to resend), but our counterparty argues that it is and that the value in tag 122 should be set to the same as SendingTime.
>
> Has anybody come across this issue? Some opinions on the interpretation of the specs on this point would be greatly appreciated to help us resolve this disagreement.
>
> Many thanks,
> Marc Maestracci
> Goldman Sachs
>