Quote from SideShowBob:
Twice now I've had orders submitted in TWS for metals on GLOBEX (NYMEX) somehow turn on their RTH flag. My TWS is set to allow stops to trigger outside of RTH and orders I submitted on other exchanges (for example eCBOT and CDE -- Montreal exchange) do not get this attribute set. Additionally when I submit the orders I do not see the "clock" in the status column, but overnight it apparently appears and the orders will not trigger until 9:30.
Has anyone else had this problem? What can I do to fix it? I use TWS 864 since IB still apparently hasn't fixed the quotes freezing problem that's been going on for months now....
SSB
SideShowBob,
Have you voted for suggestion # 2185 in the IB New Features Poll?
You are using an outdated version of TWS, for very good reason, because it is your strategy for avoiding the data freeze problem occurring in more recent versions. You are, unfortunately, also encountering a different bug, regarding stop orders, while using the outdated version. If you try to get troubleshooting for the problem with stop orders, IB's CS reps will tell you that IB will not troubleshoot the problem, because you are using an outdated TWS version. They will tell you that you must first update to the latest version, and then if the problem then continues with the current version, only then will they agree to troubleshoot.
The problem with updating to the current version is that it will force you to grapple with the new bugs introduced, but not yet corrected, in the versions following the outdated version you are currently using. This includes the datafreeze problem. So you are between a rock and a hard place.
If, on the other hand, IB had been following the policy suggested by suggestion # 1072, in the new features poll, things would have been different for you. IB did officially adopt # 1072 as policy, back in August 2006, but then IB failed to follow that policy. The # 1072 policy was that troubleshooting old bugs should take priority over adding new features. IB instead allowed the data freeze problem to persist through multiple new versions of TWS, all the while merrily adding more and more more new bells and whistles, in new version after new version.
This is one example of the reason for suggestion # 2185. Suggestion # 2185 asks that IB change its priorities, to follow its own policy adopted from suggestion # 1072, so that fixing old problems with core functions and old features takes priority over adding new features. Suggestion # 2185 has not yet been officially accepted by IB, and is still open for voting. It seems to me, based on your particular problems, that your experience with IB would be greatly improved in the future, in many different ways, if your vote helped move IB toward adopting suggestion # 2185. Have you voted for it? I think that voting for it would be the best possible answer to your question, "What can I do to fix it?"
