# How to dissociate japanese exchange with Reuters Code in FIX 4.2

**URL:** <https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340>\
**Category:** General Q&A\
**Tags:** general-qa, imported, xid\_166039\
**Created:** [November 12, 2007, 10:33am UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340 "2007-11-12T10:33:27Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 12, 2007, 10:33am UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/1 "2007-11-12T10:33:27Z")

</div>

Imported from previous forum

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 12, 2007, 10:33am UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/2 "2007-11-12T10:33:27Z")

</div>

[original email was from Francois Milot - [francois.milot@gltrade.com](mailto:francois.milot@gltrade.com) ]  
Hi all,

I’m facing a problem in FIX 4.2. I have to send orders on two markets which are TOCOM (Tokyo Commodities) and TIFFE (Tokyo International Financial Futures Exchange). The only way to specify the exchange is, for me, to use tag 100. The problem I’m facing is that, in FIX 4.2 specs, reuters code related to Tokyo is T (Tokyo Stock Exchange), so I haven’t any mean to dissociate these two markets.

I’m looking for a solution to differentiate TIFFE and TOCOM with FIX field 100. I’ve look unsuccessfully for new reuters code.

Has anybody an idea or a workaround to fix that ?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 12, 2007, 10:49am UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/3 "2007-11-12T10:49:14Z")

</div>

[original email was from Andrew Scott - [ascott@latentzero.com](mailto:ascott@latentzero.com) ]  
\> Hi all,

> I’m facing a problem in FIX 4.2. I have to send orders on two markets  
> which are TOCOM (Tokyo Commodities) and TIFFE (Tokyo International  
> Financial Futures Exchange). The only way to specify the exchange is,  
> for me, to use tag 100. The problem I’m facing is that, in FIX 4.2  
> specs, reuters code related to Tokyo is T (Tokyo Stock Exchange), so I  
> haven’t any mean to dissociate these two markets.
> 
> I’m looking for a solution to differentiate TIFFE and TOCOM with FIX  
> field 100. I’ve look unsuccessfully for new reuters code.
> 
> Has anybody an idea or a workaround to fix that ?
> 
> Thanks in advance.

Francois,

With agreement from your destinations, I would supplement the Reuters codes with ISO 10383 codes from the FIX 4.4 protocol specification document, or from

[http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)

For example, the TIFFE is XTFF, and the commodities exchange is XTKT.

Hope this helps!  
Andrew

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 12, 2007, 12:36pm UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/4 "2007-11-12T12:36:21Z")

</div>

[original email was from Francois Milot - [francois.milot@gltrade.com](mailto:francois.milot@gltrade.com) ]  
\> \> Hi all,

