Network File Transfer (NFT) is the network service
that copies disk files. The files may be copied to the same computer
or from one computer in a network to another. You can use Network
File Transfer to transfer a file between any two systems in an NS 3000/iX
network, even if both of those systems are remote from your own.
You can also use it for purely local transfers on a single HP 3000.
This chapter explains how to use the interactive command DSCOPY
to interactively invoke NFT, and the use of intrinsics that enable
NFT to be invoked from within a program. The first part of this
chapter explains how to use NFT to interactively copy files. The
second part, "Programmatic NFT", describes how
to use intrinsics to invoke NFT from within a program.
Limitations
Following are NFT limitations:
NFT only works with filenames in the
traditional MPE namespace. It does not work with filenames in the
HFS (POSIX-compliant) namespace. NFT does not recognize HFS directories
or filenames that contain slashes as directory delimiters. For example,
it will not work properly with filenames such as "./FILEa,"
or "/usr/include/stdio.h".
NFT only works with traditional MPE record-oriented
files; that is files with fixed (F), variable (V), or undefined
(U) record types. It does not work with files that have the POSIX-compliant,
bytestream (B) or directory (H) types.
