Hi all. For some reason the time is being ignored on my HTT requests. In fact, anything after the date is ignored. The start and end dates are fine, but the socket returns the entire day's worth of quotes rather than just between the times specified, which takes too long and is unnecessary. I can, however, get successful historical lookups with time using HTD, but counting days back gets problemmatic. Any and all thoughts are very much appreciated:

message <- 'HTT,@ESZ17,20171005 180000,20171005 180014,,,,1,,\r\n' this returns 20171005 from midnight full day "2017-10-05 00:00:43,2536.00,1,13787,2536...

message <- 'HTT,@ESZ17,20171005180000,20171005180014,,,,1,,\r\n' this too returns 20171005 from midnight full day "2017-10-05 00:00:43,2536.00,1,13787,2536...

message <- 'HTT,@ESZ17,20171005howdy,20171005howdy,,,,1,,\r\n' same result!

however... message <- "HTD,@ESZ17,2,,180000,180014,1r\n" returns correctly: "2017-10-05 18:00:00,2548.75,4,4,2548.75...

Thanks for looking.

Hello, I got your messages via email. Unfortunately I don't have an answer for you however, I will say (mostly for future readers of this post) that the format that should be adhered to for these fields is CCYYMMDD HHmmSS (with a single space between date/time). I understand you're just troubleshooting and it's good information that the space seems to be what is corrupting your requests but I'm not sure how currently. At this point I think we've determined it has to be something in your setup.

Do you have the ability to compile/run any of the supplied example apps we distribute with the feed? If so, do they show the same issues? If not, it looks like your account is authorized for our DTN.IQ client. http://www.dtniq.com/template.cfm?navgroup=supportlist&urlcode=33&view=1

Can you test using this (open the Time & Sales and configure the request to use a date range).

Also, which version of python are you using? and do you have any environment variables set that could be altering the run of the app?https://docs.python.org/2/using/cmdline.html#environment-variables You might try running your app with the -E parameter just to make sure that isn't the issue.