IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Additional checks for z/OS users

Problem determination for z/OS® users.

On IBM® Integration Bus for z/OS, you might find that:

The console has unexpected messages; look for an explanation by searching for the message number in the information center, or referring to 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 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.

The queue manager address space
A queue manager in your queue-sharing group
The channel initiator address space
Batch or TSO address space
The z/OS system (including ARM, RRS, or the Coupling Facility)
The network (including APPC or TCP/IP)
Another system, for example a queue manager on another operating system or a WebSphere MQ client
The external security manager product, for example RACF® or ACF2
DB2

Understanding interactions between the runtime components

There are two runtime components: the broker and the integration server. 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 IBM Integration Bus 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 integration server.

When the broker receives command requests 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 integration server, and a corresponding message being issued. Every response from an integration server that results from these command requests 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 integration server receives command requests from the broker, the integration server 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 integration server issues a message that indicates that the message has been processed.

Loading IBM and user-defined nodes and parsers

When an integration server 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.

au13640_.htm |

Last updated Friday, 21 July 2017