[This message was posted by Ryan Pierce (FPL Technical Director) of FIX Protocol Ltd. <[email protected]> to the "4.2 Changes" discussion forum at http://fixprotocol.org/discuss/5. You can reply to it on-line at http://fixprotocol.org/discuss/read/bfb25296 - PLEASE DO NOT REPLY BY MAIL.]
> Hey i beleive in the cases where the ExDestination is not mentioned in > the Protocol version you can choose any value confirm your counterparty > and if you are a roker side do the changes in your configs for that or > ask the vendor to support that ( convert the required for client) . This > can be handled at application level No, this is incorrect. In FIX 4.2 and below, ExDestination used proprietary alphabetic Reuters codes, as well as codes assigned by FPL. You can view them here: http://fixprotocol.org/specifications/exchanges.shtml Note there are two tabs, one for Reuters codes, and one for FPL-assigned values. I don't see anything assigned for Alpha or Pure. The exchanges themselves can request codes from FPL. Please ask your contacts at the exchange to mail [email protected] and ask that a code be assigned. FPL will then assign one. Note that in later versions of the protocol (4.4, and, I think, 4.3) these values are obsolete, and ISO 10383 MIC codes are used. Information and a link to request them is here: http://www.iso15022.org/MIC/homepageMIC.htm [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 -~----------~----~----~----~------~----~------~--~---
