{{Quickfixn}} Reg: Quick Fix vs ICE Tag Name Mismatch - tag# 305 - Fix44.XML

[Grant Birchmeier]

You are mis-diagnosing your issue.  The name of the tag is not
relevant.  I'm VERY familiar with ICE's Trade Capture interface.  I'm 100%
sure that you can make QF/n work with it.

You've given us so little that it's hard to say exactly what your problem
is.

But I think this message is telling you that, per your DD configuration,
tag 305 is not specified to belong to this message "d".

I strongly suspect that you have an error in your DD xml file.  ICE's
Trade-Capture interface has made a lot of message/field customizations, all
of which need to be ported accurately into the DD.  (Again, I speak
first-hand experience.)

-Grant



On Fri, Nov 22, 2019 at 9:05 AM <SPoolla at nisource.com> wrote:

> Dear Team,
>
> We are using the Quick Fix implementation in our application to interface
> with Intercontinental Exchange(ICE) to capture gas trades. We have
> identified that there is a mismatch for tag# 305 between Fix44.xml and ICE
> protocol.
>
> In Fix44.xml, the tag#305 is named as *UnderlyingSecurityIDSource* versus
> *UnderlyingIDSource* ICE protocol. The application gives a error
> validation and sends the below response back to ICE due to this mismatch.
> We have tried updating the Fix44.xml in our application with name that
> matches ICE protocols, but still no luck.
>
> 49=****| 52=20191119-15:41:06.957 | 56=ICE | 45=2 | 58=Tag not defined for
> this message type | 371=305 | 372=d
>
> Kindly suggest a fix for the above scenario. Thanks much in advance!!
>
> Thanks,
> Avinash
>
>
>
> From:        quickfixn-owner at lists.quickfixn.com
> To:        spoolla at nisource.com,
> Date:        11/21/2019 03:34 PM
> Subject:        Reg: Quick Fix vs ICE Tag Name Mismatch - tag# 305 -
> Fix44.XML
> Sent by:        "Quickfixn" <quickfixn-bounces at lists.quickfixn.com>
> ------------------------------
>
>
>
> USE CAUTION: This email was sent from an external source. Think before you
> click links or open attachments. If suspicious, please forward to
> security at nisource.com for review.
>
> Only subscribers can send to this mailing list.  If you are not a
> subscriber, this is why your message was rejected.
>
> If you sign up, you can send your message again and it will be
> accepted.
>
>
> ----- Message from SPoolla at nisource.com on Thu, 21 Nov 2019 15:34:42
> -0500 -----
>
> *To:*
> quickfixn at lists.quickfixn.com
>
> *cc:*
> maubin at nisource.com, SV at nisource.com, rnadolski at nisource.com
>
> *Subject:*
> Reg: Quick Fix vs ICE Tag Name Mismatch - tag# 305 - Fix44.XML
> Dear Team,
>
> We are using the Quick Fix implementation in our application to interface
> with Intercontinental Exchange(ICE) to capture gas trades. We have
> identified that there is a mismatch for tag# 305 between Fix44.xml and ICE
> protocol.
>
> In Fix44.xml, the tag#305 is named as *UnderlyingSecurityIDSource* versus
> *UnderlyingIDSource* ICE protocol. The application gives a error
> validation and sends the below response back to ICE due to this mismatch.
> We have tried updating the Fix44.xml in our application with name that
> matches ICE protocols, but still no luck.
>
> 49=****| 52=20191119-15:41:06.957 | 56=ICE | 45=2 | 58=Tag not defined for
> this message type | 371=305 | 372=d
>
> Kindly suggest a fix for the above scenario. Thanks much in advance!!
>
> Thanks,
> Avinash
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>


-- 
Grant Birchmeier
*Connamara Systems, LLC*
*Made-To-Measure Trading Solutions.*
Exactly what you need. No more. No less.
http://connamara.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20191122/c1108ade/attachment.htm>