Imported from previous forum
Has a Reuters mnemonic/Reuters Exchange Code been assigned for the new C2 OPTIONS EXCHANGE coming online in October 2010?
Has a Reuters mnemonic/Reuters Exchange Code been assigned for the new C2 OPTIONS EXCHANGE coming online in October 2010?
John,
C2OX is the MIC code assigned to C2. In July, Reuters had a meeting with the FIX Protocol team about assigning new FIX 4.2 Exchange IDs and agreed that new 4.2 IDs would be the same as the MIC ID (as long as there were no duplicates etc). Therefore, the FIX 4.2 ID will be C2OX.
Regards,
FPL Program Office
Has a Reuters mnemonic/Reuters Exchange Code been assigned for the new C2 OPTIONS EXCHANGE coming online in October 2010?
John,
C2OX is the MIC code assigned to C2. In July, Reuters had a meeting with the FIX Protocol team about assigning new FIX 4.2 Exchange IDs and agreed that new 4.2 IDs would be the same as the MIC ID (as long as there were no duplicates etc). Therefore, the FIX 4.2 ID will be C2OX.
Regards,
FPL Program Office
Hi FPL Program Office
Very interesting to read this comment about the new FIX42 exchange IDs assignment.
My questions are
Is the Exchange code table a reliable source for updated exchange code=? Is it updated accordingly? (http://www.fixprotocol.org/specifications/ex_other.shtml)
Do we need to request updates?
Do you need a workforce / volunteer to update?
Happy to join in the effort, will save me time and effort in any case?
Regards,
Jonathan
ISO is a reliable source for MIC values and they are not maintained by FPL. It would be good to gradually move to the ISO standard and therefore FPL has said in the past that they would only issue numeric values (your link to “Other” below) upon request and in cases where the marketplace was unable to obtain a MIC or a Reuters code. I believe that even market segments will be able to obtain a MIC, e.g. to target the dark pool of a marketplace.
I would therefore not expect the list to grow anymore and people should move from numeric values to MIC values for those in the list that also have a MIC. In any case the list you refer to below is not intended to be a complete list of marketplaces and FIX 4.3 versions are supposed to use the ISO values instead anyway.
Regards,
Hanno.
Hi FPL Program Office
Very interesting to read this comment about the new FIX42 exchange IDs assignment.My questions are
Is the Exchange code table a reliable source for updated exchange code=? Is it updated accordingly? (http://www.fixprotocol.org/specifications/ex_other.shtml)
Do we need to request updates?
Do you need a workforce / volunteer to update?
Happy to join in the effort, will save me time and effort in any case?
Regards,
Jonathan
Hello,
Just to expand on Hanno’s comment below, in terms of how it has worked, FIX versions up through and including 4.2 use Reuters suffix codes. FIX versions 4.3 and above use the ISO 10383 MIC (Market Identifier Code) standard: http://www.iso15022.org/MIC/homepageMIC.htm.
FPL has assigned numeric codes to those markets/venues that did/could not have a code defined by one of these two sources (on http://www.fixprotocol.org/specifications/ex_other.shtml) so this link has been updated as requests have come through directly to FPL.
Regards,
FPL Program Office
ISO is a reliable source for MIC values and they are not maintained by FPL. It would be good to gradually move to the ISO standard and therefore FPL has said in the past that they would only issue numeric values (your link to “Other” below) upon request and in cases where the marketplace was unable to obtain a MIC or a Reuters code. I believe that even market segments will be able to obtain a MIC, e.g. to target the dark pool of a marketplace.
I would therefore not expect the list to grow anymore and people should move from numeric values to MIC values for those in the list that also have a MIC. In any case the list you refer to below is not intended to be a complete list of marketplaces and FIX 4.3 versions are supposed to use the ISO values instead anyway.
Regards,
Hanno.Hi FPL Program Office
Very interesting to read this comment about the new FIX42 exchange IDs assignment.My questions are
Is the Exchange code table a reliable source for updated exchange code=? Is it updated accordingly? (http://www.fixprotocol.org/specifications/ex_other.shtml)
Do we need to request updates?
Do you need a workforce / volunteer to update?
Happy to join in the effort, will save me time and effort in any case?
Regards,
Jonathan
Has a Reuters mnemonic/Reuters Exchange Code been assigned for the new C2 OPTIONS EXCHANGE coming online in October 2010?
John,
C2OX is the MIC code assigned to C2. In July, Reuters had a meeting with the FIX Protocol team about assigning new FIX 4.2 Exchange IDs and agreed that new 4.2 IDs would be the same as the MIC ID (as long as there were no duplicates etc). Therefore, the FIX 4.2 ID will be C2OX.
Regards,
FPL Program Office
That being said, is there any MIC/Rueter code asigned for the upcoming Nasdaq PSX?
thanks!
Please have a look at http://www.nasdaqtrader.com/content/productsservices/trading/psx/psxfaqs.pdf.
Q: What will the PSX International Standard (ISO 10383) market identification code (MIC) be?
A: The MIC code for the PSX equities exchange will be XPHL. The MIC code for the PHLX options exchange is XPHO. Refer to http://www.iso15022.org/MIC/homepageMIC.htm for a complete list of MICs.
Has a Reuters mnemonic/Reuters Exchange Code been assigned for the new C2 OPTIONS EXCHANGE coming online in October 2010?
John,
C2OX is the MIC code assigned to C2. In July, Reuters had a meeting with the FIX Protocol team about assigning new FIX 4.2 Exchange IDs and agreed that new 4.2 IDs would be the same as the MIC ID (as long as there were no duplicates etc). Therefore, the FIX 4.2 ID will be C2OX.
Regards,
FPL Program OfficeThat being said, is there any MIC/Rueter code asigned for the upcoming Nasdaq PSX?
thanks!