Utilization of the exchange code standard - 4.2 & 4.3

, ,
1

Imported from previous forum

2

The FIX connectivity implementation scheduled at WSE for this year is based on 4.2 version of FIX.

The FIX specification standard for exchange codes changed from Reuters exchange suffix in 4.2 to ISO 10383 MIC codes in 4.3.

As far as the MIC code for the Warsaw Stock Exchange is concerned the appendix 6-C of 4.4 defines it as XWAR. Since the Warsaw Stock Exchange is not listed in the 4.2 appendix C should the Ruters suffix (which appears to be .WA) be still utilized or should MIC code be used instead?

3

The FIX connectivity implementation scheduled at WSE for this year is
based on 4.2 version of FIX.

The FIX specification standard for exchange codes changed from Reuters
exchange suffix in 4.2 to ISO 10383 MIC codes in 4.3.

As far as the MIC code for the Warsaw Stock Exchange is concerned the
appendix 6-C of 4.4 defines it as XWAR. Since the Warsaw Stock Exchange
is not listed in the 4.2 appendix C should the Ruters suffix (which
appears to be .WA) be still utilized or should MIC code be used instead?

Hi Jurek,

did you see the link

http://www.fixprotocol.org/specifications/ex_other.shtml

which provides numeric values for all exchanges not listed in the Reuters mnemonics? Perhaps you should request to get a numeric value assigned for the Warsaw Stock Exchange.

Cheers, Jörg

4

Hi Jörg,
Thanks for the link. As it seems that Reuters apply .WA extension to the RIC codes of the stocks traded at WSE should we ask that the appendix C of 4.2 is amended to reflect it?
Regards,
Jurek

The FIX connectivity implementation scheduled at WSE for this year is

based on 4.2 version of FIX.

The FIX specification standard for exchange codes changed from Reuters
exchange suffix in 4.2 to ISO 10383 MIC codes in 4.3.

As far as the MIC code for the Warsaw Stock Exchange is concerned the
appendix 6-C of 4.4 defines it as XWAR. Since the Warsaw Stock
Exchange is not listed in the 4.2 appendix C should the Ruters suffix
(which appears to be .WA) be still utilized or should MIC code be used
instead?

Hi Jurek,

did you see the link

http://www.fixprotocol.org/specifications/ex_other.shtml

which provides numeric values for all exchanges not listed in the
Reuters mnemonics? Perhaps you should request to get a numeric value
assigned for the Warsaw Stock Exchange.

Cheers, Jörg

5

As it seems that Reuters apply .WA
extension to the RIC codes of the stocks traded at WSE should we ask
that the appendix C of 4.2 is amended to reflect it? Regards, Jurek

Hi Jurek,

I think they wont update the FIX 4.2 spec, but perhaps add it to the exchange section on the specification page on this web site. Actually I do not know who to ask. From e-mail contact I happen to know Scott Atwell; he probably knows how the procedure is.

Cheers, Jörg

6

[ original email was from Chris Pickles - chris.pickles@radianz.com ]
> > As it seems that Reuters apply .WA extension to the RIC codes of the

stocks traded at WSE should we ask that the appendix C of 4.2 is
amended to reflect it? Regards, Jurek

Hi Jurek,

I think they wont update the FIX 4.2 spec, but perhaps add it to the
exchange section on the specification page on this web site. Actually I
do not know who to ask. From e-mail contact I happen to know Scott
Atwell; he probably knows how the procedure is.

Cheers, Jörg

It might be worth checking with Reuters. It may be that the Reuters codes are considered as proprietary by Reuters. If this were the case, some other vendors that compete against Reuters might not like an industry standard to include vendor-proprietary coding systems.
Regards
Chris

7

Per FIX 4.3 Specification:

As of FIX 4.3, Exchange Codes used in FIX are those defined in ISO 10383 standard: Market Identifier Code (MIC). The cross-reference list below is a subset of ISO 10383 values as of the time of this publication. It is provided to facilitate the transition from the Reuters exchange suffix codes which versions of FIX prior to FIX 4.2 were based upon. The official standard and set of values are maintained by the ISO 10383 standard and any discrepancies below should be considered typographical errors using the ISO 10383 standard as the correct set of values. To obtain the current valid list please contact the ISO 10383 secretariat (see “Appendix 6-B”) and/or visit the ISO website at http://www.iso.ch

Note that “Old FIX 4.2” values which are underlined represent “numeric codes” assigned by the FIX organization in lieu of a valid Reuters exchange suffix. Such values which have a valid MIC value should use the MIC value. Markets without a MIC value should apply to the ISO 10383 Registration Authority (SWIFT) for an appropriate value. The FIX organization will maintain numeric values for required market identifiers which are unable to establish a MIC value for some reason.

Regards
Ross

As it seems that Reuters apply .WA extension to the RIC codes of the
stocks traded at WSE should we ask that the appendix C of 4.2 is
amended to reflect it? Regards, Jurek

Hi Jurek,

I think they wont update the FIX 4.2 spec, but perhaps add it to the
exchange section on the specification page on this web site. Actually
I do not know who to ask. From e-mail contact I happen to know Scott
Atwell; he probably knows how the procedure is.

Cheers, Jörg

It might be worth checking with Reuters. It may be that the Reuters
codes are considered as proprietary by Reuters. If this were the case,
some other vendors that compete against Reuters might not like an
industry standard to include vendor-proprietary coding systems.
Regards Chris