Support Board
Date/Time: Wed, 27 Nov 2024 22:36:48 +0000
Work-around for server side OCO's
View Count: 2315
| [2014-04-06 19:27:02] |
| User92763 - Posts: 14 |
|
I'm curious if there would be a way to program a work-around for servers that don't support OCO orders. As an example: Say that you have placed a parent order with attached orders (10T stop and 20T target), as the server does not support OCO orders, the orders are handled locally in SC. At the same time that the parent order fills, an opposing order for a stop is sent that is not an OCO that will be accepted and reside on the server side (lets call this a catastrophic stop... set at 30T). The OCO orders continue to work locally, and if either target or stop is hit the OCO group cancels the opposing order, but in addition sends a cancel order for the catastrophic stop residing on the server. In this way, if you should experience an internet service interruption, at least you have that catastrophic order on the server. Of course the obvious solution would be to use a server that supports OCO's, but you are limited to the number of brokers that you can choose from. I don't know that such a thing would be popular enough to incorporate it as part of the SC platform, but if it could be programmed as described, I may be willing to pay for programming costs, and make use of it myself. I haven't considered all the possible downside scenarios yet... just asking if it's possible. Thanks. |
| [2014-04-06 19:54:06] |
| |
|
When the parent order fills, the Target and Stop are sent to the server as explained here: https://www.sierrachart.com/index.php?l=doc/doc_AttachedOrders.html#Introduction One change that could be made is that the Target could be held back as "pending" order on the local side until it is detected that it should be filled and then it could be sent at that time. This would have the advantage of if connectivity is lost there is not a chance of reentering the position through the Target or Stop order if one of them is filled but the other is not canceled. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-04-06 21:42:15] |
| User92763 - Posts: 14 |
|
Thank you for the prompt reply. I understand that attached orders with a stop and target are sent as OCO orders to the server once the parent order has filled. If the sever DOES NOT support OCO type orders then the only way to manage these OCO orders is to do it locally on the SC platform (on my computer). Is this a misunderstanding on my part? As far as programming what I described in the original post: In the time that has passed, I've already come up with a scenario where such a thing potentially would cause more problems than what it would solve. Sorry, bad idea... never mind. |
| [2014-04-07 00:31:06] |
| |
|
If the sever DOES NOT support OCO type orders then the only way to manage these OCO orders is to do it locally on the SC platform (on my computer) The canceling of the orders does have to be done locally on the client-side.We think that the idea that we mentioned, could be implemented as an option. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-04-07 00:31:34
|
| [2014-04-07 13:58:09] |
| User92763 - Posts: 14 |
|
I actually like your solution. As I understand it, the stop order would be sent to the server, and the target would be managed locally. Neither of these would be OCO orders. If the target stop was triggered, then an order to cancel the stop order would be sent to the server side. I like it. Is this something that you would consider implementing as an option on SC? I think others would be pleased to see it.
|
| [2014-04-07 17:56:32] |
| |
|
Yes, we can implement this. We will think about how to do it.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-04-07 20:14:02] |
| crazybears - Posts: 314 |
|
+1 very good feature |
| [2014-04-07 21:28:37] |
| User30720 - Posts: 20 |
|
+1 as well.
|
| [2014-04-09 11:33:09] |
| Futures Operator - Posts: 239 |
|
+1, great idea, would love to see it as an optional feature. Kudos to SC to helping traders mitigate the risks of locally held OCO orders!
|
| [2014-05-21 02:47:14] |
| User30720 - Posts: 20 |
|
Yes, we can implement this. We will think about how to do it.
Hi SC, Re your post #6. Has any more thought gone into this and when you might possibly put it into production? Thanks |
| [2014-05-22 01:16:20] |
| |
|
We will try to get to this as soon as we can. Probably still another month away.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-07-09 07:55:11] |
| User13668 - Posts: 294 |
|
Just dropping in to get an update on progress. Thanks |
| [2014-07-09 07:58:20] |
| |
|
Actually, we are starting on this today. Should be out in one or two more days.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-07-18 19:57:33] |
| usersc - Posts: 14 Invalid SC Account Name. |
|
Any news... Thanks, |
| [2014-07-18 20:03:38] |
| |
|
This is done. It will be out later today or tomorrow.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-10-11 19:14:24] |
| User13668 - Posts: 294 |
|
Hi SC, Can you point me to the place in the on-line documentation that helps me set up attached orders that utilise this work around for lack of server side OCOs. I use the TT feed via AMP and TT don't support server side OCO so I want to take advantage of this work around. Thanks EDIT: Answered my own question; Global Settings < General Trade Settings < [tick] 'Hold Limit Attached Orders on Client Side until touched'. SC: only reply if I have this wrong. Thanks Date Time Of Last Edit: 2014-10-11 19:33:44
|
| [2014-10-11 21:07:25] |
| |
|
Yes, that is the correct option.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: