Guidelines for transferring files

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

Read the relevant topics for further information.

• Transfer 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 we are transferring from and to.
• Transfer 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.
• Transfer 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 we 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.
• Transfer 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.
• Transfer 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.
• Transfer files to or from protocol bridge agents
  We can transfer files to and from an FTP or SFTP file server outside your Managed File Transfer network using a protocol bridge agent.
• Transfer 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 we want to convert the data in the files, consider the information in this topic.
• Transfer 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.
• Transfer 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.
• Transfer 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 administration reference

Related reference

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