On Windows,
the local
error log is the Windows Event log (Application view).
On UNIX and Linux systems, the local
error log is the syslog.
Where syslog messages are sent depends on how you configure your UNIX or Linux system.
On z/OS®, the local
error log is the operator console.
- On Windows:
by events from the source IBM Integration v**** and a message number
in the form nnnn, where **** is
the current four-digit product version number.
- On UNIX:
by a message number in the form BIPnnnn.
- On z/OS: by
a started task ID, and a message number in the form BIPnnnn.
When a broker encounters an error, more than one message can be written to the local error log. Typically these messages start with a general message (for example, Could not process a message), and further messages give more details about the cause of the error (for example, An error was detected while processing the following SQL statement).
On Windows,
the event log can fill up; ensure that you have a log size that is
sufficient, or that you have enabled circular logging.
Last updated Friday, 21 July 2017