Guidelines for transferring files

Guidelines for transferring files

Depending on the operating system you are transferring from and to and whether you are transferring in binary or text mode, there are guidelines on what behavior to expect.

Read the relevant topics for further information.

Transferring files and data sets between z/OS and distributed systems
We can transfer files and supported data set types between z/OS® and distributed file systems by using Managed File Transfer. Review the following behavior carefully, which is dependent on the type of system you are transferring from and to.
Transferring between data sets on z/OS
We can transfer between z/OS data sets using Managed File Transfer. Review the following behavior carefully to ensure your data sets are transferred correctly.
Transferring data sets to and from Connect:Direct nodes
We can transfer data sets between Managed File Transfer agents and IBM® Sterling Connect:Direct® nodes using the Connect:Direct bridge. We can specify a data set as the transfer source, transfer destination, or both.
Mappings between Connect:Direct process statement parameters and BPXWDYN keys
When you submit a transfer request for a data set where either the source or destination is a Connect:Direct node, any supported BPXWDYN keys that you provide are converted to a format that is accepted by Connect:Direct processes.
BPXWDYN properties you must not use with MFT
Some BPXWDYN options must not be specified when using the fteCreateTemplate command, the fteCreateTransfer command or the bpxwdynAllocAdditionalOptions property in the agent.properties file.
Transferring text files with MFT
Text file transfer involves converting the code page of a file from one code page to another. Text file transfer also involves converting CRLF (carriage return-line feed) characters between systems. This topic summarizes text file transfer behavior of Managed File Transfer.
Transferring text files between Connect:Direct and MFT
Text transfer involves converting the code page of a file from one code page to another. Text file transfer also involves converting CRLF (carriage return line feed) characters between systems. This topic summarizes text file transfer behavior in transfers between a Managed File Transfer Agent and a Connect:Direct node.
Transferring files to or from protocol bridge agents
We can transfer files to and from an FTP or SFTP file server outside the Managed File Transfer network using a protocol bridge agent.
Transferring files to or from IBM i systems
If you transfer files to or from IBM i systems using Managed File Transfer in text mode and you want to convert the data in the files, consider the information in this topic.
Transferring physical files located in QSYS.LIB on IBM i
Managed File Transfer supports the transfer of physical file members in the QSYS.LIB file system between two IBM i systems. Consider the following information when you request file transfers of physical file members.
Transferring save files located in QSYS.LIB on IBM i
Managed File Transfer supports the transfer of save files located in the QSYS.LIB file system between two IBM i systems. Consider the following information when requesting file transfers of save files.
Transferring generation data groups (GDGs)
Managed File Transfer supports generation data groups (GDGs) for source and destination data sets on z/OS. Absolute and relative GDG names are supported. When you write to a new generation, the base GDG must exist.
Use wildcard characters with MFT
We can use wildcard characters when you specify source file names and source file paths for file transfers. This allows you to select multiple files simultaneously.
Parent topic: Managed File Transfer

Related reference

Transferring files and data sets between z/OS and distributed systems
Transferring between data sets on z/OS
Transferring data sets to and from Connect:Direct nodes
Mappings between Connect:Direct process statement parameters and BPXWDYN keys
BPXWDYN properties you must not use with MFT
Transferring text files with MFT
Transferring text files between Connect:Direct and MFT
Transferring files to or from protocol bridge agents
Transferring files to or from IBM i systems
Transferring save files located in QSYS.LIB on IBM i
Transferring generation data groups (GDGs)
Use wildcard characters with MFT