Troubleshooting
Problem
You are experiencing a database problem with WebSphere Message Broker (WMB) or IBM Integration Bus (IIB) on z/OS. 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 z/OS system, and how to share that data with IBM support.
Environment
These instructions are for WebSphere Message Broker or IBM Integration Bus on z/OS systems.
Return to the WMB/IIB MustGather index for other systems.
Resolving The Problem
- Consider Using the Test Client in trace and debug mode.
- A user level trace is intended to assist users with understanding how their ESQL is processed.
It will also show a high level view of the message flow behavior. - Check for known issues:
WebSphere Message Broker support siteResolving problems when using databases
IBM and WMB FAQs
WebSphere Message Broker and JDBC
Dynamic guide to help with troubleshooting Message Broker
- Complete broker joblog
- Joblogs are vital in that they provide component messages, environment details, product level data and other useful information. Send in the joblog for the broker component experiencing the issue.
- Project Interchange files for the problematic flow/set/ESQL/model
- You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.
See: Importing resources from previous versions
- You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.
- Traces
If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces can be used to gain a better understanding of the problem.- A user level trace is intended to assist users with understanding how their ESQL is processed. It will also show a high level view of the message flow behavior.
- A service level trace is intended to be provided to IBM Support to assist in the diagnosis of your issue.
- Abend file(s) (if generated)
Some runtime failures cause an abend. The joblog (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 - ODBC Trace
If the failure can be recreated, safely, an ODBC trace will capture the internal processing of a failing SQL prepared statement.
See: ODBC Trace
- Related Broker information
The following items will be helpful in understanding your specific setup.
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:
- Use IBM Service Request to open or view a problem record with IBM.
- Send your data to IBM for further analysis.
Please see the IBM Software Support Handbook for more information on working with IBM support.
Product Synonym
WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI
Was this topic helpful?
Document Information
Modified date:
23 March 2020
UID
swg21302929