Imported from previous forum
[ original email was from ron newell - rnewell@cme.com ]
Given the addition of SecondaryClOrdID (526), another tag SecondaryOrigClOrdID might be needed.
ClOrdID (11) is currently supplemented by OrigClOrdID (41) to support Cancel and Cancel/Replace Request message types.
SecondaryClOrdID (526) may similarily need to be supplemented by a SecondaryOrigClOrdID tag.
Comment for this SecondaryOrigClOrdID tag would be "Conditionally required for response to an electronic Cancel or Cancel/Replace Request. SecondaryClOrdID of the previously accepted order when canceling or replacing an order."
Description would be "SecondaryClOrdID of the previous order as assigned by the buy-side (trader, desk, broker, institution) and used to identify the previous order in Cancel and Cancel/Replace Request messages."
This has been addressed but no changes have been deemed necessary as the SecondaryXXXID feature is not designed to mimick "chaining" like OrigClOrdID and ClOrdID. [PC20010822_2]
> Given the addition of SecondaryClOrdID (526), another tag SecondaryOrigClOrdID might be needed.
>
> ClOrdID (11) is currently supplemented by OrigClOrdID (41) to support Cancel and Cancel/Replace Request message types.
>
> SecondaryClOrdID (526) may similarily need to be supplemented by a SecondaryOrigClOrdID tag.
>
> Comment for this SecondaryOrigClOrdID tag would be "Conditionally required for response to an electronic Cancel or Cancel/Replace Request. SecondaryClOrdID of the previously accepted order when canceling or replacing an order."
>
> Description would be "SecondaryClOrdID of the previous order as assigned by the buy-side (trader, desk, broker, institution) and used to identify the previous order in Cancel and Cancel/Replace Request messages."
>