Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)




"I've been using IQFeed 4 in a multi-threaded situation for the last week or two on 2600 symbols or so with 100 simultaneous daily charts, and I have had 100% responsiveness." - Comment from Scott
"I "bracket trade" all major news releases and I have not found one lag or glitch with DTN.IQ feed. I am very comfortable with their feed under all typical news conditions (Fed releases, employment numbers, etc)." - Comment from Public Forum
"I started a trial a few weeks back before the market went wild. DTN.IQ didn’t miss anything and beat my other provider. I decided to stay with you because of the great service through all the volatility." - Comment from Mike
"You have an excellent product !!!!!!" - Comment from Arely
"I've never had DTN go out on me since switching. ******* would go down a couple times every month when I was using them." - Comment from Bryce in AL.
"Its working FABULOUSLY for me!! Holy cow...there has been so much I've been missing lately, and with this feed and Linnsoft software...I'm in the game now." - Comment from Chris R.
"I'm very glad I switched to IQFeed. It's working perfectly with no lag, even during fast market conditions." - Comment from Andy via Email
"You are much better than lawyers or the phone company because you answer the phone when I call! I just love your customer service." - Comment from Isreal
"For anyone considering using DTN.IQ for a data feed, my experience with the quality of data and the tech support has been very positive." - Comment from Public Forum
"Very impressed with the quality of your feed - ******* is a real donkey in comparison." - Comment from A.C. via Email
Home  Search  Register  Login  Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTNMarkets on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
»Forums Index »IQFeed Developer »IQFeed Developer Support »IQFeed 4.1.1.1 - !ENDMSG! query
Author Topic: IQFeed 4.1.1.1 - !ENDMSG! query (7 messages, Page 1 of 1)

thomasr
-Interested User-
Posts: 1
Joined: Feb 18, 2006

ACME'd again


Posted: Feb 18, 2006 12:47 PM          Msg. 1 of 7
I have been looking at some .NET code a customer has been using as part of a daily batch process and have been testing this with the IQFeed 4.1.1.1 client.

It was my understanding from the IQFeed documentation, that the <CR><LF>!ENDMSG!<CR><LF> message would signify an end-of-message when using the socket interface to retrieve historical data.

However - when attempting to get data for the symbol 'BUYY' - a symbol from the downloadable symbols list, the following message is returned:

!ERROR! !NONE!

!ENDMSG!
!ERROR! Invalid symbol.

!ENDMSG!

This suggests that there can be (in theory) any number of !ENDMSG! strings returned in response to a historical data lookup. The existing code used does not cater for this, and the only work arounds I can see are:

1 - Identify another 'No more data to be received' indicator (API call possibly ?)
2 - Rewrite the .NET socket client class to open and close the socket for every request (Not very efficient use of the socket interface)
3 - Use some form of timer to try and ensure that the buffer will no longer be fed data from the IQFeed client (Not very pretty way around)

The 'error' has not crept up before, so I am unclear as to whether this message format is a new addition.

Regards,
Thomas

stargrazer
-DTN Guru-
Posts: 262
Joined: Jun 13, 2005

Right Here & Now


Posted: Feb 18, 2006 12:56 PM          Msg. 2 of 7
When retrieving historical data and you get an '!ERROR! !NONE!' response, your processing state machine can expect one and only additional response set, in this case it happens to be a '!ERROR! Invalid symbol.'. I think the current documentation may discuss this, but may not be too clear. Once you receive that second response, your state machine can reset and request further information through that socket.

Open a manual telnet session and try various commands to test the various responses.

Hope this helps.

DTN_Steve_S
-DTN Guru-
Posts: 2090
Joined: Nov 21, 2005


Posted: Feb 20, 2006 08:51 AM          Msg. 3 of 7
Hello Thomas,

I have been able to duplicate this and am looking into the cause. There appears to be two seperate issues here.

For some reason, BUYY is returning an invalid symbol error which is what is making the second issue appear.

This appears to only affect Weekly, Monthly, and Daily History requests that are sent for invalid symbols. This means that it should be fairly easy to predict when it will happen programaticly until this issue is resolved.

jfcantin
-Interested User-
Posts: 20
Joined: May 18, 2004


Posted: Mar 5, 2006 11:15 PM          Msg. 4 of 7
Steve,

Does this means that we should not expect !SYNTAX_ERROR!<CR><LF> anymore as an Error from the daily historical socket?

Best,

Jean-Francois

DTN_Steve_S
-DTN Guru-
Posts: 2090
Joined: Nov 21, 2005


Posted: Mar 6, 2006 08:32 AM          Msg. 5 of 7
No. This thread is dealing with some requests that are currently returning 2 separate error messages (which is resulting in two !ENDMSG! as well).

If you do not format a request properly, you will still get a !SYNTAX_ERROR!<CR><LF>.
Edited by DTN_Steve_S on Mar 6, 2006 at 08:33 AM

jfcantin
-Interested User-
Posts: 20
Joined: May 18, 2004


Posted: Mar 6, 2006 09:53 AM          Msg. 6 of 7
Thanks for the clarification. The documentation does not explain what is associated with each error message type.

I am assuming that we will get the 2 error messages(back to back) for a bad symbol request until a new version is released. Is this a safe assumption?

Is it possible to receive only one set of error message with the current version?

Best,

Jean-Francois

DTN_Steve_S
-DTN Guru-
Posts: 2090
Joined: Nov 21, 2005


Posted: Mar 6, 2006 10:48 AM          Msg. 7 of 7
These are fairly Isolated issues and wont affect all cases so most of your requests will return normal errors.

This issue in this thread is brought on by the fact that BUYY has never actually traded and so there is no history data available.

This issue will only arise with symbols who meet the same criteria.

Valid symbols that have never traded.

There is also a similar issue dealing with History requests on this thread:
http://forums.iqfeed.net/index.cfm?page=topic&topicID=922

but once again, it is for very specific requests (based upon time of day and day of the week that the requests are made).

both of these issues will be resolved in the next release.
 

 

Time: Mon December 16, 2019 6:12 AM CFBB v1.2.0 32 ms.
© AderSoftware 2002-2003