EXDestionation value (Tag 100) for Fix 4.2

, ,
1

Imported from previous forum

2

Greetings

What EXDestionation value (Tag 100) is used for Fix 4.2 for following exchange/trading systems :

1> PURE-CNQ EXCHANGE
2> ALPHA EXCHANGE

Appreciate your response.

3

Greetings

What EXDestionation value (Tag 100) is used for Fix 4.2 for following
exchange/trading systems :

1> PURE-CNQ EXCHANGE
2> ALPHA EXCHANGE

Appreciate your response.

Hey i beleive in the cases where the ExDestination is not mentioned in the Protocol version you can choose any value confirm your counterparty and if you are a roker side do the changes in your configs for that or ask the vendor to support that ( convert the required for client) .
This can be handled at application level

4

[ original email was from Ryan Pierce (FPL Technical Director) - ryan.pierce@fixprotocol.org ]
> Hey i beleive in the cases where the ExDestination is not mentioned in

the Protocol version you can choose any value confirm your counterparty
and if you are a roker side do the changes in your configs for that or
ask the vendor to support that ( convert the required for client) . This
can be handled at application level

No, this is incorrect.

In FIX 4.2 and below, ExDestination used proprietary alphabetic Reuters codes, as well as codes assigned by FPL. You can view them here:

http://fixprotocol.org/specifications/exchanges.shtml

Note there are two tabs, one for Reuters codes, and one for FPL-assigned values.

I don’t see anything assigned for Alpha or Pure.

The exchanges themselves can request codes from FPL. Please ask your contacts at the exchange to mail fpl@fixprotocol.org and ask that a code be assigned. FPL will then assign one.

Note that in later versions of the protocol (4.4, and, I think, 4.3) these values are obsolete, and ISO 10383 MIC codes are used. Information and a link to request them is here:

http://www.iso15022.org/MIC/homepageMIC.htm

5

[ original email was from John Greenan - john.greenan@alignment-systems.com ]
In most cases brokers will accept ISO MICs in FIX 4.2 messages.

Hey i beleive in the cases where the ExDestination is not mentioned in
the Protocol version you can choose any value confirm your
counterparty and if you are a roker side do the changes in your
configs for that or ask the vendor to support that ( convert the
required for client) . This can be handled at application level

No, this is incorrect.

In FIX 4.2 and below, ExDestination used proprietary alphabetic Reuters
codes, as well as codes assigned by FPL. You can view them here:

http://fixprotocol.org/specifications/exchanges.shtml

Note there are two tabs, one for Reuters codes, and one for FPL-
assigned values.

I don’t see anything assigned for Alpha or Pure.

The exchanges themselves can request codes from FPL. Please ask your
contacts at the exchange to mail fpl@fixprotocol.org and ask that a code
be assigned. FPL will then assign one.

Note that in later versions of the protocol (4.4, and, I think, 4.3)
these values are obsolete, and ISO 10383 MIC codes are used. Information
and a link to request them is here:

http://www.iso15022.org/MIC/homepageMIC.htm