LastMkt

, ,
1

Imported from previous forum

2

[ original email was from Peter Lespasio - peter.lespasio@tfn.com ]
In the case of a broker currently using FIX 4.0, would it be considered valid for them to send an exeuction with LastMkt (FIX tag 30) with a value of 13? Is it foolish to interpret the FIX 4.0 spec, as it currently is written, for the LastMkt field to be only values listed in Appendix C (Reuters Exchange Mnemonics), which a value of 13 was not valid at the time. Or is it more logical to utilize this field as the current Reuters Exchange Mnemonic list (for which a value of tag 13 is valid today)?

3

[ original email was from Keith Olivares - kolivares@javtech.com ]
Greetings,

IMHO, it wouldn’t be wise just to limit yourself to the values for LastMkt listed in the FIX 4.0 spec. Just like Symbol, the values for these change. Even if you are just using FIX 4.0, you should be using the latest Reuters Exchange Mnemonics and so should your counter-parties.

Regards,

Keith Olivares

> In the case of a broker currently using FIX 4.0, would it be considered valid for them to send an exeuction with LastMkt (FIX tag 30) with a value of 13? Is it foolish to interpret the FIX 4.0 spec, as it currently is written, for the LastMkt field to be only values listed in Appendix C (Reuters Exchange Mnemonics), which a value of 13 was not valid at the time. Or is it more logical to utilize this field as the current Reuters Exchange Mnemonic list (for which a value of tag 13 is valid today)?
>

4

> In the case of a broker currently using FIX 4.0, would it be considered valid for them to send an exeuction with LastMkt (FIX tag 30) with a value of 13? Is it foolish to interpret the FIX 4.0 spec, as it currently is written, for the LastMkt field to be only values listed in Appendix C (Reuters Exchange Mnemonics), which a value of 13 was not valid at the time. Or is it more logical to utilize this field as the current Reuters Exchange Mnemonic list (for which a value of tag 13 is valid today)?
>
Practically speaking, if you’re with 4.0 for a session
and forced to use some 4.1/4.2 values for that,
you have no choice. However, it all depends how rigid
is your engine in terms of validating enumeration
values for the fields. Engines/handler (4.0) may
allow addition of custom values for different fields
including LastMkt. And that’s exactly what we have done
in similar case as you have asked. We’ve even added
Non Reuters Exchange Mnemonics values for our own
internal purposes!