ISO or MICs for Market Makers

, ,
1

Imported from previous forum

2

Does anyone know if there is any pseudo standard ISOs or FIX (Reuters)Exchange Mnemonics (i.e. 2 digit values) for Market Makers? Reuters Exchange Mnemonics would obviously be used for FIX 4.2?

3

I am not aware of any pseudo values for market makers and do not think this is the right approach. Which field(s) do you want to populate with such a code?

You talk about FIX 4.2 so that you do not have a Parties block (as of FIX 4.3) which offers you PartyRole 66=Market Maker. PartyID then can carry a value of bilateral agreement (PartyIDSource=D=Custom) or a BIC (PartyIDSource=B).

You might have to work with TargetSubID (57) in FIX 4.2 because ExDestination (100) is of data type Exchange.

Does anyone know if there is any pseudo standard ISOs or FIX
(Reuters)Exchange Mnemonics (i.e. 2 digit values) for Market Makers?
Reuters Exchange Mnemonics would obviously be used for FIX 4.2?

4

Thank you. That is what I’m referring too. We are intending to utilize TargetSubID in 4.2. We also allow ExDest(100) as an identifying destination. I was just curious if there were any 2 letter or MIC/ISO type codes that people were using for Market Makers other than the 4 letter identifiers.

I am not aware of any pseudo values for market makers and do not think
this is the right approach. Which field(s) do you want to populate with
such a code?

You talk about FIX 4.2 so that you do not have a Parties block (as of
FIX 4.3) which offers you PartyRole 66=Market Maker. PartyID then can
carry a value of bilateral agreement (PartyIDSource=D=Custom) or a BIC
(PartyIDSource=B).

You might have to work with TargetSubID (57) in FIX 4.2 because
ExDestination (100) is of data type Exchange.

Does anyone know if there is any pseudo standard ISOs or FIX
(Reuters)Exchange Mnemonics (i.e. 2 digit values) for Market Makers?
Reuters Exchange Mnemonics would obviously be used for FIX 4.2?