WMB/IIB MustGather: problems with Command Console Commands or Trace on Windows

See: mqsidc usage instructions

• Always gather broker-specific data when possible using the Broker Collector
• If a broker or execution group is not used, gather generic data using the General Collector

• Utility trace (for failing mqsi commands)
• A service level trace is intended to be provided to IBM Support to assist in the diagnosis of your issue

• Record the IBM Integration Bus or 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 Windows systems, the local error log is the Windows Event viewer logs.
• Collect the Standard Output/Error logs.
  WMB writes information to a console.txt file, 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 log (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