Configuring the SSTransfer custom server

The SSTransfer custom server has some command line parameters that you can set to help you debug problems, or to fine-tune the operation of the custom server.

The parameters are defined in Table 1. For information on how to set the parameters, see Setting configuration options.

Table 1. Configuration options for the SSTransfer custom server


Default setting




Provide extra debugging information (in addition to the information that always gets sent). Valid values are 0 (none) to 4 (everything). To set the logging level to 3, specify –d3 .



A fully qualified file name where trace output is to be written, for example -f/home/dtuser/sstransfer.log. The SSTransfer custom server will continue to write some critical information to DTstatus.out.

Setting configuration options

To set one or more of the configuration options, follow the procedure below:

  1. From the Welcome window, click on Applications —> Custom Servers
  2. Setting a command line parameter for the custom server: Highlight the SSTransfer custom server.
  3. Click Server —> Open.

    The system displays the Custom Server (SSTransfer) window.

  4. Click File —> Properties.

    The system displays the Properties (SSTransfer) window.

  5. Enter your command line parameters in the panel titles main() args.
  6. Click OK.

    The system closes the Properties (SSTransfer) window.

  7. In the Custom Server (SSTransfer) window, click File —> Save.
  8. Restarting the custom server: Open the Custom Server Manager window by clicking Welcome —> Operations —> Custom Server Manager.

    The system displays the available custom servers in a window.

  9. If the SSTransfer custom server Run Status is set to Waiting, stop the custom server by clicking Run Status —> Stop.

    The Run Status button should display None, after a short while.

  10. Start the SSTransfer custom server by clicking Run Status —> Start.

    After a short while the Run Status button should display Waiting. The new command line parameters are now in effect. If the Run Status remains at None, there is probably an error with one of the command line parameters. Check the error log for details.