Today, requests for daily, weekly or monthly history fail with the following new, UNDOCUMENTED error message.

"..Error: History data currently unavailable"

I, for one, am getting sick and tired of being your alpha tester and having to pay for it.

And, like every other time, the status page at

http://www.dtniq.com/product/motd/motd2.cfm

proudly proclaims all systems normal

You are not alpha testing our services. We have had 2 hardware failures overnight with the server that connects to our historical database. Thus, we had an outage early this morning, then again when you posted. According to our operations staff, for the historical data, it requires a DNS change to fail over the historical data to our backup site. In this case it was faster to restart the server. We are looking at the hardware to determine the cause of the failure.

As for the MOTD, it is a manual process to update that. Thus, our support staff must be notified of the outage and have useful information to post. 2 things happened this morning. 1, the support Manager is out of town, so I am guessing the process will move a bit slower because our other reps aren't as familiar with the process, and 2, by the time they would have posted, the problem was resolved.

I am working with our support, engineering and operations staff to determine why we have had so many issues this past week, and to ensure everything possible is being done to keep problems from occuring in the future.

---

Jay Froscheiser
DTN - Trading Markets

As the MOTD now states, we continue to have a problem with the hardware providing historical data. Engineers continue to work to resolve the problem.

---

Jay Froscheiser
DTN - Trading Markets

FYI: Actually this error message has been on the feed since the early beginnings. Recently, new error messages have been added, some in place of the 'old ones', but evidently the old ones are still there.

Here is a list of some of the error or response messages you can get - I suggest scanning for them on any request that has a reply. These are only the first part of the message - usually there is more info with it. It was suggested years ago a that a standard consistent error message format that all responses (quotes, news, history, level II, etc ) like the !ERROR! (that is starting to be the standard) and a number id that could relate to error type and expanded info if desired. Some of the errors listed below only came with news stories.

"!ERROR!", "..Error", "-Err", "..NONE..", "No data found", "E,", "SYNTAX"
and the embedded error in the "last" field position for a quote of "Invalid symbol" or "NOT FOUND" (I just look for either N or I to see if OK).

I have no idea as to the complete list - these were obtained by trail and error over the years - the software DTN first got and used for IQFeed was not well thought out and organized (or documented). I do see improvement in the more common use of !ERROR! in most error responses. It also appears we are getting close to having a stable client too to work with. (finally!)

Hope this helps.

GL!

David

---

IQXP Software
http://www.iqxp.com

LiveWire Update Service
PO Box 1417
Fairfield, IA 52556
641-472-8393
http://www.livewire-cablesoft.com/

Thank you very much David.

That is an extremely useful list. After more than 2 years of daily use, I have only encountered (and subsequently coded around) about half of those error strings.