FIX 4.4 structure vs FIX 4.2

, ,
1

Imported from previous forum

2

Hi All,

We have recntly required a job request for a developer with FIX 4.4 knowledge. Is there much difference between the structure of 4.4 and 4.2?

Regards,

Karl

3

[ original email was from Harish Kamaley - harish.kamaley@wipro.com ]
Hi Karl,

FIX 4.4 has better functionality support than FIX version 4.2.
Pls go through the below URL for your reference.
http://www.fixprotocol.org/functionality

Thanks & Regards,
Harish.

4

Thanks Harish

Hi Karl,

FIX 4.4 has better functionality support than FIX version 4.2. Pls go
through the below URL for your reference.
http://www.fixprotocol.org/functionality

Thanks & Regards, Harish.

5

I would say yes. Quite a few things have changed between those versions, e.g. the Parties component block did not exist in FIX 4.2. I would suggest to read the release notes of FIX 4.3 and FIX 4.4 to get an impression of what changes there are.

Regards,
Hanno.

Hi All,

We have recntly required a job request for a developer with FIX
4.4 knowledge. Is there much difference between the structure of
4.4 and 4.2?

Regards,

Karl

6

Many thanks Hanno.

I would say yes. Quite a few things have changed between those versions,

e.g. the Parties component block did not exist in FIX 4.2. I would
suggest to read the release notes of FIX 4.3 and FIX 4.4 to get an
impression of what changes there are.

Regards, Hanno.

Hi All,

We have recntly required a job request for a developer with FIX
4.4 knowledge. Is there much difference between the structure of
4.4 and 4.2?

Regards,

Karl

7

Hello!

From my poing of view - if you have working application for 4.2 it is simple move it to 4.4. From my experience: we just spend several days on that migration.

For funcional point of view 4.4 is more reach and interesting. Your experience in 4.2 will be very useful.

Serg Gulko

Hi All,

We have recntly required a job request for a developer with FIX
4.4 knowledge. Is there much difference between the structure of
4.4 and 4.2?

Regards,

Karl

8

Hello!

From my poing of view - if you have working application for 4.2 it is
simple move it to 4.4. From my experience: we just spend several days on
that migration.

For funcional point of view 4.4 is more reach and interesting. Your
experience in 4.2 will be very useful.

Serg Gulko

Hi All,

We have recntly required a job request for a developer with FIX
4.4 knowledge. Is there much difference between the structure of
4.4 and 4.2?

Regards,

Karl

The most important change is implementation of MIC codes in FIX 4.4 version.

207=T becomes 207=XTKS

please check this is important.

9

I disagree with the assessment below. FIX 4.2 already defines 207 as datatype “Exchange”, i.e. a MIC. Also, a change of reference from one code list to another is something trivial and does no justice to the significant conceptual changes between 4.2 and 4.4. These are for example the introduction of the Parties component block and the deprecation of ExecTransType and related changes to ExecType and OrdStatus.

I can only strongly recommend to read FIX 4.3 and FIX 4.4 Volume 6 Appendix 6-E, 6-F and 6-G as well as the FIX 4.4 Release Notes to find out what really changed between FIX 4.2 and FIX 4.4.

Regards,
Hanno.

The most important change is implementation of MIC codes in FIX
4.4 version.

207=T becomes 207=XTKS

please check this is important.

10

I disagree with the assessment below. FIX 4.2 already defines 207 as
datatype “Exchange”, i.e. a MIC. Also, a change of reference from one
code list to another is something trivial and does no justice to the
significant conceptual changes between 4.2 and 4.4. These are for
example the introduction of the Parties component block and the
deprecation of ExecTransType and related changes to ExecType and
OrdStatus.

I can only strongly recommend to read FIX 4.3 and FIX 4.4 Volume 6
Appendix 6-E, 6-F and 6-G as well as the FIX 4.4 Release Notes to find
out what really changed between FIX 4.2 and FIX 4.4.

Regards, Hanno.

The most important change is implementation of MIC codes in FIX
4.4 version.

207=T becomes 207=XTKS

please check this is important.

Hi market Identifier codes(MIC) is a four character code used to specify exchanges.
How FIX.4.2 uses 207=T for tokyo and 4.4 onwards we have to give 207=XTKS, if no implementation change at technical level.
Offcourse at business level they both means same used to identify market.