Search results

There as a discussion about creating smart router combo orders for the crack spread. Apparently, this is not possible.

I believe the answer is yes based on my understanding, but I don't have multiple accounts to speak from experience.

I've made the suggestion on IB's poll in the past that borrowing costs need to be more transparent.... I guess that suggestion sitll remains valid today.

Has anyone had experience with IB's Smart router with synthetic call combos (buy stock, buy put)? I was trying to use them and ran into two issues: 1. On a fairly liquid issue (a top 10 by dollar volume on NYSE for the day), even with a relatively wide spread (like 7c) to the implied...

I am pretty sure IB submits the iceberg as such to the ECN vs holding back the reserve size.... If you hold back the reserve size, you can miss a fill opp.

This appears to be a totally different issue from what I was experiencing. I must admit to not having seen this one before.

You lose about $225-$275 in foregone interest, after tax, per year (for US residents). It is what it is..... if it isn't worth it for a given person, it isn't. If it is, it is.

It's 10K equiv (approx) per currency, but not yet again for futures bec the balances are automatically moved between futures and stocks/options. The futures account, as far as I can tell, exists only to meet regulatory requirements and never had free cash balances in it. Also you don't need...

This may be a proxy problem: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6539601 Do you use a proxy at work? A workaround would be to download a local copy of tws instead of running it from the network.

After an exchange w/DAV, this issue appears to be resolved. No incidents all day today (Fri).

Done -- and coincidentally it just happened again a bit after I sent the requested files, though this time w/o an SSL Mac exception. So I sent a follow-up with the tail of the log that should make it easy to isolate the most recent incident. This time I do not have store settings on server...

You are right!!!! It is unlikely to be a network error. After looking through the log, it appears that the problems start with the following --- an SSL MAC error. With network, I would assume a lost connection or truncated data, but a MAC error sounds like the server calculated the wrong...

Thx. Well, why it disconnected is less the concern as I can believe a glitch -- or in any case, network glitches WILL occur. The going crazy thereafter and inability to reestablish connection is the more troubling issue. This is definitely new TWS behavior with more recent versions. I've...

As they say, misery loves company. (Well at least company means it's more likely for the problem to be found and fixed if multiple users are experiencing it.) It just happened to me two more times today making it 4 times today and once yesterday. I noticed that I was pushed 879.5 but the...

I noticed this once yesterday but twice today. I suspect it's due to a new rev of TWS that came in yesterday (I'm on 879.4). I did open a ticket after seeing it twice today (so 3 times in all) but wondering if anyone else has seen it. It starts with a pinkout -- which may be due to a...

Yesterday (11/5), I did see a login issue -- hung after entering the response to the challenge. But a 2nd attempt (after killing that java instance) worked. I assumed it was my end but I guess maybe not. Today, I am seeing a few occassional pinkout/reconnects (maybe 5 or 6 since market...

Thx for the update -- the rest of us appreciate knowing what to watch out for.

IB does not yet have full redundancy. I do recall on the most recent quarterly conference call hearing something about backup systems -- but didn't jot down the details..... Maybe it's already under way. During the market stress of August and also of this past Thu, I have found TWS to be...

A light hearted thread for a change.... Suggestion: Next time you hear the music on hold, just run it through Verizon Wireless' SongID or AT&T's similar service.

I've been eyeing this thread for the past ~2 wks waiting for some sort of resolution before commenting. I'm glad that IB got to the bottom of the situation and hopefully some reasonable settlement. The double click does seem to be a user error, and protecting against it is good...