[z/OS]

Collecting information for MFT for z/OS agent 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) agent problem on z/OS®.

About this task

Managed File Transfer agent problems include:
  • The agent failing to connect to, or being disconnected from, its agent queue manager.
  • The agent hanging.
  • The agent stopping unexpectedly.
  • The agent going into recovery.
  • The fteListAgents or fteShowAgentDetails commands, or the IBM MQ Explorer Managed File Transfer plug-in, showing incorrect, or out of date, status information for the agent.
  • The agent failing to report any status information.

Procedure

  1. Initially, review the following topics to see whether they help 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 agent.
    • The name of the agent queue manager.
    • The version of Managed File Transfer for z/OS that the agent is using.
    • The version of IBM MQ for z/OS for the agent queue manager.
    • Details of how the agent is started (for example, is it running as a started task?).
    • Any error messages that are seen in the agent's event log (output0.log) when the issue occurs.
    • An agent trace covering the time of the issue. For more information about how to collect the trace, see Tracing Managed File Transfer for z/OS agents.
      • If the agent is experiencing the problem when communicating with its agent queue manager (for example, the agent's event log contains error messages that include an IBM MQ reason code such as 2009 – MQRC_CONNECTION_BROKEN), collect the trace using the trace specification =all.
      • For all other issues, collect the trace using the trace specification com.ibm.wmqfte=all.
    • Three Javacores taken 30 seconds apart, if the agent is hanging. In order to do this, run the fteSetAgentTraceLevel command with the -jc option set, as shown in the following example:
      fteSetAgentTraceLevel -jc <agent_name>

      If the command does not cause the agent to generate a Javacore, then you should send a SIGQUIT signal to the agent process.

    • An archive containing the agent's log files, configuration files, trace files and Javacores, if applicable. For more information about how to create the archive, see Creating an archive of troubleshooting information for MFT for z/OS.
    • The job logs for the coordination queue manager and agent queue manager.