Unsolicited File Transfer
Here, "unsolicited" does not mean "unwanted" but rather that the recipient did not fetch the file and the sender might not have sign-on credentials on the target host.
UFT is sometimes expanded to "Universal File Transfer", a name with less baggage. There is also the title "Sender-Initiated File Transfer" or SIFT, which usually refers to an offline or batch variant of UFT protocol.
This repository has both POSIX and VM/CMS components.
The POSIX (Unix, Linux, and other Unix-like systems)
source is in the src directory.
The usual sequence of steps to build UFT on a POSIX system is ...
./configure
make
make install
make clean
The configure script is not very sophisticated.
The only option it takes is --prefix.
The sf UFT client command sends files to UFT servers.
Use either "-a" for plain text files or "-i" for binary files.
Files received by the UFT server are held in a sort of "loading dock"
for disposition by the target user. There are two commands: rls
to list files waiting on the dock, and rcv to receive selected files.
UFT mimics the operation of IBM's RSCS and other IBM mainframe file transfer networking (specifically NJE). So naturally, there is a VM/CMS implementation of UFT. The VM/CMS implementation was not originally maintained in this project but is now included in this new home.
See the cms directory.
The VM/CMS UFT implementation is intended to work with existing
commands and utilities on the VM/CMS system. rdrlist and receive
remain unchanged. There is a UFT-enabled sf command which can be used
in place of stock sendfile.
Pre-compiled and otherwise runnable packages are available from