Support Board
Date/Time: Wed, 01 Jan 2025 14:22:17 +0000
Error: "Synchronized Internal Position to current Service Position. Current Position qua..
View Count: 14494
| [2016-05-02 18:26:00] |
| User99735 - Posts: 234 |
|
Hi, Am getting the error "Synchronized Internal Position to current Service Position. Current Position quantity: 0" in live trading, however the same does not come in simulated trading. Sequece of orders as follows - Open a Buy Order at Market - When the Buy order is filled and PositionData.PositionQuantity is non-zero, a Stop/Limit order is placed for "Buy to close" Detailed log is as follows. Please advise. Regards Vivek ActivityType DateTime Symbol OrderActionSource InternalOrderID ServiceOrderID OrderType Quantity BuySell Price Price2 OrderStatus FillPrice FilledQuantity TradeAccount OpenClose ParentInternalOrderID PositionQuantity FillExecutionServiceID Order 2016-04-29 06:32:08.058 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade canceled order: AAPL [M] 1 Min #2|Option Trader 69497 10699 Stop 1 Sell 0.41 Pending Cancel U1644808 Close Order 2016-04-29 06:32:08.057 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade canceled order: AAPL [M] 1 Min #2|Option Trader 69498 10700 Limit 1 Sell 0.56 Pending Cancel U1644808 Close Order 2016-04-29 06:32:07.519 AAPL-OPT-20160429-94-P Synchronized Internal Position to current Service Position. Current Position quantity: 0 Unspecified U1644808 Order 2016-04-29 06:32:00.345 AAPL-OPT-20160429-94-P-SMART-100-USD IB Open Order message update 69498 10700 Limit 1 Sell 0.56 Open U1644808 Close 1 Order 2016-04-29 06:32:00.205 AAPL-OPT-20160429-94-P-SMART-100-USD IB Open Order message update 69497 10699 Stop 1 Sell 0.41 Open U1644808 Close 1 Order 2016-04-29 06:31:59.951 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade: AAPL [M] 1 Min #2 | Option Trader | sc.SubmitOrder | Bar start Date-Time: 2016-04-29 06:32:00 69498 Limit 1 Sell 0.56 Order Sent U1644808 Close 1 Order 2016-04-29 06:31:59.950 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade: AAPL [M] 1 Min #2 | Option Trader | sc.SubmitOrder | Bar start Date-Time: 2016-04-29 06:32:00 69497 Stop 1 Sell 0.41 Order Sent U1644808 Close 1 Fill 2016-04-29 06:31:59.514 AAPL-OPT-20160429-94-P-SMART-100-USD IB order fill (execution) 69496 10698 Market 1 Buy Filled 0.51 1 U1644808 Open 1 0000f157.5723439d.01.01 Order 2016-04-29 06:31:59.513 AAPL-OPT-20160429-94-P-SMART-100-USD IB order fill (execution) 69496 10698 Market 1 Buy Filled 0.51 1 U1644808 Open Order 2016-04-29 06:31:59.165 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade: AAPL [M] 1 Min #2 | Option Trader | sc.SubmitOrder | Bar start Date-Time: 2016-04-29 06:32:00 69496 Market 1 Buy Order Sent U1644808 Open Order 2016-04-29 06:30:23.091 Requesting Open orders from trading service Unspecified None |
| [2016-05-02 18:40:19] |
| |
|
This is not an error message: Order 2016-04-29 06:32:07.519 AAPL-OPT-20160429-94-P Synchronized Internal Position to current Service Position. Current Position quantity: 0 Unspecified U1644808
However, what this does indicate is that the Trader Workstation did not provide a Trade Position update for this Option symbol. You need to ask Interactive Brokers why this is the case. 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 |
| [2016-05-02 19:22:27] |
| User713273 - Posts: 409 |
|
As you have promoted, I have spoken with IB API support about this issue. The full chat log is below. Please advise. Thx ChatSys: This chat is associated with ticket #242078. Please record this number for use in future inquiries. You are currently in room 'Technical Assistance'. Siteng J: Hello, this is 'Siteng J'. How may I help you? eggnog999: Hi Siteng- Im getting this error - Order 2016-04-29 06:32:07.519 AAPL-OPT-20160429-94-P Synchronized Internal Position to current Service Position. Current Position quantity: 0 Unspecified eggnog999: Why this is the case? Im currently using a 3rd party charting software provider (Sierra Chart) Siteng J: I don't think that's is an error message sent by IB TWS. Siteng J: Please follow the instructions below to create and send us a Detailed log file: 1. Login to TWS. 2. Navigate to Edit > Global configuration > API > Settings. 3. Set the logging level to DETAIL. 4. Click Apply and OK buttons. 5. Try to replicate the concerns. 6. Once you replicate the issue, please send us the detailed log file. 7. You can send the log file by holding Ctrl+Alt+Q at the same time in TWS, and then click ‘submit’ on the Report Problem window. Once you have clicked on ‘submit’, your log files will be automatically uploaded to our server. eggnog999: Ok is currently set to detail, will submit log from this AM. eggnog999: Ok says was successfully submitted Siteng J: Ok, have you replicated the issue after you set the logging to detail? eggnog999: I have not, but logging was already set to detail within TWS Siteng J: Ok, let me check eggnog999: thx Siteng J: Did you receive the error after placing an order? eggnog999: yes Siteng J: When did you place the order? eggnog999: Order was placed, the 8-9 seconds later attached orders are cancelled eggnog999: 06:31:50 AM PST eggnog999: SRY 06:31:48 AM PST eggnog999: The placement of orders is not the issue, its the fact the attached orders are cancelled eggnog999: Using a simulation account I have not had this issue Siteng J: What is your local time right now? eggnog999: PST 11:55 AM Siteng J: And the order you mentioned was placed today, correct? eggnog999: YES, had 2 orders filled both 1 contract each order Siteng J: I guess the log file from today is too big to be directly uploaded Siteng J: In TWS, could you please hold Ctrl+Alt+U Siteng J: Then you will see the directory where the logs are stored eggnog999: Yes do you want me to replicate first? Siteng J: No, you can directly go to that directory eggnog999: ok Siteng J: Find the file called tws.log Siteng J: Please try to zip the file and see what's is the size of the compressed file eggnog999: ok stored in C:/jts/daownqydnq\ Siteng J: What is the size of the compressed log file? eggnog999: 538 MB Siteng J: Oh that is too big Siteng J: Do you mind if we delete the old log and have you replicate the issue to create a new log? eggnog999: thats fine Siteng J: Ok, please delete the tws.log directly Siteng J: You may have to close TWS before you do that eggnog999: ok Siteng J: And then you can replicate the issue again. Hold Ctrl+Alt+Q to upload the diagnostics eggnog999: ok file deleted and tws closed, will wait for issue to reoccur, should be no longer that a couple minutes Siteng J: Ok eggnog999: ok uploaded eggnog999: please check Siteng J: Yes, one moment please Siteng J: I actually do not see any issue in the log file Siteng J: I see that you placed two bracket orders. Siteng J: In the first one, the two brackets were canceled Siteng J: Is that the issue you are reporting? eggnog999: yes Siteng J: It was canceled directly by the third party program Siteng J: I see that it sent out the cancel order request in the log file eggnog999: Ok, they have said it was on IB's side, I will circle back with them on this eggnog999: Is there a way I can contact you directly? email? Siteng J: You can still initiate a chat and ask for me. My name is Siteng J Siteng J: Or you can call 877-442-2757 #5 > #4 Siteng J: And ask for me eggnog999: Ok thx eggnog999: This is the response from the 3rd party provider on this, "what this does indicate is that the Trader Workstation did not provide a Trade Position update for this Option symbol" Siteng J: I have double checked the log file Siteng J: I do not see Sierra Charts requested for position information Siteng J: The parent order was executed correctly and the execution information was sent back with no issue Siteng J: If Sierra Charts doubt it's an IB issue, they should be able to contact us directly but do not put you in the middle eggnog999: Ok, I understand, will speak with Sierra Chart about this as you have said Siteng J: Okay Date Time Of Last Edit: 2016-05-02 19:29:11
|
| [2016-05-02 22:14:33] |
| User713273 - Posts: 409 |
|
Would Using Order Fill Calculated Trade Positions be something to try w/this issue? https://www.sierrachart.com/index.php?l=doc/doc_TradeStatusWindows.html#OrderFillCalculatedPosition |
| [2016-05-02 22:16:57] |
| |
|
Yes that is the best solution and also what Interactive Brokers has said is not correct: Siteng J: I have double checked the log file
You can confirm this through the Trade >> Trade Service Log. Sierra Chart did subscribe to Position data.
Siteng J: I do not see Sierra Charts requested for position information 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 |
| [2016-05-02 22:24:57] |
| User713273 - Posts: 409 |
|
Ok will test tomorrow with that function set. One other item, I have attached the Trade Activity Log. I notice that every 3 or so minutes we are "Removing Position with Quantity of 0". Is this a normal constant response? |
 image (2).png / V - Attached On 2016-05-02 22:22:38 UTC - Size: 213.36 KB - 283 views |
