IBM Support

Collect IBM MQ MustGather data to solve managed file transfer problems on Linux, UNIX, Windows and IBM i

Troubleshooting


Problem

An IBM MQ or WebSphere MQ File Transfer Edition managed file transfer agent, database logger or other command is reporting a problem or failing to work properly, and you need to collect MustGather data to find a solution.

Environment

These instructions apply to IBM MQ V9.0 and V8.0 on AIX, HP-UX, Linux, Solaris, Windows and IBM i, to WebSphere MQ V7.5 on AIX, HP-UX, Linux, Solaris and Windows, and to WebSphere MQ File Transfer Edition V7.0, V7.0.1, V7.0.2, V7.0.3 and V7.0.4 on AIX, HP-UX, Linux, Solaris, Windows and IBM i. Refer to the IBM MQ Read First page for instructions on other operating systems, including IBM 4690 or Toshiba 4690:

Resolving The Problem

Please answer these questions about the problem and then follow the steps below:

  • What managed file transfer problem did you observe on the system?
  • What time did the managed file transfer problem start and when did it stop?
  • What is your MQ file transfer topology, and where are the coordination queue managers?
  • Which managed file transfer agents, and managed file transfer loggers were involved in the problem?


Step 1: Generate Data


If the managed file transfer problem is reproducible or is happening right now, generate data to provide more information about the problem:




  1. If the problem involves TLS (formerly SSL) channel issues with a managed file transfer agent, enable JSSE tracing in the agent and carry on with the steps below.


  2. If a managed file transfer process is hanging, follow the instructions in Step 1.1 of the MQ hang and high CPU MustGather to generate three javacores from the process.


  3. Generate a trace of any failing MQ managed file transfer agent, logger, or other command and save the output of the failing command as well.


  4. If the problem involves interaction with a queue manager, generate a trace of the queue manager at the same time:




