Error messages and return codes are recorded in several places. Look for the following:
WebSphere Business Integration Message Broker error messages have the prefix BIP. If you receive any messages with this prefix (for example, in the UNIX or z/OS syslog), see Diagnostic messages for an explanation.
In the Windows Event log, references to BIP messages are identified by the value BIPV500 in the Source field; add the prefix BIP to the Event number to get the full message identifier.
WebSphere Business Integration Message Broker messages having a mixture of identifiers such as BIPV500, WMQIv210, MQSIv202, and MQSIv201 indicate a mixed install, which does not work properly.
For messages with a different prefix, such as AMQ or CSQ for WebSphere MQ, or SQL for DB2, see the appropriate messages and codes documentation for a suggested course of action to help you resolve the problem.
Messages associated with the startup of WebSphere Business Integration Message Broker, or issued while the system was running before the error occurred, might indicate a system problem that prevented your application from running successfully.
A large or complex WebSphere Business Integration Message Broker broker domain might require some additional configuration of the environment beyond what is recommended in Installing. The need for such configuration changes are typically indicated by warning or error messages logged by the various components, including WebSphere MQ, the databases, and the operating system. These messages are normally accompanied by a suggested User Response.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
au13550_ |