[z/OS]

Collecting information for MFT for z/OS managed transfer problems

The troubleshooting information that you need to collect and send to IBM® if you need assistance from IBM Support with a Managed File Transfer (MFT) managed transfer problem on z/OS®.

About this task

Problems related to Managed File Transfer managed transfers include:
  • A managed transfer failing unexpectedly.
  • A managed transfer going into recovery and not completing.
  • A managed transfer getting stuck.

Procedure

  1. Initially, review the information in Troubleshooting managed transfer problems to see whether that helps you to resolve the problem.
  2. If you still require assistance, collect the following information and send it to IBM Support:
    • The name of the source agent for the managed transfer.
    • The name of the source agent queue manager.
    • The version of Managed File Transfer or Managed File Transfer for z/OS that the source agent is using.
    • The version of IBM MQ or IBM MQ for z/OS for the source agent queue manager.
    • The name of the destination agent for the managed transfer.
    • The name of the destination agent queue manager.
    • The version of Managed File Transfer or Managed File Transfer for z/OS that the destination agent is using.
    • The version of IBM MQ or IBM MQ for z/OS for the destination agent queue manager.
    • If the source and destination agent queue managers are different, details of how the queue managers are connected together (that is, through sender/receiver channels or an IBM MQ cluster).
    • The transfer identifier for the managed transfer.
    • Details of how the managed transfer request was created (that is, was it generated by a resource monitor, the fteCreateTransfer command, the IBM MQ Explorer Managed File Transfer plug-in, or something else?).
    • Details of any error messages that are related to the managed transfer in either the source agent or destination agent's event log (output0.log).
    • A trace from both the source and destination agents that covers the time when the issue occurred. For more information about how to collect the trace, see Tracing Managed File Transfer agents on Multiplatforms or Tracing Managed File Transfer for z/OS agents. The trace should be collected using the trace specification com.ibm.wmqfte=all.
    • An archive from the source agent containing the agent's log files and configuration files and an archive from the destination agent, containing the agent's log files and configuration files. For more information about how to collect the archives for the source and destination agents, see Creating an archive of MFT troubleshooting information or Creating an archive of troubleshooting information for MFT for z/OS.
    • runmqras output for the source agent queue manager and the destination agent queue manager, if they are running on a platform other than z/OS. For more information about how to collect the runmqras output for the source agent queue manager and the destination agent queue manager, see Collecting troubleshooting information automatically with runmqras.

    When you are investigating issues related to managed transfers, it is often useful to draw a simple diagram, as shown in the following example, that shows the agents and the agent queue managers. This diagram allows you and IBM Support to see how the agents and the agent queue managers are connected, which can help to identify possible issues within the IBM MQ network that might cause managed transfers to enter recovery or get stuck.

    Figure 1. Example of a simple diagram showing how a source agent, AGENT1, and a destination agent, AGENT2, and their agent queue managers, MQ01 and QM2 are connected.
    A simple diagram showing how the agents and the agent queue managers are connected.