The following steps are required to change over an openFT instance to another computer:
Stop the instance on the original computer (STOP-FT).
Unload the instance on the original computer (DELETE-FT-INSTANCE). This unlocks all of the files required by openFT (request file, transfer files, etc.).
Import the variable files, the network address (virtual BCAM host) and all of the files required by the requests to the destination computer. This can contain, among other things, the switching over of one or several pubsets).
It is recommended to import all files of the configuration user ID when changing over.
Load the instance on the destination computer (CREATE-FT-INSTANCE).
Start the instance on the destination computer (if this does not occur automatically, then use SET-FT-INSTANCE, START-FT).
After importing an instance to another computer, openFT finishes the (under some circumstances restartable) requests, whose admissions were already checked before importing. The new environment must have the same prerequisites as the old computer (the same IDs with the same file access admissions).
All pubsets that are accessed by requests must be available. All requests whose pubsets are not accessible during restart attempts are aborted.
On the new computer, the network view must be the same as that on the old computer. This means that, from the point of view of the BCAM, the same host names for partner computers must be available and they must refer to the same partner computer. The network address of the (virtual) host on which the instance is running, must be seen from the outside the same as from the address of the host, on which the instance was previously running.
The name of the instance must be the same on all of the computers, since, for example, it is used for qualifying temporary files.