Imported from previous forum
[ original email was from Jeffrey Croft - jeff.croft@plusmarketsgroup.com ]
Tag 368 ‘QuoteEntryRejectReason’ does not support an enumeration to cover an instrument being suspended. Would seem like a logical addition to the spec unless there is another tag I should be using for this? ‘Exchange Closed’ is probably closest but misleading.
Agree that this use case is not covered yet. You can use values of 100 and above until there is a standard value. Maybe this can be added to the next gap analysis being submitted in the area of quote handling by somebody. The list of standard valid values cannot be extended on the basis of forum entries alone.
Tag 368 ‘QuoteEntryRejectReason’ does not support an enumeration to cover an instrument being suspended. Would seem like a logical addition to the spec unless there is another tag I should be using for this? ‘Exchange Closed’ is probably closest but misleading.
[ original email was from Jeffrey Croft - jeff.croft@plusmarketsgroup.com ]
Thanks for the reply. I guess for now we will use a field above 100 to support this.
Agree that this use case is not covered yet. You can use values of 100 and above until there is a standard value. Maybe this can be added to the next gap analysis being submitted in the area of quote handling by somebody. The list of standard valid values cannot be extended on the basis of forum entries alone.
Tag 368 ‘QuoteEntryRejectReason’ does not support an enumeration to cover an instrument being suspended. Would seem like a logical addition to the spec unless there is another tag I should be using for this? ‘Exchange Closed’ is probably closest but misleading.