IBM Support

WMB/IIB MustGather: Problems with a Database on z/OS

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


Step 1: Self-guided Troubleshooting


  1. Consider Using the Test Client in trace and debug mode.

  2. 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.

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

    Resolving problems when using databases


    IBM and WMB FAQs
    WebSphere Message Broker and JDBC
    Dynamic guide to help with troubleshooting Message Broker


Step 2: Collect Data


  1. Complete broker joblog

    See: Viewing broker joblogs

    • 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.

  2. Project Interchange files for the problematic flow/set/ESQL/model

  3. 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

  4. Related Broker information

    The following items will be helpful in understanding your specific setup.



  • 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.



[{"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Database","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"10.0;9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI

Document Information

Modified date:
23 March 2020

UID

swg21302929