Step 2: Collect Data


  1. For file transfer agents agent problems, save the output of the fteShowAgentDetails command. Replace AGENTNAME with the actual name of the agent in this example:

    1. Display the agent details on Linux, UNIX, Windows and IBM i:


      fteShowAgentDetails -bl -v AGENTNAME



  2. Create an archive in the top-level MQ errors directory which contains any managed file transfer traces and javacores you generated in Step 1 as well as the logs, properties, and FFST files recorded by MQ managed file transfer. Both the runmqras automation tool and the manual collection steps below collect the files found in the top-level MQ errors directory. If you are running IBM MQ V9.0 or V8.0, or WebSphere MQ V7.5.0.3 or later you can archive the managed file transfer files automatically using fteRAS, which will print a message BFGCL0604I to identify the location of the zip file when it is done:

    1. V9.0, V8.0 and V7.5.0.3 and later fteRAS usage on Linux and UNIX


      Copy any interactive command traces and javacores to the /var/mqm/errors directory and then run fteRAS as shown:

      sh> fteRAS /var/mqm/errors
      ...
      BFGCL0604I: fteRAS command completed successfully. Output is stored in /var/mqm/errors/fteRAS.zip


      V9.0, V8.0 and V7.5.0.3 and later fteRAS usage on Windows


      Copy any interactive command traces and javacores to the top-level MQ errors directory. The example given below is the default errors directory for a new installation of IBM MQ V8.0 or later, but the location may be different on your system. For example, WebSphere MQ V7.5 and older releases commonly used C:\Program Files\IBM\WebSphere MQ\errors. Run fteRAS with the correct directory name for your system:

      C:\> fteRAS "C:\ProgramData\IBM\MQ\errors"
      ...
      BFGCL0604I: fteRAS command completed successfully. Output is stored in C:\ProgramData\IBM\MQ\errors\fteRAS.zip


      V8.0 and later fteRAS usage on IBM i


      Copy any interactive command traces and javacores you created (i.e. spool files from the GENJVMDMP command) to /QIBM/UserData/mqm/errors and then run the fteRAS command from the Qshell as shown:

      ===> /QIBM/ProdData/mqm/bin/fteRAS /QIBM/UserData/mqm/errors
      ...
      BFGCL0604I: fteRAS command completed successfully. Output is stored in /QIBM/UserData/mqm/errors/fteRAS.zip



    If you are running WebSphere MQ V7.5.0.2 or older, or if you wish to collect files manually, follow the instructions below and replace COORDQMNAME with the actual name of your coordination queue manager. Note that the path names may vary on Windows if you chose a different installation location:

      V9.0, V8.0 and V7.5 agent and logger javacores, traces, logs, properties and FFST files on Linux and UNIX


      Include any interactive command traces and javacores written to the current directory or to other directories as well as the contents of:

      /var/mqm/mqft/logs/COORDQMNAME/*
      /var/mqm/mqft/config/COORDQMNAME/*

      V9.0, V8.0 and V7.5 agent and logger javacores, traces, logs, properties and FFST files on Windows


      Include any interactive command traces and javacores written to the current directory or to other directories as well as the contents of the following directories (which may vary depending on your installation location):

      C:\Program Files\IBM\WebSphere MQ\mqft\logs\COORDQMNAME\*
      C:\Program Files\IBM\WebSphere MQ\mqft\config\COORDQMNAME\*

      V9.0 and V8.0 agent and logger JVM dumps, traces, logs, properties and FFST files on IBM i


      Include any interactive command traces and javacores you created (i.e. spool files from the GENJVMDMP command), as well as the contents of:

      /QIBM/UserData/mqm/mqft/logs/COORDQMNAME/*
      /QIBM/UserData/mqm/mqft/config/COORDQMNAME/*

      V7.0 agent and logger javacores, traces, logs, properties and FFST files on Linux and UNIX


      Include any interactive command traces and javacores written to the current directory or to other directories as well as the contents of:

      /var/IBM/WMQFTE/config/COORDQMNAME/*

      V7.0 agent and logger javacores, traces, logs, properties and FFST files on Windows


      Include any interactive command traces and javacores written to the current directory or to other directories as well as the contents of the following directories (which may vary depending on your installation location):

      C:\Documents and Settings\All Users\Application Data\IBM\WMQFTE\config\COORDQMNAME\*

      V7.0 agent and logger JVM dumps, traces, logs, properties and FFST files on IBM i


      Include any interactive command traces and javacores you created (i.e. spool files from the GENJVMDMP command), as well as the contents of:

      /QIBM/UserData/WMQFTE/V7/config/logs/COORDQMNAME/*



  3. Collect data from the coordination queue manager automatically with the runmqras command if you are running MQ V9.0, V8.0, V7.5, V7.1.0.1 and later, or V7.0.1.8 and later. Be sure to collect the runmqras defs and trace sections, and to specify your PMR number. If all of the file transfer data is in the top-level MQ errors directory, runmqras will include it:

    1. Collecting runmqras output from queue manager COORDQMNAME


      runmqras -section defs,trace -qmlist COORDQMNAME -pmrno 12345,67R,890



  4. Alternatively, collect the MQ data manually.

    Collecting MQ data manually


    1. If your system has more than one MQ installation, use the setmqenv command to choose the one with the problem before proceeding:

      Linux and UNIX


      sh> . /path/to/mqm/bin/setmqenv -n InstallationX

      Windows


      C:\> "C:\Program Files\IBM\MQ\bin\setmqenv" -n InstallationX


    2. Record the MQ version and maintenance level.


    3. Record the operating system version and maintenance level.


    4. Save the MQ configuration information, for example registry keys and ini files.


    5. If your system has more than one MQ installation, record your MQ installation details:

      Linux and UNIX


      sh> dspmqinst > /tmp/dspmqinst.txt

      Windows


      C:\> dspmqinst > %TEMP%/dspmqinst.txt


    6. On MQ V7.5 and later installations, use dmpmqcfg to record the queue manager configuration:

      Linux and UNIX


      sh> dmpmqcfg -m QMA > /tmp/QMA.config.txt

      Windows


      C:\> dmpmqcfg -m QMA > %TEMP%\QMA.config.txt

      IBM i Qshell


      ===> /QSYS.LIB/QMQM.LIB/DMPMQCFG.PGM -m QMA > /tmp/QMA.config.txt


    7. Otherwise, on WebSphere MQ File Transfer Edition V7.0 installations, use runmqsc to record the queue manager configuration. If any command gives an error, carry on with the others:

      DISPLAY QMGR ALL
      DISPLAY Q(*) ALL
      DISPLAY SUB(*) ALL
      DISPLAY TOPIC(*) ALL
      DISPLAY CHANNEL(*) ALL
      DISPLAY SERVICE(*) ALL
      DISPLAY PROCESS(*) ALL
      DISPLAY LISTENER(*) ALL
      DISPLAY NAMELIST(*) ALL


    8. On all MQ installations, use runmqsc to record status information from the queue manager. If any command gives an error, carry on with the others:

      DISPLAY PUBSUB ALL
      DISPLAY QMSTATUS ALL
      DISPLAY CHSTATUS(*) ALL
      DISPLAY LSSTATUS(*) ALL
      DISPLAY SVSTATUS(*) ALL
      DISPLAY SBSTATUS(*) ALL
      DISPLAY CONN(*) TYPE(*) ALL
      DISPLAY QSTATUS(*) TYPE(QUEUE) ALL
      DISPLAY QSTATUS(*) TYPE(HANDLE) ALL
      DISPLAY TPSTATUS('#') TYPE(PUB) ALL
      DISPLAY TPSTATUS('#') TYPE(SUB) ALL
      DISPLAY TPSTATUS('#') TYPE(TOPIC) ALL


    9. Manually package your files for IBM, including files containing the output from the commands listed in Step 1 and 2.


Step 3: Send Data to IBM


  1. Send your data to the /toibm/websphere directory on the IBM ECuRep repository by standard or secure HTTP or FTP, or by using the IBM Secure Diagnostic Data Upload Utility (SDDUU) Java application. Be sure to include the full PMR number in the file name so that it will be associated with your problem, e.g. 12345,69R,890.zip. Small files may be emailed to websphere_support@ecurep.ibm.com if you put the full PMR number in the subject of your note.


  2. While the data is transferring, send an email or use the IBM Service Request tool to update your PMR with your description of the problem and of the data you are sending.



  3. Contact your country representative if you need to speak to an IBM technical support representative, or in the US call 1-800-IBM-SERV. Refer to the IBM Software Support Handbook for more information on working with IBM.


[{"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Problem Determination","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.0;7.5;7.0.4;7.0.3;7.0.2;7.0.1;7.0","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

IBMMQ WebSphere MQ File Transfer Edition WMQFTE WMQ FTE

Document Information

Modified date:
22 June 2018

UID

swg21599033