[This message was posted by Hanno Klein of Deutsche Börse Systems 
<[email protected]> to the "General Q/A" discussion forum at 
http://fixprotocol.org/discuss/22. You can reply to it on-line at 
http://fixprotocol.org/discuss/read/fedfa895 - PLEASE DO NOT REPLY BY MAIL.]

> > The standard option is always to use the Text (58) tag. This will work
> > if you do not need to convey other information in the context of a
> > trade cancel.
> 
> Sure, but we want to have a more type safe way of doing this handling
> the canceled trades is an automated process.
> 
> > Adding one "locally" only works for internal tags >10000, otherwise it
> > needs to be one between 5000 and 9999 registered on the FPL website. I
> > guess what you are looking for should be called TradeCxlReason and
> > have a list of pre-defined values and Reserved100Plus datatype for user-
> > defined values. The closest one I found is 6042 CxlReason which should
> > apply for orders, quotes and trades (executions). I suggest to use
> > that tag if you do not want to submit a gap analysis for an extension
> > of the FIX standard.
> 
> Using 6042 seems just fine to me. Is there any other information apart
> from the tag name and number in the list on the web site, like what
> values are valid?

Not that I am aware of. It would be in the field description. Apparently it was 
introduced as part of a repeating group to cancel rebills but you would use it 
as a standalone field. I still think it is better to re-use that field and not 
introduce a new user-defined field.


[You can unsubscribe from this discussion group by sending a message to 
mailto:[email protected]]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Financial Information eXchange" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/FIX-Protocol?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to