> > I’m facing a problem in FIX 4.2. I have to send orders on two markets  
> > which are TOCOM (Tokyo Commodities) and TIFFE (Tokyo International  
> > Financial Futures Exchange). The only way to specify the exchange is,  
> > for me, to use tag 100. The problem I’m facing is that, in FIX 4.2  
> > specs, reuters code related to Tokyo is T (Tokyo Stock Exchange), so I  
> > haven’t any mean to dissociate these two markets.
> > 
> > I’m looking for a solution to differentiate TIFFE and TOCOM with FIX  
> > field 100. I’ve look unsuccessfully for new reuters code.
> > 
> > Has anybody an idea or a workaround to fix that ?
> > 
> > Thanks in advance.
> 
> Francois,
> 
> With agreement from your destinations, I would supplement the Reuters  
> codes with ISO 10383 codes from the FIX 4.4 protocol specification  
> document, or from
> 
> [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> 
> For example, the TIFFE is XTFF, and the commodities exchange is XTKT.
> 
> Hope this helps! Andrew

Many thanks for your answer. The problem is that I have to deal with FIX 4.2 (so Reuters Code in FIX tag 100).

I found a link in other cases : [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but don’t know if these codes are official.

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 12, 2007, 12:57pm UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/5 "2007-11-12T12:57:03Z")

</div>

[original email was from Andrew Scott - [ascott@latentzero.com](mailto:ascott@latentzero.com) ]  
\> \> \> Hi all,

> > > I’m facing a problem in FIX 4.2. I have to send orders on two  
> > > markets which are TOCOM (Tokyo Commodities) and TIFFE (Tokyo  
> > > International Financial Futures Exchange). The only way to specify  
> > > the exchange is, for me, to use tag 100. The problem I’m facing is  
> > > that, in FIX 4.2 specs, reuters code related to Tokyo is T (Tokyo  
> > > Stock Exchange), so I haven’t any mean to dissociate these two  
> > > markets.
> > > 
> > > I’m looking for a solution to differentiate TIFFE and TOCOM with FIX  
> > > field 100. I’ve look unsuccessfully for new reuters code.
> > > 
> > > Has anybody an idea or a workaround to fix that ?
> > > 
> > > Thanks in advance.
> > 
> > Francois,
> > 
> > With agreement from your destinations, I would supplement the Reuters  
> > codes with ISO 10383 codes from the FIX 4.4 protocol specification  
> > document, or from
> > 
> > [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> > 
> > For example, the TIFFE is XTFF, and the commodities exchange is XTKT.
> > 
> > Hope this helps! Andrew
> 
> Many thanks for your answer. The problem is that I have to deal with FIX  
> 4.2 (so Reuters Code in FIX tag 100).
> 
> I found a link in other cases :  
> [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but don’t know if these  
> codes are official.

FIX 4.2 deals with the structure and semantics of the message; as far as I know there is nothing stopping you using ISO 10383 codes in 100 ExDestination on a FIX 4.2 message, beyond explicit agreement from your counterparties.

I’ve checked out this link. The CBOE code you reference conflicts with the FPL codes at:

[http://www.fixprotocol.org/specifications/exchanges.shtml](http://www.fixprotocol.org/specifications/exchanges.shtml)

and the code ‘CO’ points to the Copenhagen Stock Exchange.

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 12, 2007, 1:07pm UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/6 "2007-11-12T13:07:34Z")

</div>

[original email was from Francois Milot - [francois.milot@gltrade.com](mailto:francois.milot@gltrade.com) ]  
\> \> \> \> Hi all,

> > > > I’m facing a problem in FIX 4.2. I have to send orders on two  
> > > > markets which are TOCOM (Tokyo Commodities) and TIFFE (Tokyo  
> > > > International Financial Futures Exchange). The only way to specify  
> > > > the exchange is, for me, to use tag 100. The problem I’m facing is  
> > > > that, in FIX 4.2 specs, reuters code related to Tokyo is T (Tokyo  
> > > > Stock Exchange), so I haven’t any mean to dissociate these two  
> > > > markets.
> > > > 
> > > > I’m looking for a solution to differentiate TIFFE and TOCOM with  
> > > > FIX field 100. I’ve look unsuccessfully for new reuters code.
> > > > 
> > > > Has anybody an idea or a workaround to fix that ?
> > > > 
> > > > Thanks in advance.
> > > 
> > > Francois,
> > > 
> > > With agreement from your destinations, I would supplement the  
> > > Reuters codes with ISO 10383 codes from the FIX 4.4 protocol  
> > > specification document, or from
> > > 
> > > [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> > > 
> > > For example, the TIFFE is XTFF, and the commodities exchange  
> > > is XTKT.
> > > 
> > > Hope this helps! Andrew
> > 
> > Many thanks for your answer. The problem is that I have to deal with  
> > FIX 4.2 (so Reuters Code in FIX tag 100).
> > 
> > I found a link in other cases :  
> > [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but don’t know if these  
> > codes are official.
> 
> FIX 4.2 deals with the structure and semantics of the message; as far as  
> I know there is nothing stopping you using ISO 10383 codes in 100  
> ExDestination on a FIX 4.2 message, beyond explicit agreement from your  
> counterparties.
> 
> I’ve checked out this link. The CBOE code you reference conflicts with  
> the FPL codes at:
> 
> [http://www.fixprotocol.org/specifications/exchanges.shtml](http://www.fixprotocol.org/specifications/exchanges.shtml)
> 
> and the code ‘CO’ points to the Copenhagen Stock Exchange.

You’re right concerning conflicts in the related link (there are some other conflicts like ‘V’ for both USA index and Austria Exchange).

Moreover, regarding to FIX 4.2 protocol, in FIX Field 100 for the valid values, they made reference to Appendix C which lists all valid Reuters Code. So client who wants to make FIX 4.2 will see that and will logically want to use Reuters code. That’s the problem I’m facing with.

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 12, 2007, 1:27pm UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/7 "2007-11-12T13:27:40Z")

</div>

[original email was from Ainhoa Dewisme - [ainhoa.dewisme@reuters.com](mailto:ainhoa.dewisme@reuters.com) ]  
Hello,

If this is of any help:

Reuters Code for Tokyo Commodity Exchange is TCE

Reuters Code for Tokyo Financial Futures Exchange TFF

Regards

Ainhoa

> > > > > Hi all,
> > > > > 
> > > > > I’m facing a problem in FIX 4.2. I have to send orders on two  
> > > > > markets which are TOCOM (Tokyo Commodities) and TIFFE (Tokyo  
> > > > > International Financial Futures Exchange). The only way to  
> > > > > specify the exchange is, for me, to use tag 100. The problem I’m  
> > > > > facing is that, in FIX 4.2 specs, reuters code related to Tokyo  
> > > > > is T (Tokyo Stock Exchange), so I haven’t any mean to dissociate  
> > > > > these two markets.
> > > > > 
> > > > > I’m looking for a solution to differentiate TIFFE and TOCOM with  
> > > > > FIX field 100. I’ve look unsuccessfully for new reuters code.
> > > > > 
> > > > > Has anybody an idea or a workaround to fix that ?
> > > > > 
> > > > > Thanks in advance.
> > > > 
> > > > Francois,
> > > > 
> > > > With agreement from your destinations, I would supplement the  
> > > > Reuters codes with ISO 10383 codes from the FIX 4.4 protocol  
> > > > specification document, or from
> > > > 
> > > > [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> > > > 
> > > > For example, the TIFFE is XTFF, and the commodities exchange is  
> > > > XTKT.
> > > > 
> > > > Hope this helps! Andrew
> > > 
> > > Many thanks for your answer. The problem is that I have to deal with  
> > > FIX 4.2 (so Reuters Code in FIX tag 100).
> > > 
> > > I found a link in other cases :  
> > > [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but don’t know if  
> > > these codes are official.
> > 
> > FIX 4.2 deals with the structure and semantics of the message; as far  
> > as I know there is nothing stopping you using ISO 10383 codes in 100  
> > ExDestination on a FIX 4.2 message, beyond explicit agreement from  
> > your counterparties.
> > 
> > I’ve checked out this link. The CBOE code you reference conflicts with  
> > the FPL codes at:
> > 
> > [http://www.fixprotocol.org/specifications/exchanges.shtml](http://www.fixprotocol.org/specifications/exchanges.shtml)
> > 
> > and the code ‘CO’ points to the Copenhagen Stock Exchange.
> 
> You’re right concerning conflicts in the related link (there are some  
> other conflicts like ‘V’ for both USA index and Austria Exchange).
> 
> Moreover, regarding to FIX 4.2 protocol, in FIX Field 100 for the valid  
> values, they made reference to Appendix C which lists all valid Reuters  
> Code. So client who wants to make FIX 4.2 will see that and will  
> logically want to use Reuters code. That’s the problem I’m facing with.

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 12, 2007, 1:46pm UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/8 "2007-11-12T13:46:08Z")

</div>

[original email was from Francois Milot - [francois.milot@gltrade.com](mailto:francois.milot@gltrade.com) ]  
I appreciate a lot. It helps me a lot. How did you have such a code ? That will be helpful for me.

Regards,

> Hello,
> 
> If this is of any help:
> 
> Reuters Code for Tokyo Commodity Exchange is TCE
> 
> Reuters Code for Tokyo Financial Futures Exchange TFF
> 
> Regards
> 
> Ainhoa
> 
> > > > > > Hi all,
> > > > > > 
> > > > > > I’m facing a problem in FIX 4.2. I have to send orders on two  
> > > > > > markets which are TOCOM (Tokyo Commodities) and TIFFE (Tokyo  
> > > > > > International Financial Futures Exchange). The only way to  
> > > > > > specify the exchange is, for me, to use tag 100. The problem  
> > > > > > I’m facing is that, in FIX 4.2 specs, reuters code related to  
> > > > > > Tokyo is T (Tokyo Stock Exchange), so I haven’t any mean to  
> > > > > > dissociate these two markets.
> > > > > > 
> > > > > > I’m looking for a solution to differentiate TIFFE and TOCOM  
> > > > > > with FIX field 100. I’ve look unsuccessfully for new reuters  
> > > > > > code.
> > > > > > 
> > > > > > Has anybody an idea or a workaround to fix that ?
> > > > > > 
> > > > > > Thanks in advance.
> > > > > 
> > > > > Francois,
> > > > > 
> > > > > With agreement from your destinations, I would supplement the  
> > > > > Reuters codes with ISO 10383 codes from the FIX 4.4 protocol  
> > > > > specification document, or from
> > > > > 
> > > > > [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> > > > > 
> > > > > For example, the TIFFE is XTFF, and the commodities exchange is  
> > > > > XTKT.
> > > > > 
> > > > > Hope this helps! Andrew
> > > > 
> > > > Many thanks for your answer. The problem is that I have to deal  
> > > > with FIX 4.2 (so Reuters Code in FIX tag 100).
> > > > 
> > > > I found a link in other cases :  
> > > > [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but don’t know if  
> > > > these codes are official.
> > > 
> > > FIX 4.2 deals with the structure and semantics of the message; as  
> > > far as I know there is nothing stopping you using ISO 10383 codes in  
> > > 100 ExDestination on a FIX 4.2 message, beyond explicit agreement  
> > > from your counterparties.
> > > 
> > > I’ve checked out this link. The CBOE code you reference conflicts  
> > > with the FPL codes at:
> > > 
> > > [http://www.fixprotocol.org/specifications/exchanges.shtml](http://www.fixprotocol.org/specifications/exchanges.shtml)
> > > 
> > > and the code ‘CO’ points to the Copenhagen Stock Exchange.
> > 
> > You’re right concerning conflicts in the related link (there are some  
> > other conflicts like ‘V’ for both USA index and Austria Exchange).
> > 
> > Moreover, regarding to FIX 4.2 protocol, in FIX Field 100 for the  
> > valid values, they made reference to Appendix C which lists all valid  
> > Reuters Code. So client who wants to make FIX 4.2 will see that and  
> > will logically want to use Reuters code. That’s the problem I’m  
> > facing with.

---

<div class="post-metadata">

**Author:** ![fp\_x](https://avatars.discourse-cdn.com/v4/letter/f/9de0a6/32.png) [@fp\_x](https://forum.fixtrading.org/u/fp_x)\
**Post date:** [November 12, 2007, 2:04pm UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/9 "2007-11-12T14:04:43Z")

</div>

Dear Francois,

We will be updating a full list of Reuters Exchange Codes on the FPL website shortly. Meanwhile, we will add both Tokyo derivatives exchanges codes to our list.

Thank you,  
FPL Program Office

> I appreciate a lot. It helps me a lot. How did you have such a code ?  
> That will be helpful for me.
> 
> Regards,
> 
> > Hello,
> > 
> > If this is of any help:
> > 
> > Reuters Code for Tokyo Commodity Exchange is TCE
> > 
> > Reuters Code for Tokyo Financial Futures Exchange TFF
> > 
> > Regards
> > 
> > Ainhoa
> > 
> > > > > > > Hi all,
> > > > > > > 
> > > > > > > I’m facing a problem in FIX 4.2. I have to send orders on  
> > > > > > > two markets which are TOCOM (Tokyo Commodities) and TIFFE  
> > > > > > > (Tokyo International Financial Futures Exchange). The only  
> > > > > > > way to specify the exchange is, for me, to use tag 100. The  
> > > > > > > problem I’m facing is that, in FIX 4.2 specs, reuters code  
> > > > > > > related to Tokyo is T (Tokyo Stock Exchange), so I haven’t  
> > > > > > > any mean to dissociate these two markets.
> > > > > > > 
> > > > > > > I’m looking for a solution to differentiate TIFFE and TOCOM  
> > > > > > > with FIX field 100. I’ve look unsuccessfully for new reuters  
> > > > > > > code.
> > > > > > > 
> > > > > > > Has anybody an idea or a workaround to fix that ?
> > > > > > > 
> > > > > > > Thanks in advance.
> > > > > > 
> > > > > > Francois,
> > > > > > 
> > > > > > With agreement from your destinations, I would supplement the  
> > > > > > Reuters codes with ISO 10383 codes from the FIX 4.4 protocol  
> > > > > > specification document, or from
> > > > > > 
> > > > > > [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> > > > > > 
> > > > > > For example, the TIFFE is XTFF, and the commodities exchange  
> > > > > > is XTKT.
> > > > > > 
> > > > > > Hope this helps! Andrew
> > > > > 
> > > > > Many thanks for your answer. The problem is that I have to deal  
> > > > > with FIX 4.2 (so Reuters Code in FIX tag 100).
> > > > > 
> > > > > I found a link in other cases :  
> > > > > [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but don’t know if  
> > > > > these codes are official.
> > > > 
> > > > FIX 4.2 deals with the structure and semantics of the message; as  
> > > > far as I know there is nothing stopping you using ISO 10383 codes  
> > > > in 100 ExDestination on a FIX 4.2 message, beyond explicit  
> > > > agreement from your counterparties.
> > > > 
> > > > I’ve checked out this link. The CBOE code you reference conflicts  
> > > > with the FPL codes at:
> > > > 
> > > > [http://www.fixprotocol.org/specifications/exchanges.shtml](http://www.fixprotocol.org/specifications/exchanges.shtml)
> > > > 
> > > > and the code ‘CO’ points to the Copenhagen Stock Exchange.
> > > 
> > > You’re right concerning conflicts in the related link (there are  
> > > some other conflicts like ‘V’ for both USA index and Austria  
> > > Exchange).
> > > 
> > > Moreover, regarding to FIX 4.2 protocol, in FIX Field 100 for the  
> > > valid values, they made reference to Appendix C which lists all  
> > > valid Reuters Code. So client who wants to make FIX 4.2 will see  
> > > that and will logically want to use Reuters code. That’s the problem  
> > > I’m facing with.

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 12, 2007, 2:06pm UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/10 "2007-11-12T14:06:29Z")

</div>

[original email was from Francois Milot - [francois.milot@gltrade.com](mailto:francois.milot@gltrade.com) ]  
Great thanks. Very good news.

> Dear Francois,
> 
> We will be updating a full list of Reuters Exchange Codes on the FPL  
> website shortly. Meanwhile, we will add both Tokyo derivatives exchanges  
> codes to our list.
> 
> Thank you, FPL Program Office
> 
> > I appreciate a lot. It helps me a lot. How did you have such a code ?  
> > That will be helpful for me.
> > 
> > Regards,
> > 
> > > Hello,
> > > 
> > > If this is of any help:
> > > 
> > > Reuters Code for Tokyo Commodity Exchange is TCE
> > > 
> > > Reuters Code for Tokyo Financial Futures Exchange TFF
> > > 
> > > Regards
> > > 
> > > Ainhoa
> > > 
> > > > > > > > Hi all,
> > > > > > > > 
> > > > > > > > I’m facing a problem in FIX 4.2. I have to send orders on  
> > > > > > > > two markets which are TOCOM (Tokyo Commodities) and TIFFE  
> > > > > > > > (Tokyo International Financial Futures Exchange). The only  
> > > > > > > > way to specify the exchange is, for me, to use tag 100.  
> > > > > > > > The problem I’m facing is that, in FIX 4.2 specs, reuters  
> > > > > > > > code related to Tokyo is T (Tokyo Stock Exchange), so I  
> > > > > > > > haven’t any mean to dissociate these two markets.
> > > > > > > > 
> > > > > > > > I’m looking for a solution to differentiate TIFFE and  
> > > > > > > > TOCOM with FIX field 100. I’ve look unsuccessfully for new  
> > > > > > > > reuters code.
> > > > > > > > 
> > > > > > > > Has anybody an idea or a workaround to fix that ?
> > > > > > > > 
> > > > > > > > Thanks in advance.
> > > > > > > 
> > > > > > > Francois,
> > > > > > > 
> > > > > > > With agreement from your destinations, I would supplement  
> > > > > > > the Reuters codes with ISO 10383 codes from the FIX 4.4  
> > > > > > > protocol specification document, or from
> > > > > > > 
> > > > > > > [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> > > > > > > 
> > > > > > > For example, the TIFFE is XTFF, and the commodities exchange  
> > > > > > > is XTKT.
> > > > > > > 
> > > > > > > Hope this helps! Andrew
> > > > > > 
> > > > > > Many thanks for your answer. The problem is that I have to  
> > > > > > deal with FIX 4.2 (so Reuters Code in FIX tag 100).
> > > > > > 
> > > > > > I found a link in other cases :  
> > > > > > [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but don’t know  
> > > > > > if these codes are official.
> > > > > 
> > > > > FIX 4.2 deals with the structure and semantics of the message;  
> > > > > as far as I know there is nothing stopping you using ISO 10383  
> > > > > codes in 100 ExDestination on a FIX 4.2 message, beyond explicit  
> > > > > agreement from your counterparties.
> > > > > 
> > > > > I’ve checked out this link. The CBOE code you reference  
> > > > > conflicts with the FPL codes at:
> > > > > 
> > > > > [http://www.fixprotocol.org/specifications/exchanges.shtml](http://www.fixprotocol.org/specifications/exchanges.shtml)
> > > > > 
> > > > > and the code ‘CO’ points to the Copenhagen Stock Exchange.
> > > > 
> > > > You’re right concerning conflicts in the related link (there are  
> > > > some other conflicts like ‘V’ for both USA index and Austria  
> > > > Exchange).
> > > > 
> > > > Moreover, regarding to FIX 4.2 protocol, in FIX Field 100 for the  
> > > > valid values, they made reference to Appendix C which lists all  
> > > > valid Reuters Code. So client who wants to make FIX 4.2 will see  
> > > > that and will logically want to use Reuters code. That’s the  
> > > > problem I’m facing with.

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 12, 2007, 4:07pm UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/11 "2007-11-12T16:07:53Z")

</div>

[original email was from Francois Milot - [francois.milot@gltrade.com](mailto:francois.milot@gltrade.com) ]  
Can you please advise me when changes will be effective and where they are available (in FIX 4.2. technical spec in Appendix C ?) ?

Thanks in advance.

> Great thanks. Very good news.
> 
> > Dear Francois,
> > 
> > We will be updating a full list of Reuters Exchange Codes on the FPL  
> > website shortly. Meanwhile, we will add both Tokyo derivatives  
> > exchanges codes to our list.
> > 
> > Thank you, FPL Program Office
> > 
> > > I appreciate a lot. It helps me a lot. How did you have such a code  
> > > ? That will be helpful for me.
> > > 
> > > Regards,
> > > 
> > > > Hello,
> > > > 
> > > > If this is of any help:
> > > > 
> > > > Reuters Code for Tokyo Commodity Exchange is TCE
> > > > 
> > > > Reuters Code for Tokyo Financial Futures Exchange TFF
> > > > 
> > > > Regards
> > > > 
> > > > Ainhoa
> > > > 
> > > > > > > > > Hi all,
> > > > > > > > > 
> > > > > > > > > I’m facing a problem in FIX 4.2. I have to send orders  
> > > > > > > > > on two markets which are TOCOM (Tokyo Commodities) and  
> > > > > > > > > TIFFE (Tokyo International Financial Futures Exchange).  
> > > > > > > > > The only way to specify the exchange is, for me, to use  
> > > > > > > > > tag 100. The problem I’m facing is that, in FIX 4.2  
> > > > > > > > > specs, reuters code related to Tokyo is T (Tokyo Stock  
> > > > > > > > > Exchange), so I haven’t any mean to dissociate these two  
> > > > > > > > > markets.
> > > > > > > > > 
> > > > > > > > > I’m looking for a solution to differentiate TIFFE and  
> > > > > > > > > TOCOM with FIX field 100. I’ve look unsuccessfully for  
> > > > > > > > > new reuters code.
> > > > > > > > > 
> > > > > > > > > Has anybody an idea or a workaround to fix that ?
> > > > > > > > > 
> > > > > > > > > Thanks in advance.
> > > > > > > > 
> > > > > > > > Francois,
> > > > > > > > 
> > > > > > > > With agreement from your destinations, I would supplement  
> > > > > > > > the Reuters codes with ISO 10383 codes from the FIX 4.4  
> > > > > > > > protocol specification document, or from
> > > > > > > > 
> > > > > > > > [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> > > > > > > > 
> > > > > > > > For example, the TIFFE is XTFF, and the commodities  
> > > > > > > > exchange is XTKT.
> > > > > > > > 
> > > > > > > > Hope this helps! Andrew
> > > > > > > 
> > > > > > > Many thanks for your answer. The problem is that I have to  
> > > > > > > deal with FIX 4.2 (so Reuters Code in FIX tag 100).
> > > > > > > 
> > > > > > > I found a link in other cases :  
> > > > > > > [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but don’t know  
> > > > > > > if these codes are official.
> > > > > > 
> > > > > > FIX 4.2 deals with the structure and semantics of the message;  
> > > > > > as far as I know there is nothing stopping you using ISO 10383  
> > > > > > codes in 100 ExDestination on a FIX 4.2 message, beyond  
> > > > > > explicit agreement from your counterparties.
> > > > > > 
> > > > > > I’ve checked out this link. The CBOE code you reference  
> > > > > > conflicts with the FPL codes at:
> > > > > > 
> > > > > > [http://www.fixprotocol.org/specifications/exchanges.shtml](http://www.fixprotocol.org/specifications/exchanges.shtml)
> > > > > > 
> > > > > > and the code ‘CO’ points to the Copenhagen Stock Exchange.
> > > > > 
> > > > > You’re right concerning conflicts in the related link (there are  
> > > > > some other conflicts like ‘V’ for both USA index and Austria  
> > > > > Exchange).
> > > > > 
> > > > > Moreover, regarding to FIX 4.2 protocol, in FIX Field 100 for  
> > > > > the valid values, they made reference to Appendix C which lists  
> > > > > all valid Reuters Code. So client who wants to make FIX 4.2 will  
> > > > > see that and will logically want to use Reuters code. That’s the  
> > > > > problem I’m facing with.

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 12, 2007, 4:16pm UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/12 "2007-11-12T16:16:07Z")

</div>

[original email was from Francois Milot - [francois.milot@gltrade.com](mailto:francois.milot@gltrade.com) ]  
I have another need concerning always Reuters Code.

I need to send order on SGX Quest (Singapore Exchange, I found ) and SFE (Sydney Future Exchange) markets.

Regards,

> Can you please advise me when changes will be effective and where they  
> are available (in FIX 4.2. technical spec in Appendix C ?) ?
> 
> Thanks in advance.
> 
> > Great thanks. Very good news.
> > 
> > > Dear Francois,
> > > 
> > > We will be updating a full list of Reuters Exchange Codes on the FPL  
> > > website shortly. Meanwhile, we will add both Tokyo derivatives  
> > > exchanges codes to our list.
> > > 
> > > Thank you, FPL Program Office
> > > 
> > > > I appreciate a lot. It helps me a lot. How did you have such a  
> > > > code ? That will be helpful for me.
> > > > 
> > > > Regards,
> > > > 
> > > > > Hello,
> > > > > 
> > > > > If this is of any help:
> > > > > 
> > > > > Reuters Code for Tokyo Commodity Exchange is TCE
> > > > > 
> > > > > Reuters Code for Tokyo Financial Futures Exchange TFF
> > > > > 
> > > > > Regards
> > > > > 
> > > > > Ainhoa
> > > > > 
> > > > > > > > > > Hi all,
> > > > > > > > > > 
> > > > > > > > > > I’m facing a problem in FIX 4.2. I have to send orders  
> > > > > > > > > > on two markets which are TOCOM (Tokyo Commodities) and  
> > > > > > > > > > TIFFE (Tokyo International Financial Futures  
> > > > > > > > > > Exchange). The only way to specify the exchange is,  
> > > > > > > > > > for me, to use tag 100. The problem I’m facing is  
> > > > > > > > > > that, in FIX 4.2 specs, reuters code related to Tokyo  
> > > > > > > > > > is T (Tokyo Stock Exchange), so I haven’t any mean to  
> > > > > > > > > > dissociate these two markets.
> > > > > > > > > > 
> > > > > > > > > > I’m looking for a solution to differentiate TIFFE and  
> > > > > > > > > > TOCOM with FIX field 100. I’ve look unsuccessfully for  
> > > > > > > > > > new reuters code.
> > > > > > > > > > 
> > > > > > > > > > Has anybody an idea or a workaround to fix that ?
> > > > > > > > > > 
> > > > > > > > > > Thanks in advance.
> > > > > > > > > 
> > > > > > > > > Francois,
> > > > > > > > > 
> > > > > > > > > With agreement from your destinations, I would  
> > > > > > > > > supplement the Reuters codes with ISO 10383 codes from  
> > > > > > > > > the FIX 4.4 protocol specification document, or from
> > > > > > > > > 
> > > > > > > > > [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> > > > > > > > > 
> > > > > > > > > For example, the TIFFE is XTFF, and the commodities  
> > > > > > > > > exchange is XTKT.
> > > > > > > > > 
> > > > > > > > > Hope this helps! Andrew
> > > > > > > > 
> > > > > > > > Many thanks for your answer. The problem is that I have to  
> > > > > > > > deal with FIX 4.2 (so Reuters Code in FIX tag 100).
> > > > > > > > 
> > > > > > > > I found a link in other cases :  
> > > > > > > > [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but don’t  
> > > > > > > > know if these codes are official.
> > > > > > > 
> > > > > > > FIX 4.2 deals with the structure and semantics of the  
> > > > > > > message; as far as I know there is nothing stopping you  
> > > > > > > using ISO 10383 codes in 100 ExDestination on a FIX 4.2  
> > > > > > > message, beyond explicit agreement from your counterparties.
> > > > > > > 
> > > > > > > I’ve checked out this link. The CBOE code you reference  
> > > > > > > conflicts with the FPL codes at:
> > > > > > > 
> > > > > > > [http://www.fixprotocol.org/specifications/exchanges.shtml](http://www.fixprotocol.org/specifications/exchanges.shtml)
> > > > > > > 
> > > > > > > and the code ‘CO’ points to the Copenhagen Stock Exchange.
> > > > > > 
> > > > > > You’re right concerning conflicts in the related link (there  
> > > > > > are some other conflicts like ‘V’ for both USA index and  
> > > > > > Austria Exchange).
> > > > > > 
> > > > > > Moreover, regarding to FIX 4.2 protocol, in FIX Field 100 for  
> > > > > > the valid values, they made reference to Appendix C which  
> > > > > > lists all valid Reuters Code. So client who wants to make FIX  
> > > > > > 4.2 will see that and will logically want to use Reuters code.  
> > > > > > That’s the problem I’m facing with.

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 16, 2007, 10:34am UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/13 "2007-11-16T10:34:21Z")

</div>

[original email was from Francois Milot - [francois.milot@gltrade.com](mailto:francois.milot@gltrade.com) ]  
Hi guys, just want to know if Reuter’s code have been updated ?

Thanks in advance.

> I have another need concerning always Reuters Code.
> 
> I need to send order on SGX Quest (Singapore Exchange, I found ) and SFE  
> (Sydney Future Exchange) markets.
> 
> Regards,
> 
> > Can you please advise me when changes will be effective and where they  
> > are available (in FIX 4.2. technical spec in Appendix C ?) ?
> > 
> > Thanks in advance.
> > 
> > > Great thanks. Very good news.
> > > 
> > > > Dear Francois,
> > > > 
> > > > We will be updating a full list of Reuters Exchange Codes on the  
> > > > FPL website shortly. Meanwhile, we will add both Tokyo derivatives  
> > > > exchanges codes to our list.
> > > > 
> > > > Thank you, FPL Program Office
> > > > 
> > > > > I appreciate a lot. It helps me a lot. How did you have such a  
> > > > > code ? That will be helpful for me.
> > > > > 
> > > > > Regards,
> > > > > 
> > > > > > Hello,
> > > > > > 
> > > > > > If this is of any help:
> > > > > > 
> > > > > > Reuters Code for Tokyo Commodity Exchange is TCE
> > > > > > 
> > > > > > Reuters Code for Tokyo Financial Futures Exchange TFF
> > > > > > 
> > > > > > Regards
> > > > > > 
> > > > > > Ainhoa
> > > > > > 
> > > > > > > > > > > Hi all,
> > > > > > > > > > > 
> > > > > > > > > > > I’m facing a problem in FIX 4.2. I have to send  
> > > > > > > > > > > orders on two markets which are TOCOM (Tokyo  
> > > > > > > > > > > Commodities) and TIFFE (Tokyo International  
> > > > > > > > > > > Financial Futures Exchange). The only way to specify  
> > > > > > > > > > > the exchange is, for me, to use tag 100. The problem  
> > > > > > > > > > > I’m facing is that, in FIX 4.2 specs, reuters code  
> > > > > > > > > > > related to Tokyo is T (Tokyo Stock Exchange), so I  
> > > > > > > > > > > haven’t any mean to dissociate these two markets.
> > > > > > > > > > > 
> > > > > > > > > > > I’m looking for a solution to differentiate TIFFE  
> > > > > > > > > > > and TOCOM with FIX field 100. I’ve look  
> > > > > > > > > > > unsuccessfully for new reuters code.
> > > > > > > > > > > 
> > > > > > > > > > > Has anybody an idea or a workaround to fix that ?
> > > > > > > > > > > 
> > > > > > > > > > > Thanks in advance.
> > > > > > > > > > 
> > > > > > > > > > Francois,
> > > > > > > > > > 
> > > > > > > > > > With agreement from your destinations, I would  
> > > > > > > > > > supplement the Reuters codes with ISO 10383 codes from  
> > > > > > > > > > the FIX 4.4 protocol specification document, or from
> > > > > > > > > > 
> > > > > > > > > > [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> > > > > > > > > > 
> > > > > > > > > > For example, the TIFFE is XTFF, and the commodities  
> > > > > > > > > > exchange is XTKT.
> > > > > > > > > > 
> > > > > > > > > > Hope this helps! Andrew
> > > > > > > > > 
> > > > > > > > > Many thanks for your answer. The problem is that I have  
> > > > > > > > > to deal with FIX 4.2 (so Reuters Code in FIX tag 100).
> > > > > > > > > 
> > > > > > > > > I found a link in other cases :  
> > > > > > > > > [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but don’t  
> > > > > > > > > know if these codes are official.
> > > > > > > > 
> > > > > > > > FIX 4.2 deals with the structure and semantics of the  
> > > > > > > > message; as far as I know there is nothing stopping you  
> > > > > > > > using ISO 10383 codes in 100 ExDestination on a FIX 4.2  
> > > > > > > > message, beyond explicit agreement from your  
> > > > > > > > counterparties.
> > > > > > > > 
> > > > > > > > I’ve checked out this link. The CBOE code you reference  
> > > > > > > > conflicts with the FPL codes at:
> > > > > > > > 
> > > > > > > > [http://www.fixprotocol.org/specifications/exchanges.shtml](http://www.fixprotocol.org/specifications/exchanges.shtml)
> > > > > > > > 
> > > > > > > > and the code ‘CO’ points to the Copenhagen Stock Exchange.
> > > > > > > 
> > > > > > > You’re right concerning conflicts in the related link (there  
> > > > > > > are some other conflicts like ‘V’ for both USA index and  
> > > > > > > Austria Exchange).
> > > > > > > 
> > > > > > > Moreover, regarding to FIX 4.2 protocol, in FIX Field 100  
> > > > > > > for the valid values, they made reference to Appendix C  
> > > > > > > which lists all valid Reuters Code. So client who wants to  
> > > > > > > make FIX  
> > > > > > > 4.2 will see that and will logically want to use Reuters  
> > > > > > > code. That’s the problem I’m facing with.

---

<div class="post-metadata">

**Author:** ![fp\_x](https://avatars.discourse-cdn.com/v4/letter/f/9de0a6/32.png) [@fp\_x](https://forum.fixtrading.org/u/fp_x)\
**Post date:** [November 16, 2007, 2:19pm UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/14 "2007-11-16T14:19:28Z")

</div>

Hi Francois,

For a list of Reuters codes, this page [http://fixprotocol.org/specifications/exchanges.shtml](http://fixprotocol.org/specifications/exchanges.shtml) is a more up to date source than the spec.

The Tokyo codes have been updated, as well as the Sydney Futures Exchange and Singapore Quest (under Singapore Derivatives Exchange)

Thank you,  
FPL Program Office

> Hi guys, just want to know if Reuter’s code have been updated ?
> 
> Thanks in advance.
> 
> > I have another need concerning always Reuters Code.
> > 
> > I need to send order on SGX Quest (Singapore Exchange, I found ) and  
> > SFE (Sydney Future Exchange) markets.
> > 
> > Regards,
> > 
> > > Can you please advise me when changes will be effective and where  
> > > they are available (in FIX 4.2. technical spec in Appendix C ?) ?
> > > 
> > > Thanks in advance.
> > > 
> > > > Great thanks. Very good news.
> > > > 
> > > > > Dear Francois,
> > > > > 
> > > > > We will be updating a full list of Reuters Exchange Codes on the  
> > > > > FPL website shortly. Meanwhile, we will add both Tokyo  
> > > > > derivatives exchanges codes to our list.
> > > > > 
> > > > > Thank you, FPL Program Office
> > > > > 
> > > > > > I appreciate a lot. It helps me a lot. How did you have such a  
> > > > > > code ? That will be helpful for me.
> > > > > > 
> > > > > > Regards,
> > > > > > 
> > > > > > > Hello,
> > > > > > > 
> > > > > > > If this is of any help:
> > > > > > > 
> > > > > > > Reuters Code for Tokyo Commodity Exchange is TCE
> > > > > > > 
> > > > > > > Reuters Code for Tokyo Financial Futures Exchange TFF
> > > > > > > 
> > > > > > > Regards
> > > > > > > 
> > > > > > > Ainhoa
> > > > > > > 
> > > > > > > > > > > > Hi all,
> > > > > > > > > > > > 
> > > > > > > > > > > > I’m facing a problem in FIX 4.2. I have to send  
> > > > > > > > > > > > orders on two markets which are TOCOM (Tokyo  
> > > > > > > > > > > > Commodities) and TIFFE (Tokyo International  
> > > > > > > > > > > > Financial Futures Exchange). The only way to  
> > > > > > > > > > > > specify the exchange is, for me, to use tag 100.  
> > > > > > > > > > > > The problem I’m facing is that, in FIX 4.2 specs,  
> > > > > > > > > > > > reuters code related to Tokyo is T (Tokyo Stock  
> > > > > > > > > > > > Exchange), so I haven’t any mean to dissociate  
> > > > > > > > > > > > these two markets.
> > > > > > > > > > > > 
> > > > > > > > > > > > I’m looking for a solution to differentiate TIFFE  
> > > > > > > > > > > > and TOCOM with FIX field 100. I’ve look  
> > > > > > > > > > > > unsuccessfully for new reuters code.
> > > > > > > > > > > > 
> > > > > > > > > > > > Has anybody an idea or a workaround to fix that ?
> > > > > > > > > > > > 
> > > > > > > > > > > > Thanks in advance.
> > > > > > > > > > > 
> > > > > > > > > > > Francois,
> > > > > > > > > > > 
> > > > > > > > > > > With agreement from your destinations, I would  
> > > > > > > > > > > supplement the Reuters codes with ISO 10383 codes  
> > > > > > > > > > > from the FIX 4.4 protocol specification document, or  
> > > > > > > > > > > from
> > > > > > > > > > > 
> > > > > > > > > > > [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> > > > > > > > > > > 
> > > > > > > > > > > For example, the TIFFE is XTFF, and the commodities  
> > > > > > > > > > > exchange is XTKT.
> > > > > > > > > > > 
> > > > > > > > > > > Hope this helps! Andrew
> > > > > > > > > > 
> > > > > > > > > > Many thanks for your answer. The problem is that I  
> > > > > > > > > > have to deal with FIX 4.2 (so Reuters Code in FIX tag  
> > > > > > > > > > 100).
> > > > > > > > > > 
> > > > > > > > > > I found a link in other cases :  
> > > > > > > > > > [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but  
> > > > > > > > > > don’t know if these codes are official.
> > > > > > > > > 
> > > > > > > > > FIX 4.2 deals with the structure and semantics of the  
> > > > > > > > > message; as far as I know there is nothing stopping you  
> > > > > > > > > using ISO 10383 codes in 100 ExDestination on a FIX 4.2  
> > > > > > > > > message, beyond explicit agreement from your  
> > > > > > > > > counterparties.
> > > > > > > > > 
> > > > > > > > > I’ve checked out this link. The CBOE code you reference  
> > > > > > > > > conflicts with the FPL codes at:
> > > > > > > > > 
> > > > > > > > > [http://www.fixprotocol.org/specifications/exchanges.sht-](http://www.fixprotocol.org/specifications/exchanges.sht-)  
> > > > > > > > > ml
> > > > > > > > > 
> > > > > > > > > and the code ‘CO’ points to the Copenhagen Stock  
> > > > > > > > > Exchange.
> > > > > > > > 
> > > > > > > > You’re right concerning conflicts in the related link  
> > > > > > > > (there are some other conflicts like ‘V’ for both USA  
> > > > > > > > index and Austria Exchange).
> > > > > > > > 
> > > > > > > > Moreover, regarding to FIX 4.2 protocol, in FIX Field 100  
> > > > > > > > for the valid values, they made reference to Appendix C  
> > > > > > > > which lists all valid Reuters Code. So client who wants to  
> > > > > > > > make FIX  
> > > > > > > > 4.2 will see that and will logically want to use Reuters  
> > > > > > > > code. That’s the problem I’m facing with.

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 19, 2007, 10:49am UTC](https://forum.fixtrading.org/t/how-to-dissociate-japanese-exchange-with-reuters-code-in-fix-4-2/2340/15 "2007-11-19T10:49:28Z")

</div>

[original email was from Francois Milot - [francois.milot@gltrade.com](mailto:francois.milot@gltrade.com) ]  
Thanks a lot. We will be able to provide to our client these codes.

Regards,

> Hi Francois,
> 
> For a list of Reuters codes, this page  
> [http://fixprotocol.org/specifications/exchanges.shtml](http://fixprotocol.org/specifications/exchanges.shtml) is a more up to  
> date source than the spec.
> 
> The Tokyo codes have been updated, as well as the Sydney Futures  
> Exchange and Singapore Quest (under Singapore Derivatives Exchange)
> 
> Thank you, FPL Program Office
> 
> > Hi guys, just want to know if Reuter’s code have been updated ?
> > 
> > Thanks in advance.
> > 
> > > I have another need concerning always Reuters Code.
> > > 
> > > I need to send order on SGX Quest (Singapore Exchange, I found ) and  
> > > SFE (Sydney Future Exchange) markets.
> > > 
> > > Regards,
> > > 
> > > > Can you please advise me when changes will be effective and where  
> > > > they are available (in FIX 4.2. technical spec in Appendix C ?) ?
> > > > 
> > > > Thanks in advance.
> > > > 
> > > > > Great thanks. Very good news.
> > > > > 
> > > > > > Dear Francois,
> > > > > > 
> > > > > > We will be updating a full list of Reuters Exchange Codes on  
> > > > > > the FPL website shortly. Meanwhile, we will add both Tokyo  
> > > > > > derivatives exchanges codes to our list.
> > > > > > 
> > > > > > Thank you, FPL Program Office
> > > > > > 
> > > > > > > I appreciate a lot. It helps me a lot. How did you have such  
> > > > > > > a code ? That will be helpful for me.
> > > > > > > 
> > > > > > > Regards,
> > > > > > > 
> > > > > > > > Hello,
> > > > > > > > 
> > > > > > > > If this is of any help:
> > > > > > > > 
> > > > > > > > Reuters Code for Tokyo Commodity Exchange is TCE
> > > > > > > > 
> > > > > > > > Reuters Code for Tokyo Financial Futures Exchange TFF
> > > > > > > > 
> > > > > > > > Regards
> > > > > > > > 
> > > > > > > > Ainhoa
> > > > > > > > 
> > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > > 
> > > > > > > > > > > > > I’m facing a problem in FIX 4.2. I have to send  
> > > > > > > > > > > > > orders on two markets which are TOCOM (Tokyo  
> > > > > > > > > > > > > Commodities) and TIFFE (Tokyo International  
> > > > > > > > > > > > > Financial Futures Exchange). The only way to  
> > > > > > > > > > > > > specify the exchange is, for me, to use tag 100.  
> > > > > > > > > > > > > The problem I’m facing is that, in FIX 4.2  
> > > > > > > > > > > > > specs, reuters code related to Tokyo is T (Tokyo  
> > > > > > > > > > > > > Stock Exchange), so I haven’t any mean to  
> > > > > > > > > > > > > dissociate these two markets.
> > > > > > > > > > > > > 
> > > > > > > > > > > > > I’m looking for a solution to differentiate  
> > > > > > > > > > > > > TIFFE and TOCOM with FIX field 100. I’ve look  
> > > > > > > > > > > > > unsuccessfully for new reuters code.
> > > > > > > > > > > > > 
> > > > > > > > > > > > > Has anybody an idea or a workaround to fix that  
> > > > > > > > > > > > > ?
> > > > > > > > > > > > > 
> > > > > > > > > > > > > Thanks in advance.
> > > > > > > > > > > > 
> > > > > > > > > > > > Francois,
> > > > > > > > > > > > 
> > > > > > > > > > > > With agreement from your destinations, I would  
> > > > > > > > > > > > supplement the Reuters codes with ISO 10383 codes  
> > > > > > > > > > > > from the FIX 4.4 protocol specification document,  
> > > > > > > > > > > > or from
> > > > > > > > > > > > 
> > > > > > > > > > > > [http://www.mddl.org/ext/scheme/iso10383.asp](http://www.mddl.org/ext/scheme/iso10383.asp)
> > > > > > > > > > > > 
> > > > > > > > > > > > For example, the TIFFE is XTFF, and the  
> > > > > > > > > > > > commodities exchange is XTKT.
> > > > > > > > > > > > 
> > > > > > > > > > > > Hope this helps! Andrew
> > > > > > > > > > > 
> > > > > > > > > > > Many thanks for your answer. The problem is that I  
> > > > > > > > > > > have to deal with FIX 4.2 (so Reuters Code in FIX  
> > > > > > > > > > > tag  
> > > > > > > > > > > 100).
> > > > > > > > > > > 
> > > > > > > > > > > I found a link in other cases :  
> > > > > > > > > > > [http://channel.bridge.com/bc/webhelp/EXCH.htm](http://channel.bridge.com/bc/webhelp/EXCH.htm) but  
> > > > > > > > > > > don’t know if these codes are official.
> > > > > > > > > > 
> > > > > > > > > > FIX 4.2 deals with the structure and semantics of the  
> > > > > > > > > > message; as far as I know there is nothing stopping  
> > > > > > > > > > you using ISO 10383 codes in 100 ExDestination on a  
> > > > > > > > > > FIX 4.2 message, beyond explicit agreement from your  
> > > > > > > > > > counterparties.
> > > > > > > > > > 
> > > > > > > > > > I’ve checked out this link. The CBOE code you  
> > > > > > > > > > reference conflicts with the FPL codes at:
> > > > > > > > > > 
> > > > > > > > > > tp://www.fixprotocol.org/specifications/exchanges.sht-  
> > > > > > > > > > ml
> > > > > > > > > > 
> > > > > > > > > > and the code ‘CO’ points to the Copenhagen Stock  
> > > > > > > > > > Exchange.
> > > > > > > > > 
> > > > > > > > > You’re right concerning conflicts in the related link  
> > > > > > > > > (there are some other conflicts like ‘V’ for both USA  
> > > > > > > > > index and Austria Exchange).
> > > > > > > > > 
> > > > > > > > > Moreover, regarding to FIX 4.2 protocol, in FIX Field  
> > > > > > > > > 100 for the valid values, they made reference to  
> > > > > > > > > Appendix C which lists all valid Reuters Code. So client  
> > > > > > > > > who wants to make FIX  
> > > > > > > > > 4.2 will see that and will logically want to use Reuters  
> > > > > > > > > code. That’s the problem I’m facing with.
