Using DTC Server for Data and Trading in Another Sierra Chart Instance

Instructions For Sharing Data Using Sub Instances (Easiest And Recommended Method)

1. Start another instance of Sierra Chart by selecting File >> New Instance in an existing running instance of Sierra Chart. This can only be done from the main instance of Sierra Chart, not a sub-instance.
2. To automatically start new instances of Sierra Chart on startup of the main instance, the instance numbers can be specified as a comma separated list in Global Settings >> General Settings >> Instances to Run on Startup. For example, you can enter a 2 in that edit box to automatically start a second instance. Or enter 2, 3 to start a second and third instance automatically.
3. When using File >> New Instance, a new instance is automatically updated to the same version as the main instance of Sierra Chart.
4. Each instance of Sierra Chart maintains its own copy of global settings, Chartbooks and chart data files. The first time a new instance is created, it receives a copy of the global settings and Chartbooks from the main instance.
5. To open a chart which will be fed by the DTC Server from the main instance of Sierra Chart, select File >> Find Symbol in the new instance of Sierra Chart.
6. The Find Symbol list will initially be empty because the Symbol Settings have to be requested. Wait a moment for them to be received and then the list will fill in.
   
   If this does not occur within about 5 to 20 seconds, then follow the procedure to perform an Update of the Symbol Settings to get them. It is necessary to have the proper Symbol Settings in an instance of Sierra Chart which is connected to the DTC Server of another instance.

Historical Data and Missing Historical Data

All historical Intraday and Daily data for a Symbol in an instance of Sierra Chart started using New Instance, is downloaded from the existing Intraday or Daily chart data file in the Main Instance if the file exists.

If the file exists, but it is not up to date with the current data, then the current data will be downloaded into the file first before the data is served to client instances of Sierra Chart.

If a chart data file does not exist in the Main Instance, then the data will be first automatically downloaded for that Symbol and chart data type from the connected Data or Trading service the Main Instance is set to use. When this historical data download is done, then the data is served to client instances of Sierra Chart.

If there is any missing or incorrect Historical Daily or Intraday chart data in the client instance of Sierra Chart which is connected to the Main Instance, then go to the the main instance of where you selected File >> New Instance) and open the same type of chart (Historical or Intraday) for the same Symbol and correct any missing or incorrect data issues there first.

Refer to the following sections to solve a missing or incorrect data issue.

• Missing or Incomplete Intraday Chart Data
• Missing Historical Chart Data (Daily, Weekly, Monthly, Quarterly, Yearly Charts)
• Deleting and Re-downloading Data (Intraday Charts)
• Correcting Data Errors by Downloading the Data Again (Historical Daily, Weekly, Monthly, Quarterly, Yearly Charts)
• Downloading/Viewing More Historical Intraday Data

Once you have corrected the missing or incorrect data issue in the Main Instance of Sierra Chart, then re-download the data in the sub instances of Sierra Chart by re-downloading all of the data in the chart by going to the chart and selecting Edit >> Delete All Data and Download. You just need to do this once per symbol and not for each chart.

Simulated Trading in a Sub Instance

Simulated trading can be performed two different ways in a sub instance of Sierra Chart.

Viewing Trading Data in Sub instance from Main Instance

To view trading data on a chart in a sub instance, for trading activity occurring in the main instance, it is necessary to disable/uncheck Trade >> Trade Simulation Mode On on the menu.

The next step is to follow through all of the steps in the Viewing Simulated and Non-Simulated Working Orders and Trade Position section on the Chart Trading page.

Differences with Order Handling Between Main and Sub Instance

When using multiple Target Attached Orders, the parent order is split up into multiple orders to match the quantity of each Target order. These multiple parent orders are linked together. When you adjust the price of one of them the others will automatically adjust along with it. There is a link between these paired orders.

If you go to a different instance of Sierra Chart as compared to where the orders were submitted from, the link between these orders does not exist. If you adjust the price of one of these parent orders, the others will not adjust.

To avoid this issue only adjust the order from the instance it was initiated in.

Related to this is that since the parent order is split up into multiple orders, when you cancel one of these parent orders in an instance other than where the orders were originally entered from, you will have to cancel each order individually and get multiple order confirmations.

A similar case is true of the order association lines between Target and Stop order. You will only see these lines in the instance where the orders were entered from. You will not see them in other instances. The information necessary for these lines only exists in the instance where the orders were submitted from. However, you will see the order association lines in the main/server instance of Sierra Chart. Since it is aware the Target and Stop orders are in an OCO group.

Using the Correct Trade Account (Rejections Related to Simulation Mode)

