On z/OS®, the broker writes messages to the appropriate z/OS system log and job logs. These messages might include information, warning, error, and severe messages to indicate various situations and events.
The broker runs in multiple address spaces. A single control address space is always running when the broker is active, and is responsible for communicating with the IBM® Integration Toolkit.
Each integration server within the broker is mapped to its own address space, and as these integration servers start and stop, the corresponding address spaces are started and stopped. The control address space is assigned a JOBNAME and STEPNAME, which is the same as the broker name. The integration servers have a JOBNAME that is also the same as the broker name, and a STEPNAME that matches the last seven characters of the integration server name.
The broker writes all its messages to the z/OS system console log. You can see messages from all address spaces running on the z/OS system in this log. It is easy to identify jobs that are associated with the broker in the console log, because of the naming of broker address spaces. By using the console log, you can see the order of event reporting for different products. This information can be helpful for cross-product problem determination.
The broker control address space, and each of the integration server address spaces, has its own job log. When you select the job log for the appropriate address space, you can see all messages relating to that address space. Use this option in a busy system where the system console log might have many messages from different products obscuring the information in which you are interested.