Imported from previous forum
[ original email was from ron newell - rnewell@cme.com ]
What is the use / benefit of adding SecondaryExecID?
ExecID, it would appear, is specific to a single Execution Report message.
This is unlike the combinations ClOrdID/SecondaryClOrdID and OrderID/SecondaryOrderID, which allow system and sub-system to each assign an ID
Also, description provided in the Data Dictionary is in error.
This has been addressed for the final release of FIX 4.3 (post-Draft #3). Thank you.
[PC20010822_2] Address post-Draft #3 documentation/consistency issues with SecondaryClOrdID, SecondaryOrderID, and SecondaryExecID field
Rationale:
- SecondaryClOrdID should appear in exactly every message where a new ClOrdID is specified (buy-side). In addition, it should be allowed for in sell-side messages where the sell-side echoes back a ClOrdID
- SecondaryExecID should appear in exactly every message containing an ExecID originated by the sell-side
- SecondaryOrderID should be in exactly every message where a new OrderID is specified (sell-side)
Changes associated with this item:
- Removed SecondaryExecID from Order Cancel Reject (did not contain ExecID).
> What is the use / benefit of adding SecondaryExecID?
>
> ExecID, it would appear, is specific to a single Execution Report message.
>
> This is unlike the combinations ClOrdID/SecondaryClOrdID and OrderID/SecondaryOrderID, which allow system and sub-system to each assign an ID
>
> Also, description provided in the Data Dictionary is in error.
>