Date/Time: Thu, 19 Jul 2018 19:31:29 +0000
Post From: Notice: CTS Trading Service Symbols
Sierra Chart Engineering - Posts: 61903
The problem is we see some inconsistent and intermittent problems with security definition responses from CTS where ultimately the market ID requested is not provided. Also with the way that Sierra Chart handles security definition requests is not 100% reliable because there are a lot of considerations to handle this correctly in the case of when we do not get the market ID. It takes time to implement this properly and we have not had enough time to do it.
The problem is, all of this programming makes no sense for us to be doing. CTS can so easily do this on their side.
A failure to get the market ID from a security definition request will prevent a chart or Trade DOM from updating and also prevent the submission of orders.
It is not proper for us to be going through an extraordinary amount of work interface to a system. There is a much better way.
CTS can easily solve this on their side and we have told them that.
We should be able to identify a futures contract by the underlying symbol, the month and year, and the exchange and the security type. They just need to allow this in their market data request. This is so simple. We shouldn't have to go through a complex procedure to look up a market ID and handle all of the failure scenarios.
The market ID concept should not even be exposed for outright futures contracts. And they should not be changing these IDs for existing futures contracts which are already listed.
Sierra Chart Support - Engineering Level
Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2014-03-14 02:56:39