3.7.2

This Release correctly handles the changed label on the login button when logging in to the live account using Gateway 947.

If you have already installed IBC 3.7.0 or 3.7.1, you just need to extract the IBC.jar file from the zip to your IBC folder, replacing the existing file. You should also do the same with the version file, to ensure that IBC log files contain the correct information.

3.7.1

This Release further enhances IBC to handle the changed button labels on the Exit Session Setting dialog in TWS 974.

You will need to use this version if you use TWS 974 and you have IbAutoClosedown=no in your config.ini file, ie if you are using IBC to keep TWS running continuously, bypassing the TWS autologoff feature.

If you have already installed IBC 3.7.0, you just need to extract the IBC.jar file from the zip to your IBC folder, replacing the existing file. You should also do the same with the version file, to ensure that IBC log files contain the correct information.

3.7.0

This Release adds support for TWS 947. Just set TWS_MAJOR_VRSN to 974 in your start scripts as usual.

Prior versions of TWS will continue to work: no changes necessary.

A few minor corrections to the User Guide have been made.

If you are currently using IBC 3.6.0, you only need to extract the IBC.jar file from the zip file to replace the existing version in your IBC folder. All other changes are irrelevant to correct operation, unless you are a macOS user, in which case you may want to use the revised top-level script files (see 'Bug fixes' below).

Bug fixes:

• fixed the macOS gatewaystartmacos.sh and twsstartmacos.sh scripts to allow TWS/Gateway to be started in a new terminal session

• fixed a problem where the CommandServer's BindAddress was being accessed using the wrong setting name (PR #18)

• fixed the failure of IBC 3.6.0 to work with TWS 947 (Issue #27)

3.6.0

This is the first release of IBC since the fork from IBController.

IMPORTANT NOTES

1. There are 3 different zip files included in this release, for Windows, Linux and macOS. Choose the appropriate one for your system.

2. The User Guide refers to the IBC User Group: this does not currently exist, so use the IBController User Group instead. The latter will be renamed to become the IBC User Group in due course.

There are some key differences between IBC and IBController that you'll need to be aware of if you're switching to IBC from IBController. You can find more information about this in the last section of the IBC User Guide.

At the date the fork was made, the latest IBController release was IBController 3.4.0, and the repository contained 22 commits which had not yet been included in a release, plus one pull request which had not yet been applied. None of these were of particular significance, but taken together they represent a significant improvement over IBController release 3.4.0. The intention was that the pull request together with the remaining commits since release 3.4.0 would form a new IBController release 3.5.0, but this has not yet happened.

All of these changes have been carried through to this first release of IBC, and a number of further improvements have been made: hence the decision to label this release as 3.6.0. In future, it is not likely that there will be any correlation between IBC and IBController release labels.

The changes and improvements that have been made in this release include the following:

• bug fix: the Windows scripts now correctly delete old IBC logfiles

• bug fix: the Windows scripts now trap attempts to use a logfile that is already in use by another process

• bug fix: when using the /INLINE argument, the relevant window was incorrectly closed on exit from IBC

• bug fix: the Stop.bat script can now be run from any folder

• the 'ClosedownAt' setting can now specify a daily closedown time. This is useful for Gateway users who do not want to run the Gateway continuously

• separate ZIP files for each platform are now included in the release

• error handling has been improved

• IBC log entries now include the date as well as the time. This can be helpful when logs span several days

• the Windows scripts now write additional diagnostic information to the banner window

• the IBC command server is not started unless the CommandServerPort setting is set to a non-zero value

• the CommandServerPort setting is logged when the command server starts