Imported from previous forum
[ original email was from Sarah Hoff - hoffs@stifel.com ]
Hi,
I have a vendor ITG TRITON who is an FIX Protocol Limited Partner. Who is mandating that I use/support tag 97 on 4.2. My OMS will NOT support this NOR is it a FIX standard. How do you nicely explain the rules to a FPL?
Thanks.
SWH
PossResend Tag 97=Y is required when a FIX message has been already sent earlier and is being retransmitted with a different sequence number in this message.
There is no harm in 97=N present in original transmissions, but it serves no purpose other than to assert that it is a original send and is not a retransmission. I do not see any reason to mandate its presence in original transmissions because as per FIXProtocol, its optional in original transmissions.
How to “nicely” explain the rule ? If you are sending them a paper / printed reply, maybe you can send it with a box of choclates and a nice greeting card. If you are sending them an email, you could attach a cookie jar (enable cookies in your internet browser, then copy all the cookie files to a folder and create a java archive file), dont forget to add many 
Hi,
I have a vendor ITG TRITON who is an FIX Protocol Limited Partner.
Who is mandating that I use/support tag 97 on 4.2. My OMS will NOT
support this NOR is it a FIX standard. How do you nicely explain the
rules to a FPL?Thanks. SWH
[ original email was from Sarah Hoff - hoffs@stifel.com ]
Thanks Mahesh. I like your style and I will send the email with an attach cookie jar and a bit of Java with plenty of these LOL.
But don’t worry I won’t comply the code!
Sarah
PossResend Tag 97=Y is required when a FIX message has been already sent
earlier and is being retransmitted with a different sequence number in
this message.There is no harm in 97=N present in original transmissions, but it
serves no purpose other than to assert that it is a original send and is
not a retransmission. I do not see any reason to mandate its presence in
original transmissions because as per FIXProtocol, its optional in
original transmissions.How to “nicely” explain the rule ? If you are sending them a paper /
printed reply, maybe you can send it with a box of choclates and a nice
greeting card. If you are sending them an email, you could attach a
cookie jar (enable cookies in your internet browser, then copy all the
cookie files to a folder and create a java archive file), dont forget to
add manyHi,
I have a vendor ITG TRITON who is an FIX Protocol Limited Partner.
Who is mandating that I use/support tag 97 on 4.2. My OMS will NOT
support this NOR is it a FIX standard. How do you nicely explain the
rules to a FPL?Thanks. SWH
Hi Sarah,
Just a curiosity, are you both use the same Fix version? I just wanted to know because I think I had the same issue before where the counterparty insisted in including few tags that are not mandatory. The fact that our engine was setup on 4.0 and they were using 4.2.
Thanks Mahesh that well explained.
Joe
Thanks Mahesh. I like your style and I will send the email with an
attach cookie jar and a bit of Java with plenty of these
But don’t worry I won’t comply the code!Sarah
PossResend Tag 97=Y is required when a FIX message has been already
sent earlier and is being retransmitted with a different sequence
number in this message.There is no harm in 97=N present in original transmissions, but it
serves no purpose other than to assert that it is a original send and
is not a retransmission. I do not see any reason to mandate its
presence in original transmissions because as per FIXProtocol, its
optional in original transmissions.How to “nicely” explain the rule ? If you are sending them a paper /
printed reply, maybe you can send it with a box of choclates and a
nice greeting card. If you are sending them an email, you could attach
a cookie jar (enable cookies in your internet browser, then copy all
the cookie files to a folder and create a java archive file), dont
forget to add manyHi,
I have a vendor ITG TRITON who is an FIX Protocol Limited Partner.
Who is mandating that I use/support tag 97 on 4.2. My OMS will NOT
support this NOR is it a FIX standard. How do you nicely explain the
rules to a FPL?Thanks. SWH
[ original email was from Sarah Hoff - hoffs@stifel.com ]
Hi Joe,
With 4.0 you are lucky because the tags only go up to 140 but with 4.2 you have custom tags like locate 5700 and it provides you more flexibility with routing, etc. If you are on FIX 4.0 and your counter party is on 4.2 they must be a middle man and should “dumb it down” for you. They can not mandate any tags over 140. You have to be on the same version to connect so that is why I am thinking they are a middle man. I hope this helps.
Sarah
Hi Sarah,
Just a curiosity, are you both use the same Fix version? I just wanted
to know because I think I had the same issue before where the
counterparty insisted in including few tags that are not mandatory. The
fact that our engine was setup on 4.0 and they were using 4.2.Thanks Mahesh that well explained.
Joe
Thanks Mahesh. I like your style and I will send the email with an
attach cookie jar and a bit of Java with plenty of these
But don’t worry I won’t comply the code!Sarah
PossResend Tag 97=Y is required when a FIX message has been already
sent earlier and is being retransmitted with a different sequence
number in this message.There is no harm in 97=N present in original transmissions, but it
serves no purpose other than to assert that it is a original send
and is not a retransmission. I do not see any reason to mandate its
presence in original transmissions because as per FIXProtocol, its
optional in original transmissions.How to “nicely” explain the rule ? If you are sending them a paper /
printed reply, maybe you can send it with a box of choclates and a
nice greeting card. If you are sending them an email, you could
attach a cookie jar (enable cookies in your internet browser, then
copy all the cookie files to a folder and create a java archive
file), dont forget to add manyHi,
I have a vendor ITG TRITON who is an FIX Protocol Limited Partner.
Who is mandating that I use/support tag 97 on 4.2. My OMS will NOT
support this NOR is it a FIX standard. How do you nicely explain
the rules to a FPL?Thanks. SWH
Just want to correct the prior message. FIX.4.0 spec does accommodate user defined fields. It is not limited to tag 140 and below.
Hi Joe,
With 4.0 you are lucky because the tags only go up to 140 but with 4.2
you have custom tags like locate 5700 and it provides you more
flexibility with routing, etc. If you are on FIX 4.0 and your counter
party is on 4.2 they must be a middle man and should “dumb it down” for
you. They can not mandate any tags over 140. You have to be on the same
version to connect so that is why I am thinking they are a middle man. I
hope this helps.Sarah
Hi Sarah,
Just a curiosity, are you both use the same Fix version? I just wanted
to know because I think I had the same issue before where the
counterparty insisted in including few tags that are not mandatory.
The fact that our engine was setup on 4.0 and they were using 4.2.Thanks Mahesh that well explained.
Joe
Thanks Mahesh. I like your style and I will send the email with an
attach cookie jar and a bit of Java with plenty of these
LOL. But don’t worry I won’t comply the code!Sarah
PossResend Tag 97=Y is required when a FIX message has been
already sent earlier and is being retransmitted with a different
sequence number in this message.There is no harm in 97=N present in original transmissions, but it
serves no purpose other than to assert that it is a original send
and is not a retransmission. I do not see any reason to mandate
its presence in original transmissions because as per FIXProtocol,
its optional in original transmissions.How to “nicely” explain the rule ? If you are sending them a paper
/ printed reply, maybe you can send it with a box of choclates and
a nice greeting card. If you are sending them an email, you could
attach a cookie jar (enable cookies in your internet browser, then
copy all the cookie files to a folder and create a java archive
file), dont forget to add manyHi,
I have a vendor ITG TRITON who is an FIX Protocol Limited
Partner. Who is mandating that I use/support tag 97 on 4.2. My
OMS will NOT support this NOR is it a FIX standard. How do you
nicely explain the rules to a FPL?Thanks. SWH