| [2016-05-02 22:58:24] |
| User713273 - Posts: 409 |
|
Siteng J: It was canceled directly by the third party program
Siteng J: I see that it sent out the cancel order request in the log file Also, I realize that statement of his is incorrect, but referencing the above. Why would SC be cancelling attached/bracket orders? And beyond that, he himself said it was cancelled by a a third party provider (i.e. Sierra Chart). I don't see any reason TWS would be cancelling attached orders once attached orders are placed in TWS. It doesnt hold any weight. Any direction would be great on this. Again, I will test tomorrow and hopefully this is resolved. Thx |
| [2016-05-03 01:20:44] |
| User713273 - Posts: 409 |
|
More context in IB Log found below. Also attached TWS trade log and SC Trade Activity Log for even more context.. SC/TWS are off by 2 seconds when referencing. 06:31:56:554 -> 3-6-10713-Cancelled-0-1-0-691491877-0-0-9368395--4-2-10713-202-Order Canceled - reason:- 06:31:56:617 -> 3-6-10712-Cancelled-0-1-0-691491876-0-0-9368395--4-2-10712-202-Order Canceled - reason:- |
| Private File |
| [2016-05-03 05:42:39] |
| |
|
One other item, I have attached the Trade Activity Log. I notice that every 3 or so minutes we are "Removing Position with Quantity of 0". Is this a normal constant response? Why would SC be cancelling attached/bracket orders?
You are in the best position to answer this. You know exactly what you are doing and you have access to the Trade Activity Log:https://www.sierrachart.com/index.php?page=doc/doc_TradeActivityLog.php#ViewingHistoricalTradeActivity If you have a question about something you see in the Trade Activity Log, provide us that line and provide a clear question. 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: 2016-05-03 05:43:17
|
| [2016-05-03 05:46:43] |
| |
|
The orders with Internal Order IDs: 69628 69629 Were canceled by your automated trading system. So that answers post #8, #9. 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 |
| [2016-05-03 06:45:30] |
| User713273 - Posts: 409 |
|
Were canceled by your automated trading system.
I can say this much, after I notice the cancelation of attached orders within IB TWS, I disconnect from the SC data feed. The most recent attached orders are then acted out as they should w/ a profit/stop as typically there is a 8 second lag (highlighted below) before cancellation of attached orders occurs and then another order is entered. So in turn the error is definitely coming from SC ACSIL source code. Order 2016-04-29 06:32:08.058 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade canceled order: AAPL [M] 1 Min #2|Option Trader 69497 10699 Stop 1 Sell 0.41 Pending Cancel U1644808 Close
Order 2016-04-29 06:32:07.519 AAPL-OPT-20160429-94-P Synchronized Internal Position to current Service Position. Current Position quantity: 0 Unspecified U1644808 Order 2016-04-29 06:32:08.057 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade canceled order: AAPL [M] 1 Min #2|Option Trader 69498 10700 Limit 1 Sell 0.56 Pending Cancel U1644808 Close Order 2016-04-29 06:32:00.345 AAPL-OPT-20160429-94-P-SMART-100-USD IB Open Order message update 69498 10700 Limit 1 Sell 0.56 Open U1644808 Close 1 Order 2016-04-29 06:32:00.205 AAPL-OPT-20160429-94-P-SMART-100-USD IB Open Order message update 69497 10699 Stop 1 Sell 0.41 Open U1644808 Close 1 Order 2016-04-29 06:31:59.951 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade: AAPL [M] 1 Min #2 | Option Trader | sc.SubmitOrder | Bar start Date-Time: 2016-04-29 06:32:00 69498 Limit 1 Sell 0.56 Order Sent U1644808 Close 1 Order 2016-04-29 06:31:59.950 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade: AAPL [M] 1 Min #2 | Option Trader | sc.SubmitOrder | Bar start Date-Time: 2016-04-29 06:32:00 69497 Stop 1 Sell 0.41 Order Sent U1644808 Close 1 Fill 2016-04-29 06:31:59.514 AAPL-OPT-20160429-94-P-SMART-100-USD IB order fill (execution) 69496 10698 Market 1 Buy Filled 0.51 1 U1644808 Open 1 0000f157.5723439d.01.01 Order 2016-04-29 06:31:59.513 AAPL-OPT-20160429-94-P-SMART-100-USD IB order fill (execution) 69496 10698 Market 1 Buy Filled 0.51 1 U1644808 Open Order 2016-04-29 06:31:59.165 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade: AAPL [M] 1 Min #2 | Option Trader | sc.SubmitOrder | Bar start Date-Time: 2016-04-29 06:32:00 69496 Market 1 Buy Order Sent U1644808 Open I will speak w/ my developer about this. |
| [2016-05-03 14:21:32] |
| User713273 - Posts: 409 |
|
Using > Use Fill Calculated Positions - Global did nothing but cause multiple buy orders without any sign of attached orders, I had to manually exit all orders and took a loss. If you have a question about something you see in the Trade Activity Log, provide us that line and provide a clear question.
When looking at the first line item from the Trade Activity Log, what would be the reason for the order's not syncing? We believe the root of the problem is the fact the Internal and Service position are not communicating, causing cancellation of the service position. As you can see below the timeframes between this happening and the cancellation of attached orders (Target, Stop) is less than 1 second. Order 2016-04-29 06:32:07.519 AAPL-OPT-20160429-94-P Synchronized Internal Position to current Service Position. Current Position quantity: 0 Unspecified U1644808 Order 2016-04-29 06:32:08.058 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade canceled order: AAPL [M] 1 Min #2|Option Trader 69497 10699 Stop 1 Sell 0.41 Pending Cancel U1644808 Close Order 2016-04-29 06:32:08.057 AAPL-OPT-20160429-94-P-SMART-100-USD Auto-trade canceled order: AAPL [M] 1 Min #2|Option Trader 69498 10700 Limit 1 Sell 0.56 Pending Cancel U1644808 Close Have you seen prior issues where the internal and service order positions did not synch or communicate? Is there a function within ACSIL that would resolve this issue? Thanks again for the help on this. |
| [2016-05-03 15:18:25] |
| User713273 - Posts: 409 |
|
https://www.sierrachart.com/index.php?l=doc/doc_TradeActivityLog.php#DeterminingHistoricalPositionQuantity Yes it seems if a Trade Position Quantity is not updated to reflect that the Internal Trade Position Quantity has been synchronized to the Service Position Quantity then that would be the cause of the service position being cancelled. |
| [2016-05-03 15:34:42] |
| User99735 - Posts: 234 |
|
So can we expect a fix for the issue?
|
| [2016-05-03 17:26:07] |
| |
|
For further help on this, this is going to be chargeable at 55 USD per hour. If you are in agreement with that, add a deposit for 55 USD to the Additional Services Balance: https://www.sierrachart.com/usercp.php?page=AddAccountCredit We will look at this in our available time. There is no chance we will spend any further time on this unless there is a separate payment. None of this is our problems. All of this is issues with Interactive Brokers. There is nothing to fix here. 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 |
| [2016-05-03 17:43:19] |
| User713273 - Posts: 409 |
|
Account credit added, I need this to be solved. Thx
|
| [2016-05-03 17:45:58] |
| User713273 - Posts: 409 |
|
Please advise what is needed on our end. Thx
|
| [2016-05-03 21:08:26] |
| |
|
The first step is we need to review the recent postings. And then we need to set up a time for remote assistance where you can demonstrate the problem to us so we can gather the necessary information. Would tomorrow evening work for you? What time zone are you in? 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 |
| [2016-05-03 21:15:44] |
| User713273 - Posts: 409 |
|
Yes im in PST time zone. Also find new dialogue with IB API Support below. Thx again eggnog999: Hi Josh- Im getting this error - Order 2016-04-29 06:32:07.519 AAPL-OPT-20160429-94-P Synchronized Internal Position to current Service Position. Current Position quantity: 0 Unspecified eggnog999: Why this is the case? Im currently using a 3rd party charting software provider (Sierra Chart) Joshua B: You see that error in eSignal ? eggnog999: This is also directly from IB TWS log eggnog999: 06:31:56:554 -> 3-6-10713-Cancelled-0-1-0-691491877-0-0-9368395--4-2-10713-202-Order Canceled - reason:- 06:31:56:617 -> 3-6-10712-Cancelled-0-1-0-691491876-0-0-9368395--4-2-10712-202-Order Canceled - reason:- eggnog999: no Sierra chart Joshua B: Oh ok, what is the underlying issue that the logs are being reviewed for? I would not recommend examining the logs unless there is an underlying issue- there will be many diagnostic messages eggnog999: Underlying issue is attached orders are being placed in TWS and then are being deleted Joshua B: ok, it might be easiest to upload the full log- I can take a look at it Joshua B: Do you see these orders as attached in Tws or do they never appear that way? eggnog999: Yes they appear attached and the typically 8 seconds later they are deleted, I assume this indicates that TWS did not provide a Trade Position update for this Option symbol thus the canceling occurs Joshua B: Can you give an example of such an order? I can take a look here. eggnog999: yes, give me a minute eggnog999: These are the messages I recieve in TWS 06:31:56:554 -> 3-6-10713-Cancelled-0-1-0-691491877-0-0-9368395--4-2-10713-202-Order Canceled - reason:- 06:31:56:617 -> 3-6-10712-Cancelled-0-1-0-691491876-0-0-9368395--4-2-10712-202-Order Canceled - reason:- eggnog999: Cancel a Limit target and stop orders Joshua B: These orders were today with user eggnog999 ? eggnog999: no yesterday eggnog999: sry should have clarified eggnog999: The question at hand, would TWS ever cancel attached orders when placed in TWS Joshua B: no problem, I'm taking a look eggnog999: ok, also the stops/targets are not really attached they are separate exit orders that are sent once parent order is filled Joshua B: oh ok, I thought they were intended to be sent as attached orders eggnog999: no, sry again eggnog999: Once parent is fully executed we then have a 2nd order sent, all these orders are then opened in TWS eggnog999: the issue comes 8-9 seconds after execution that the stop/target orders are then cancelled Joshua B: Do you have the full API log? It can be emailed to api@interactivebrokers.com eggnog999: um let me check, does IB file away API logs that were sent over the last week or so? eggnog999: if so can you check from yesterday the API log should be there Joshua B: The API log will actually upload with the diagnostics Joshua B: *will actually not upload Joshua B: The Tws log will though eggnog999: yes, i uploaded yesterdays log eggnog999: Ctrl+Alt+U Joshua B: Ok I'm taking a look eggnog999: thx eggnog999: test Joshua B: The log shows several messages "Handling incoming CancelOrder message" Joshua B: Was that intentional? eggnog999: No Joshua B: It appears that cancel order messages were sent approximately 7-8 seconds after the orders were placed eggnog999: yes eggnog999: thats the issue eggnog999: Is TWS responding with correct order quantity to our 3rd party provider (Sierra Chart)? Joshua B: Do you mean the correct position sizes? eggnog999: Yes, Sierra Chart wonders if a Trade Position Quantity is not updated to reflect that the Internal Trade Position Quantity (Parent) has been synchronized to the Service Position Quantity (STOP/TARGET) then that would be the cause of the service position being cancelled. eggnog999: as we get this message "Order 2016-04-29 06:32:07.519 AAPL-OPT-20160429-94-P Synchronized Internal Position to current Service Position. Current Position quantity: 0 Unspecified U1644808" Joshua B: That doesn't look like an actual API message though that would be sent back to Sierra eggnog999: Its not, its the logging Sierra Chart provides eggnog999: but im wondering if IB is not providing position request then request comes back as 0 and in turn the stop/target are then cancelled Joshua B: looking through the log, I haven't seen any position updates being requested or sent back Joshua B: I do see the trade execution reports which indicate that the orders have filled eggnog999: so by not seeing "position updates being requested or sent back" this in turn means the orders are most likely being cancelled? eggnog999: or cancelled by SC? Joshua B: they are being actively cancelled yes eggnog999: ok, so to clear the orders are being cancelled by SC not IB TWS? Joshua B: yes thats correct eggnog999: Can u also do me a favor and copy the API log section and paste into chat? Joshua B: yes it will take a minute eggnog999: ok i can wait thx Joshua B: Here is one snippet- 2016-05-02 12:09:36.850 [BH] INFO [JTS-EServerSocket-65] - [9368395:62:76:1:0:0:0:INFO] Handling incoming PlaceOrder message. ... 2016-05-02 12:09:44.804 [BH] INFO [JTS-EServerSocket-65] - [9368395:62:76:1:0:0:0:INFO] Handling incoming CancelOrder message. 2016-05-02 12:09:44.804 [BH] INFO [JTS-EServerSocket-65] - [9368395:62:76:1:0:0:0:INFO] Cancelling orderId {10720}. 2016-05-02 12:09:44.819 [BH] INFO [JTS-EServerSocket-65] - [9368395:62:76:1:0:0:0:INFO] OrderId {10720} is cancelled. Joshua B: Here is another - 2016-05-02 12:09:44.819 [BH] INFO [JTS-EServerSocket-65] - [9368395:62:76:1:0:0:0:INFO] Handling incoming PlaceOrder message. ... 2016-05-02 12:09:44.819 [BH] INFO [JTS-EServerSocket-65] - [9368395:62:76:1:0:0:0:INFO] Handling incoming CancelOrder message. 2016-05-02 12:09:44.819 [BH] INFO [JTS-EServerSocket-65] - [9368395:62:76:1:0:0:0:INFO] Cancelling orderId {10719}. 2016-05-02 12:09:44.819 [BH] INFO [JTS-EServerSocket-65] - [9368395:62:76:1:0:0:0:INFO] OrderId {10719} is cancelled. |
| [2016-05-04 22:14:12] |
| User713273 - Posts: 409 |
|
Hi SC Support- I'm waiting to hear back from IB, i've uploaded TWS Log and API Log into their API Support Team. Do you still want to connect today? -Adam |
| [2016-05-04 22:16:39] |
| |
|
We apologize we were not able to get to it today, and by the time we are ready it is probably going to be too late for you. Tomorrow will be better. 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 |
| [2016-05-04 22:53:30] |
| User713273 - Posts: 409 |
|
No problem. Find IB TWS trade log, feel free to peruse. Also attached SC Trade Activity Log, both from 5/4. 2016-05-04 11:25:34.061 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:INFO] Sending open order. 2016-05-04 11:25:34.061 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:DET] [5;32;10734;AAPL;OPT;20160506;94;C;SMART;USD;AAPL 160506C00094000;BUY;1;MKT;0.75;0.0;GTC;null;U1644808;O;0;null;9368395;1396322851;0;0;1.7976931348623157E308;;1396322851.0/U1644808/100;null;1.7976931348623157E308;;0;null;;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;2147483647;false;false;false;false;2147483647;3.0;true;true;1.7976931348623157E308;0;0;1.7976931348623157E308;0;None;1.7976931348623157E308;0;0;1.7976931348623157E308;1.7976931348623157E308;2147483647;;2147483647;2147483647;1.7976931348623157E308;null;IB;0;null;false;Filled;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.0814;1.7976931348623157E308;USD;null] 2016-05-04 11:25:34.061 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:INFO] Open order sent. 2016-05-04 11:25:34.061 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:INFO] Sending order status. 2016-05-04 11:25:34.061 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:DET] [3;6;10734;Filled;1;0;0.75;1396322851;0;0.75;9368395;] 016-05-04 11:25:34.656 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Handling incoming PlaceOrder message. 2016-05-04 11:25:34.656 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Started reading message: 2016-05-04 11:25:34.657 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished reading message: 2016-05-04 11:25:34.657 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] a8::[version=40,ID=10735,reqDesc=Symbol=AAPL Type=OPT Expiry=20160506 Strike=94.0 Put/Call=C Exchange=SMART CompExch=null Currency=USD Multiplier=100 IbLocalSymbol=null IbTradingClass=null SecIdType=NULL SecId=null includeExpired=false needLeadFutureMonth=false needContinuousLeadFutureOnly=false newsSource=null Legs=null Special Info=null,transmit=true,combo=null] 2016-05-04 11:25:34.657 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] [40;10735;0;AAPL;OPT;20160506;94;1;100;SMART;null;USD;null;null;NULL;null;2;1;STP;Default;1.7976931348623157E308;Value;0.67;1.7976931348623157E308;0.67;1;U1644808.;true;0;null;ExpireDateTime [null];Reduce on Fill without Block;null;NbboPriceCap=1.7976931348623157E308;TriggerMethod=Default;ContinuousUpdate=false;OptOutSmartRouting=false;VolatilityType=None;PercentOffset=1.7976931348623157E308;NotHeld=false;StockRangeUpper=1.7976931348623157E308;OutsideRth=false;DeltaNeutralAuxPrice=1.7976931348623157E308;Volatility=1.7976931348623157E308;DeltaNeutralOrderType=None;AllOrNone=false;ReferencePriceType=None;Hidden=false;ETradeOnly=true;StockRefPrice=1.7976931348623157E308;OpenCloseAttrib=O;OptionAcctAttrib=c;Delta=1.7976931348623157E308;MinimumQuantity=2147483647;StockRangeLower=1.7976931348623157E308;SweepToFill=false;BlockOrder=false;DisplaySize=2147483647;Clearing=/IB;StartingPrice=1.7976931348623157E308;FirmQuoteOnly=true] 2016-05-04 11:25:34.657 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Start validating message: 2016-05-04 11:25:34.657 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished validating message: 2016-05-04 11:25:34.657 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Started processing message: 2016-05-04 11:25:34.657 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Placing orderId - 10735 2016-05-04 11:25:34.658 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Processing of order {10735} completed. 2016-05-04 11:25:34.658 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished processing message: 2016-05-04 11:25:34.658 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Handling incoming PlaceOrder message. 2016-05-04 11:25:34.659 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished reading message: 2016-05-04 11:25:34.659 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] a8::[version=40,ID=10736,reqDesc=Symbol=AAPL Type=OPT Expiry=20160506 Strike=94.0 Put/Call=C Exchange=SMART CompExch=null Currency=USD Multiplier=100 IbLocalSymbol=null IbTradingClass=null SecIdType=NULL SecId=null includeExpired=false needLeadFutureMonth=false needContinuousLeadFutureOnly=false newsSource=null Legs=null Special Info=null,transmit=true,combo=null] 2016-05-04 11:25:34.659 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] [40;10736;0;AAPL;OPT;20160506;94;1;100;SMART;null;USD;null;null;NULL;null;2;1;LMT;Value;0.83;Default;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1;U1644808.;true;0;null;ExpireDateTime [null];Reduce on Fill without Block;null;NbboPriceCap=1.7976931348623157E308;TriggerMethod=Default;ContinuousUpdate=false;OptOutSmartRouting=false;VolatilityType=None;PercentOffset=1.7976931348623157E308;NotHeld=false;StockRangeUpper=1.7976931348623157E308;OutsideRth=false;DeltaNeutralAuxPrice=1.7976931348623157E308;Volatility=1.7976931348623157E308;DeltaNeutralOrderType=None;AllOrNone=false;ReferencePriceType=None;Hidden=false;ETradeOnly=true;StockRefPrice=1.7976931348623157E308;OpenCloseAttrib=O;OptionAcctAttrib=c;Delta=1.7976931348623157E308;MinimumQuantity=2147483647;StockRangeLower=1.7976931348623157E308;SweepToFill=false;BlockOrder=false;DisplaySize=2147483647;Clearing=/IB;StartingPrice=1.7976931348623157E308;FirmQuoteOnly=true] 2016-05-04 11:25:34.659 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Start validating message: 2016-05-04 11:25:34.659 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished validating message: 2016-05-04 11:25:34.659 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Started processing message: 2016-05-04 11:25:34.659 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Placing orderId - 10736 2016-05-04 11:25:34.660 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Processing of order {10736} completed. 2016-05-04 11:25:34.660 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished processing message: 2016-05-04 11:25:34.724 [CH] INFO [JTS-Async-24] - CM IB PORT U1644808./1/2092908538: Finished loading portfolio 2016-05-04 11:25:34.724 [CH] INFO [JTS-Async-24] - Backout 1 positions BACKOUT 2016-05-04 11:25:34.726 [CH] INFO [JTS-CCPDispatcherS1-30] - Updating base currency: accountSpec=U1644808., currency=USD 2016-05-04 11:25:34.777 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:1:6:INFO] Sending tick price. 2016-05-04 11:25:34.777 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:1:6:DET] [1;6;5;1;0.60;eligible;23] 2016-05-04 11:25:34.777 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:2:6:INFO] Sending tick size. 2016-05-04 11:25:34.778 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:46:6:DET] [46;6;9;33;NZ] 2016-05-04 11:25:34.778 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:46:6:INFO] Generic tick sent. 2016-05-04 11:25:34.834 [CH] INFO [JTS-AsyncNonLocked-25] - SECDEF Sending reqId=UnderlyingECNoDupsReqByConid186 conid=265598 exch=ANYEXCH 2016-05-04 11:25:34.926 [CH] INFO [JTS-CCPDispatcherS1-30] - Order added to the volatility monitoring:1396322852 2016-05-04 11:25:34.929 [CH] INFO [JTS-CCPDispatcherS1-30] - ENCODING STOP PRICE 0.67 2016-05-04 11:25:34.930 [CH] INFO [JTS-CCPDispatcherS1-30] - Order removed from the volatility monitoring:1396322852 2016-05-04 11:25:34.944 [CH] INFO [JTS-CCPDispatcherS1-30] - Order added to the volatility monitoring:1396322853 2016-05-04 11:25:34.946 [CH] INFO [JTS-CCPDispatcherS1-30] - Order removed from the volatility monitoring:1396322853 2016-05-04 11:25:34.998 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:1:6:INFO] Sending tick price. 2016-05-04 11:25:35.013 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:INFO] Sending open order. 2016-05-04 11:25:35.014 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:DET] [5;32;10735;AAPL;OPT;20160506;94;C;SMART;USD;AAPL 160506C00094000;SELL;1;STP;0.74;0.67;GTC;null;U1644808;O;0;null;9368395;1396322852;0;0;1.7976931348623157E308;;1396322852.0/U1644808/100;null;1.7976931348623157E308;;0;null;;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;2147483647;false;false;false;false;2147483647;3.0;true;true;1.7976931348623157E308;0;0;1.7976931348623157E308;0;None;1.7976931348623157E308;0;0;1.7976931348623157E308;1.7976931348623157E308;2147483647;;2147483647;2147483647;1.7976931348623157E308;null;IB;0;null;false;PreSubmitted;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;;null] 2016-05-04 11:25:35.014 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:INFO] Open order sent. 2016-05-04 11:25:35.014 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:INFO] Sending order status. 2016-05-04 11:25:35.014 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:DET] [3;6;10735;PreSubmitted;0;1;0;1396322852;0;0;9368395;locate,trigger] 2016-05-04 11:25:35.014 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:INFO] Order status sent. 2016-05-04 11:25:35.075 [CH] INFO [JTS-ExecCommissionSave-574] - Save daily commission records to file commission.Wed.dat; Time spent on newFile=true size=1 wrote=1 total = 1 took 8 ms 2016-05-04 11:25:35.102 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:INFO] Sending open order. 2016-05-04 11:25:35.103 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:DET] [5;32;10736;AAPL;OPT;20160506;94;C;SMART;USD;AAPL 160506C00094000;SELL;1;LMT;0.83;0.0;GTC;null;U1644808;O;0;null;9368395;1396322853;0;0;1.7976931348623157E308;;1396322853.0/U1644808/100;null;1.7976931348623157E308;;0;null;;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;2147483647;false;false;false;false;2147483647;3.0;true;true;1.7976931348623157E308;0;0;31.89;2;None;1.7976931348623157E308;0;0;1.7976931348623157E308;1.7976931348623157E308;2147483647;;2147483647;2147483647;1.7976931348623157E308;null;IB;0;null;false;Submitted;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;;null] 2016-05-04 11:25:35.103 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:INFO] Open order sent. 2016-05-04 11:25:35.103 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:INFO] Sending order status. 2016-05-04 11:25:35.103 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:DET] [3;6;10736;Submitted;0;1;0;1396322853;0;0;9368395;] 2016-05-04 11:25:35.103 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:INFO] Order status sent. 2016-05-04 11:25:35.333 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:2:6:INFO] Sending tick size. 2016-05-04 11:25:42.727 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:2:6:DET] [2;6;10;0;915] 2016-05-04 11:25:42.727 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:2:6:INFO] Tick size sent. 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Handling incoming CancelOrder message. 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Started reading message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished reading message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] a0::[version=1,ID=10736] 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Start validating message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished validating message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Started processing message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Cancelling orderId {10736}. 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - CANCELSOURCE SEL 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] OrderId {10736} is cancelled. 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished processing message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Handling incoming CancelOrder message. 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Started reading message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished reading message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] a0::[version=1,ID=10735] 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Start validating message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished validating message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Started processing message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Cancelling orderId {10735}. 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - CANCELSOURCE SEL 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] OrderId {10735} is cancelled. 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished processing message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Handling incoming PlaceOrder message. 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Started reading message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished reading message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] a8::[version=40,ID=10737,reqDesc=Symbol=AAPL Type=OPT Expiry=20160506 Strike=94.0 Put/Call=C Exchange=SMART CompExch=null Currency=USD Multiplier=100 IbLocalSymbol=null IbTradingClass=null SecIdType=NULL SecId=null includeExpired=false needLeadFutureMonth=false needContinuousLeadFutureOnly=false newsSource=null Legs=null Special Info=null,transmit=true,combo=null] 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] [40;10737;0;AAPL;OPT;20160506;94;1;100;SMART;null;USD;null;null;NULL;null;1;1;MKT;Default;1.7976931348623157E308;Default;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1;U1644808.;true;0;null;ExpireDateTime [null];Reduce on Fill without Block;null;NbboPriceCap=1.7976931348623157E308;TriggerMethod=Default;ContinuousUpdate=false;OptOutSmartRouting=false;VolatilityType=None;PercentOffset=1.7976931348623157E308;NotHeld=false;StockRangeUpper=1.7976931348623157E308;OutsideRth=false;DeltaNeutralAuxPrice=1.7976931348623157E308;Volatility=1.7976931348623157E308;DeltaNeutralOrderType=None;AllOrNone=false;ReferencePriceType=None;Hidden=false;ETradeOnly=true;StockRefPrice=1.7976931348623157E308;OpenCloseAttrib=O;OptionAcctAttrib=c;Delta=1.7976931348623157E308;MinimumQuantity=2147483647;StockRangeLower=1.7976931348623157E308;SweepToFill=false;BlockOrder=false;DisplaySize=2147483647;Clearing=/IB;StartingPrice=1.7976931348623157E308;FirmQuoteOnly=true] 016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Start validating message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished validating message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Started processing message: 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Placing orderId - 10737 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:INFO] Processing of order {10737} completed. 2016-05-04 11:25:42.780 [CH] INFO [JTS-EServerSocket-63] - [9368395:62:76:1:0:0:0:DET] Finished processing message: 2016-05-04 11:25:42.843 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:2:6:INFO] Sending tick size. 2016-05-04 11:25:42.843 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:2:6:DET] [2;6;8;0;657] 2016-05-04 11:25:42.843 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:2:6:INFO] Tick size sent. 2016-05-04 11:25:42.874 [CH] INFO [JTS-CCPDispatcherS1-30] - Order Canceled - reason: 2016-05-04 11:25:42.874 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:INFO] Sending order status. 2016-05-04 11:25:42.875 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:4:2:DET] Sending error. 2016-05-04 11:25:42.875 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:4:2:DET] [4;2;10736;202;Order Canceled - reason:] 2016-05-04 11:25:42.875 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:4:2:DET] Error sent. 2016-05-04 11:25:42.875 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:DET] [3;6;10736;Cancelled;0;1;0;1396322853;0;0;9368395;] 2016-05-04 11:25:42.875 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:INFO] Order status sent. 2016-05-04 11:25:42.936 [CH] INFO [JTS-CCPDispatcherS1-30] - Order Canceled - reason: 2016-05-04 11:25:42.936 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:INFO] Sending order status. 2016-05-04 11:25:42.936 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:4:2:DET] Sending error. 2016-05-04 11:25:42.936 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:4:2:DET] [4;2;10735;202;Order Canceled - reason:] 2016-05-04 11:25:42.936 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:4:2:DET] Error sent. 2016-05-04 11:25:42.936 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:DET] [3;6;10735;Cancelled;0;1;0;1396322852;0;0;9368395;] 2016-05-04 11:25:42.936 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:INFO] Order status sent. 2016-05-04 11:25:43.043 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:1:6:INFO] Sending tick price. 2016-05-04 11:25:43.244 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:INFO] Sending open order. 2016-05-04 11:25:43.260 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:DET] [5;32;10737;AAPL;OPT;20160506;94;C;SMART;USD;AAPL 160506C00094000;BUY;1;MKT;0.75;0.0;GTC;null;U1644808;O;0;null;9368395;1396322854;0;0;1.7976931348623157E308;;1396322854.0/U1644808/100;null;1.7976931348623157E308;;0;null;;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;2147483647;false;false;false;false;2147483647;3.0;true;true;1.7976931348623157E308;0;0;1.7976931348623157E308;0;None;1.7976931348623157E308;0;0;1.7976931348623157E308;1.7976931348623157E308;2147483647;;2147483647;2147483647;1.7976931348623157E308;null;IB;0;null;false;Submitted;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;1.7976931348623157E308;;null] 2016-05-04 11:25:43.260 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:5:32:INFO] Open order sent. 2016-05-04 11:25:43.260 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:INFO] Sending order status. 2016-05-04 11:25:43.260 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:DET] [3;6;10737;Submitted;0;1;0;1396322854;0;0;9368395;] 2016-05-04 11:25:43.260 [CH] INFO [JTS-CCPDispatcherS1-30] - [9368395:62:76:1:0:3:6:INFO] Order status sent. 2016-05-04 11:25:43.345 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:46:6:INFO] Sending generic tick. 2016-05-04 11:25:43.345 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:46:6:DET] [46;6;6;45;1462386353] 2016-05-04 11:25:43.345 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:46:6:INFO] Generic tick sent. 2016-05-04 11:25:43.345 [CH] INFO [JTS-usoptDispatcherS6-106S6-107] - [9368395:62:76:1:0:2:6:INFO] Sending tick size. |
| image (6).png / V - Attached On 2016-05-04 22:53:22 UTC - Size: 243.05 KB - 305 views |
| [2016-05-05 21:15:50] |
| User713273 - Posts: 409 |
|
Message ticket from IB API Support. Please let me know if we can connect today. Your log file snippet has been received and reviewed. As before, the section of the log sent does not show any requests through the API for current account or portfolio values. If these values are needed for the algorithm in Sierra Charts they would have to be specifically requested, and the requests would appear in the log file along with any returned information. The log file does show several orders being placed, as well as the order status callbacks ("Submitted", "Filled", ...) and execution reports. By default, these are the only types of messages which are passed back through the API. Other values such as current portfolio positions have to be specifically requested. The log also shows order cancellations as before for the limit and stop orders about 7-8 seconds after they were placed. Unfortunately from the Tws log alone it cannot be determined why Sierra Charts cancelled these orders. If it would be of use, of course Sierra Charts could always contact the API Support Group here directly with any questions. Best Regards, Joshua B API Support, Technical Assistance Center Interactive Brokers |
| [2016-05-05 22:35:26] |
| |
|
We are looking all of this more recent information over. Make sure your current telephone number is set here: https://www.sierrachart.com/usercp.php?page=ManageAccountInfo And would you be available around 6 p.m. or later today? 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: 2016-05-05 22:35:36
|
To post a message in this thread, you need to log in with your Sierra Chart account: