Debugging problems related to Java Message Service (JMS) support
You might encounter JMS-related errors in the WebSphere Application Server
for z/OS environment. To debug these errors, use any of the various WebSphere
console settings that controls the type of trace data collected.
- com.ibm.ejs.*=all=enabled
- Turns on all container tracing
- com.ibm.ejs.j2c.*=all=enabled
- Turns on all tracing for connector support in WebSphere Application Server
for z/OS
- Messaging=all=enabled
- Collects trace data for the JMS and Message-driven bean (MDB) components
of WebSphere Application Server for z/OS
If your installation configures WebSphere MQ to provide Java Message Service
(JMS) support, you might need to use specific MQ tools for diagnosis:
- WebSphere variable JMSApi=all=enabled, which turns
on all tracing for applications that use the JMS application programming interface
(API).
- MQSC commands, which allow you to display information and perform other
operations.
- The CSQUTIL utility program, which helps you to perform backup, restoration,
and reorganization tasks, and to issue WebSphere MQ commands.
For more information about these diagnostic tools, refer to WebSphere MQ
books, which are available through the Web site:
http://www.ibm.com/software/ts/mqseries/library/
The most useful for diagnostic information are:
- WebSphere MQ for z/OS Problem Determination, GC34-6054
- WebSphere MQ for z/OS Messages and Codes, SC34-6056
- WebSphere MQ Script (MQSC) Command Reference, SC34-6055
- WebSphere MQ for z/OS System Administration Guide, SC34-6053
All of these publications can be accessed from the IBM Publications Center.

Steps for configuring WebSphere variables
Searchable topic ID:
rtrb_debugjms
Last updated: Jun 21, 2007 9:56:50 PM CDT
WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/rtrb_debugjms.html