When trading in a sub instance of Sierra Chart and Trade >> Trade Simulation Mode On is disabled, it is necessary to use the Trade Account in the sub instance which corresponds to the Trade >> Trade Simulation Mode On setting in the main instance of Sierra Chart.

When Trade >> Trade Simulation Mode On is enabled in the main instance, then you can only use simulated trading accounts in the sub instance (Example: Sim1). Refer to Selecting Trade Account.

When Trade >> Trade Simulation Mode On is disabled in the main instance, then you can only use non-simulated trading accounts in the sub instance. Refer to Selecting Trade Account.

If the incorrect Trade Account is being used in the sub instance, you will see a message like this in Trade >> Trade Service Log in the sub instance after submitting an order:

To trade live from a sub instance, it is necessary that Trade >> Trade Simulation Mode On is disabled both in the sub instance and in the main instance of Sierra Chart. And that you have selected a non-simulated trading account. Otherwise, the below rejection message will be given when submitting an order from the sub instance.

Resolving DTC Protocol Server Port Number Conflicts

Normally only one instance of Sierra Chart that you are running on the same computer should be set to be a DTC Server and have the DTC Protocol Server enabled.

If other instances of Sierra Chart which are running your computer system at the same time also have the DTC Protocol Server enabled (Global Settings >> Sierra Chart Server Settings >> DTC Protocol Server >> Enable DTC Protocol Server = Yes, you need to make sure there are not port number conflicts. In other words, they need to be using different port numbers.

Client instances of Sierra Chart which connect to a DTC Server instance of Sierra Chart must have the Global Settings >> Sierra Chart Server Settings >> DTC Protocol Server >> Enable DTC Protocol Server option disabled to avoid port number conflicts.

Once you have disabled this option, you should not have to continue with the further instructions. Unless more than one instance of Sierra Chart is running as a server on the same computer.

Below is an example of what you will see in the Message Log indicating a port number conflict.

Follow through the below steps to resolve port number conflicts for each installation of Sierra Chart that you have running.

1. Exit from any sub instances of Sierra Chart, started with File >> New Instance.
2. Go to one of the instances of Sierra Chart you have running on your system and select Global Settings >> Sierra Chart Server Settings >> DTC Protocol Server.
3. Make sure the Enable DTC Protocol Server option is enabled and make a note of the Listening Port and Historical Data Port numbers.
4. Press OK.
5. Go to the next instance of Sierra Chart on your system and select Global Settings >> Sierra Chart Server Settings >> DTC Protocol Server.
6. Either uncheck the Enable DTC Protocol Server option or set the Listening Port and Historical Data Port numbers to different port numbers than what are currently used in other instances of Sierra Chart. You can use any port numbers. They should be in the range of 10000 through 60000.
   
   Make sure you are not using a port already in use on your system or used by another instance of Sierra Chart. You can determine what ports are in use through the netstat program. Commandline: netstat -a -b.
   
   Unless these other instances of Sierra Chart should be functioning as a DTC server, which is unlikely in most cases, then uncheck Enable DTC Protocol Server.
7. In the case of an instance of Sierra Chart started with File >> New Instance and where the Global Settings >> Data/Trade Service Settings >> Service in that instance is set to DTC - Sub Instance, then you must uncheck the Enable DTC Protocol Server option.
8. Press OK.
9. Repeat the steps above starting with step 5 for other instances of Sierra Chart on your system.

Automatically Copying Files from the Main Instance to Sub Instance

The below procedure will start with a new/fresh copy of a sub instance and then copy all of the main Sierra Chart installation folder to the sub instance folder except for Intraday and Daily chart data files, and the current Internal Order ID file. These files copied include Chartbook and Spreadsheet files.

Any existing sub instance files will be lost because this procedure explains deleting them.

1. Exit from any sub instances you are currently running. Go to the Sierra Chart installation folder through your operating system file manager. This is usually C:\SierraChart. You can find this folder through Window >> Message Log. Refer to the Program path line near the top of the log. Example: Program path: C:\SierraChart\.
2. Delete the SierraChartInstance_2 subfolder. This will be the first, folder for a sub instance. This will be the folder you will usually want to delete. You may want to make a backup of it first. Other sub instances may exist, and will have this folder format: SierraChartInstance_#, where the # represents the instance number.
   
   The main instances always Considered instance 1.
3. Start a sub instance through File >> New Instance.
4. The sub instance will now have access to the main instance Chartbooks and you can open them in the sub instance in the same way through File >> Open Chartbook.
5. Any charts you no longer want to use in the main instance among the currently open Chartbooks, can be closed by selecting the chart from the CW menu and then selecting File >> Close Active Window. After this Save the Chartbook with File >> Save.