WebSphere Message Brokers
File: au13640_
Writer: Jane Brockbank

Task topic

This build: July 31, 2007 21:39:11

Additional checks for z/OS users

On WebSphere Message Broker for z/OS, you might find that:
  • The console has unexpected messages; look for an explanation in Diagnostic messages or other relevant messages and codes documentation.
  • RRS is not started; issue the command D A,RRS.
  • The queue manager is not available; issue the WebSphere MQ command DISPLAY THREAD(*).
  • DB2 is not working; issue the DB2 command DISPLAY THREAD.
  • The User Name Server is not working.

The cause of your problem on z/OS could be in any of the following areas. Check each of these, starting with whichever seems the most likely, based on the nature of your problem.

Understanding interactions between the runtime components

There are three runtime components: the broker, the Configuration Manager and the execution group. These components communicate with each other by exchanging command requests inside WebSphere MQ messages to perform actions, such as deploying a message flow. After completion of the command request, responses are sent back to the originating component, indicating whether the request was successful.

On WebSphere Message Broker for z/OS, you see extra information messages issued by z/OS runtime components that allow you and IBM Service personnel to determine the interactions between the various runtime components, including the Configuration Manager, broker and execution group.

When the broker receives command requests from the Configuration Manager, the broker issues a message that identifies the command request. When this request completes, a message is issued that indicates whether the command is successful. Each command request that the broker receives results in at least one matching command request being sent to an execution group, and a corresponding message being issued. Every response from an execution group that results from these command requests will result in a message being issued. These messages can be turned on and off and are to be used by the IBM Service team.

When an execution group receives command requests from the broker, the execution group issues information messages that identify the command request. For actions that are contained within a command request, an information message is issued that identifies the action to be performed and the resource upon which the action is to take effect. When the request completes, the execution group issues a message that indicates that the message has been processed.

When a Configuration Manager receives a command request and when this request completes, information messages are issued.

Loading IBM and user-defined nodes and parsers

When an execution group starts, it loads all available IBM and user-defined nodes and parsers. For each library that is loaded, two messages are issued. One is issued before the library is loaded and one is issued after the library has been loaded.

Related tasks
Troubleshooting and support
Making initial checks
Using WebSphere MQ shared queues for input and output (z/OS)
Related reference
Other sources of diagnostic information on z/OS
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:39:11

au13640_ This topic's URL is: