What to do if your transfer does not complete

If your transfer does not complete we can carry out a number of problem determination steps to investigate the cause.

Use the following flowchart to help you to diagnose problems and decide what action to take next:

Flowchart key:

1. Check the agent output0.log for errors. If the agent reports it has successfully started, but neither IBM MQ Explorer nor fteShowAgentDetails report the agent as running, then check the connectivity between the agent queue manager and the coordination queue manager. It may be that a queue manager to queue manager channel is unavailable.
2. If the source agent lists the transfer ID as an In progress transfer but the destination agent does not, there might be a connectivity issue between the source and destination queue managers. Use the ftePingAgent command from the destination agent machine to the source agent using the destination agent queue manager as the command queue manager, in the command.properties file. We can also run this command the other way round, from source to destination.
3. If both the source and destination agents list the transfer ID as In progress, this suggests there has been a connectivity issue between the source and destination queue managers since the transfer was initiated. Use the ftePingAgent command from the destination agent machine to the source agent using the destination agent queue manager as the command queue manager, in the command.properties file. We can also run this command the other way round, from source to destination.
4. If we have been round this loop already, check whether either of statements are relevant to your situation:
   • Both source and destination agents report as Running, but no transfer is listed. Either the transfer request did not reach the agent command queue, or the agent although reporting as Running, is no longer monitoring the command queue. Check for errors in the source agent output0.log. Use the ftePingAgent command from the same machine the transfer was sent from, to the source agent, to verify the connectivity between the command queue manager and the agent queue manager, and that the agent is servicing the command queue.
   • Both source and destination agents report as Running, and the transfer is listed as In progress, recovering. Use the ftePingAgent command from the destination agent machine to the source agent using the destination agent queue manager as the command queue manager, in the command.properties file. We can also run this command the other way round, from source to destination.

Parent topic: MFT general troubleshooting