Imported from previous forum
[ original email was from Francois Milot - 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.
[ original email was from Andrew Scott - 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
For example, the TIFFE is XTFF, and the commodities exchange is XTKT.
Hope this helps!
Andrew
[ original email was from Francois Milot - 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 fromhttp://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 but don’t know if these codes are official.
[ original email was from Andrew Scott - 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 fromhttp://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 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
and the code ‘CO’ points to the Copenhagen Stock Exchange.
[ original email was from Francois Milot - 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 fromhttp://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 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
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.
[ original email was from Ainhoa Dewisme - 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 fromhttp://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 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
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.
[ original email was from Francois Milot - 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 fromhttp://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 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
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.
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 fromhttp://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 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
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.
[ original email was from Francois Milot - 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 fromhttp://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 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
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.
[ original email was from Francois Milot - 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 fromhttp://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 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
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.
[ original email was from Francois Milot - 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 fromhttp://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 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
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.
[ original email was from Francois Milot - 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 fromhttp://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 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
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.
Hi Francois,
For a list of Reuters codes, this page 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
fromhttp://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 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-
mland 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.
[ original email was from Francois Milot - 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 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 fromhttp://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 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-
mland 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.