IBM Support

WMB/IIB Mustgather: problems with User Interfaces: Commands and Traces on UNIX and Linux

Troubleshooting


Problem

You are experiencing a problem with User Interfaces: Commands and Traces with WebSphere Message Broker (WMB) or IBM Integration Bus (IIB). This mustgather document explains how to troubleshoot this problem by yourself, how to generate diagnostic data when the problem is happening, how to collect the available data from your system, and how to share that data with IBM support.

Environment

These instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, and Solaris systems.
Return to the WebSphere Message Broker MustGather index for other systems.

Resolving The Problem


Step 1: Self-guided Troubleshooting


  1. Consider Troubleshooting
  2. Dealing with problems

  3. Check for known issues:
    WebSphere Message Broker support site


Step 2: Collect Data


  1. mqsidc

    See: mqsidc usage instructions

    • This command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, and IIB 9.0.
    • When running the tool, select the option for 'Broker Collector', when prompted.

  2. Traces

  3. General Broker information
    If the mqsidc tool was not run, then capture this information manually
    • Record the WebSphere Message Broker version, release, and maintenance level.
      This can be captured using the command 'mqsiservice -v'.
    • Record the operating system version, release, and maintenance level.
    • Record the version, release, and maintenance level of any related products and components for the problematic application.
    • Collect the local error log. On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.
      See: Configuring the syslog daemon
    • Collect the Standard Output/Error logs.
      WMB writes information to both STDOUT and STDERR. These files are located under the Message Broker workpath.
      See: Standard System Logs
    • Exact command that caused the problem

    • With your mqsi serviceID, collect the output of the command 'env'
    • Abend file(s) (if generated)
      Some runtime failures cause an abend. The syslog (see above) will record the time and location of any *.abend files created, as a result. You can also manually check for abend files in the directory: {MQSI_WORKPATH}/common/errors
      See: Abend files


  • ATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!
    When sending data to IBM, be sure to update your PMR or send a note with the following information:

    • Tell us what errors you saw, where you saw them, and what time they happened
    • Let us know if you made any changes to WebSphere Message Broker or the system before the problem
    • Share any other observations which you think will help us to better understand the problem

Step 3: Submit Data to IBM






Please see the IBM Software Support Handbook for more information on working with IBM support.

Back to top

[{"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Usage","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"8.0;7.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}},{"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI

Document Information

Modified date:
23 March 2020

UID

swg21299820

Page Feedback