Troubleshooting managed transfer problems

Use the following tasks to help you to resolve issues with managed transfers.

Troubleshooting an MFT transfer that does not complete
If your transfer does not complete, use a flowchart to investigate the cause..
Troubleshooting a file transfer that might be stuck
On a heavily loaded system, or when there are network problems between the source and destination agents, transfers can occasionally appear to be stuck in a queued or recovering state.
Troubleshooting a failed file transfer to a clustered queue
When using Managed File Transfer to transfer a file into a queue, if you use a destination that is a clustered queue, or an alias to a clustered queue, you might get reason code 2085, or 2082. This issue is resolved if you set up a remote queue definition that points to the clustered queue.
Troubleshooting a scheduled file transfer that does not run or is delayed
If you have a scheduled transfer that does not run when it is due or is delayed, it might be because the agent is processing commands on its command queue. Because the agent is busy, scheduled transfers are not checked and are therefore not run.
Troubleshooting errors when transferring IBM i save files
If you use Managed File Transfer to transfer the same IBM® i save file several times, the transfer might fail.
Troubleshooting transfers that fail with error BFGIO0341E
If a managed transfer is transferring a file into a location that is being monitored by an external process, the transfer might fail with the error: BFGIO0341E: The rename of temporary file destination_filename.part to destination_filename failed because the temporary file does not exist. This is because of the way that the destination agent for managed transfers uses temporary files when writing a destination file.

Parent topic: Troubleshooting Managed File Transfer problems

Related tasks

Troubleshooting common MFT problems

Related reference

Return codes for MFT