{{Quickfixn}} ICE FIX engine xml changes

[Rettenmier, Curt]

Grant,

Thanks for your response. Yes I am working with ICE. I did receive the 2.0.38.1 latest version doc only this morning and was added to the ICE community and was also was added to their mailing list. I did open a case with the ICE Help Desk yesterday and discovered that they had implemented changes in June. The errors we have been having are related to Security Definitions.  Last year when I was developing our solution you sent me an unofficial copy of the xml schema with ICE custom fields in it which we have been using since then. In looking at the schema one thing I noticed is it doesn’t appear that the order of the tag fields in the schema exactly matches the ICE documentation. For example at the start of the Security Definition in the new ICE doc the first three fields are SecurityResponseID, SecurityResponseType and SecurityReqID in that order but in the 4.4 schema under the message SecurityDefinition the first three fields are SecurityReqID, SecurityResponseID and SecurityResponseType. So does it matter under the SecurityDefinition message where I add the new fields? Would you be open to sending me your modified schema with the latest changes?

Curt Rettenmier
Software Developer
Avista Corporation
509-495-8492
curt.rettenmier at avistacorp.com<mailto:curt.rettenmier at avistacorp.com>

From: Quickfixn [mailto:quickfixn-bounces at lists.quickfixn.com] On Behalf Of Grant Birchmeier
Sent: Friday, July 17, 2015 10:31 AM
To: Mailing list for QuickFIX/n
Subject: Re: {{Quickfixn}} ICE FIX engine xml changes

I'm very familiar withe ICE TradeCapture Interface, if that's what you're working with.  I maintain an app that uses it.

1. Do you have the latest version of their doc, the ICE-FIX TradeCapture Reference Manual?  (Latest version is 2.0.38.1)

2. Have you customized your FIX 4.4 DD XML file to match the message and field definitions that ICE has defined in that document?  It's simple to do, though a little time consuming the first time.  They only use a handful of messages; most of the other App-level message definitions you can just delete.

3. Are you on ICE's mailing list so that you are alerted whenever they make changes to the message definitions?  This typically happens 2-3 times per year.  They give you plenty of lead time before the changes go live, and they have a test environment you can use to test your app before the changes go live.

-Grant


On Fri, Jul 17, 2015 at 12:09 PM, Rettenmier, Curt <Curt.Rettenmier at avistacorp.com<mailto:Curt.Rettenmier at avistacorp.com>> wrote:
We just became aware of changes made by our counterparty (ICE) to their application that were implemented at the end of June. We have been receiving errors since then and need to modify our application to support their changes. We are using QuickFix/n and the FIX 4.4 schema and are wondering if others have made changes to their schemas to incorporate ICE’s changes and would be willing to share or discuss their modifications. Thanks,

Curt Rettenmier
Software Developer
Avista Corporation
509-495-8492<tel:509-495-8492>
curt.rettenmier at avistacorp.com<mailto:curt.rettenmier at avistacorp.com>


_______________________________________________
Quickfixn mailing list
Quickfixn at lists.quickfixn.com<mailto: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/20150717/2d07d6b9/attachment-0002.htm>