[This message was posted by Xinyu Xiang of Bloomberg, LP <[email protected]> to the "Asia/Pac" discussion forum at http://fixprotocol.org/discuss/18. You can reply to it on-line at http://fixprotocol.org/discuss/read/fe9654ae - PLEASE DO NOT REPLY BY MAIL.]
Hi Varaprasad, I tried this out. Our software picks out "ENVH SP" as the best match. The other one does not seem to have any history trade data. Wish I could understand why it exists. Good luck. > Dear Xinyu Xiang, > > Thank you very much for your answers! > > You are correct for stock [GGR2 SP], the stock is delisted. It may be my > back example. > > How about for the stock:[ENVH SP, ENVH1 SP], i have checked in the > bloomberg both are active. Hence both will have same 48/22/100 if > ISIN is used. > > How do we over come if we do not user Tag55? > > > It looks to me [GGR2 SP] is delisted since 5/11/09. So your engine > > should find [GGR SP] as the sole hit. We also use 48/22/100 or 207 and > > whenever available tag15 (currency) to load security. As far as I > > know, this combo creates unique hit. > > > > > Few Singapore Securities [ex GGR SP, GGR2 SP] has the same ISIN code > > > and listed on the same exchange. The only difference in these > > > securities is tradable lot size. > > > > > > Does any one know how is the FIX standard to get the unique stock > > > when we use the ISIN to lookup the security Master. > > > > > > MY client is sending the FIX order with 48/22/100. With these we > > > still get 2 valid stocks and MY FIXEngine rejects as it could not > > > get the unique stock. > > > > > > Do you have any suggestions? [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.
