You can find details of error messages and return codes in several places.
WebSphere® Event Broker error messages have the prefix BIP. If you receive any messages with this prefix (for example, in the UNIX®, Linux®, or z/OS® syslog), see Diagnostic messages for an explanation.
In the Windows® Event
log, references to BIP messages are identified by the source name "WebSphere Broker
v6000", where v6000 can be replaced by a number representing the exact service
level of your installation, for example 6001.
WebSphere Event Broker messages that have a mixture of identifiers such as BIPv600, BIPv500, WMQIv210, MQSIv202, and MQSIv201 indicate a mixed installation, 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 resolve the problem.
Messages that are associated with the startup of WebSphere Event Broker, or were 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 Event Broker broker domain might require some additional configuration of the environment beyond what is recommended in Installing complementary products. The need for such configuration changes is typically indicated by warning or error messages that are logged by the various components, including WebSphere MQ, the databases, and the operating system. These messages are normally accompanied by a suggested user response.