Starting and stopping openFT

Starting openFT

openFT is started with the START-FT command. Care must also be taken to ensure that all pubsets are available, as otherwise any locally submitted request that requires an unavailable pubset will be terminated with an error message. If this happens, the user cannot be informed of the circumstances by an event list or a job variable.

START-FT starts all applications that have been activated using the command MODIFY-FT-OPTIONS .. ACTIVE-APPLICATIONS=.

If multiple instances are used on one computer, each instance must be started individually. Individual instances can be set up so that they are automatically started on executing the command START-SUBSYSTEM, see the section “Using openFT instances”).

If the openFT option HOST-NAME is not set at start time then the real BCAM host is used. If multiple instances have to be started in a system then the host name must be set using the /MODIFY-FT-OPTIONS command at all but one of them.

Stopping openFT

Using STOP-FT terminates openFT in the current instance. When file transfer is terminated, non-restartable requests are aborted. Local requests continue to be accepted even after STOP-FT. The requests are stored in the request queue until openFT is restarted. When START-FT is entered again, the requests are processed in sequence.