WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

z/OS: Viewing broker job logs

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.

Understanding the broker address spaces

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 WebSphere® Message Broker Toolkit.

Each execution group within the broker is mapped to its own address space, and as these execution groups 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 execution groups have a JOBNAME that is also the same as the broker name, and a STEPNAME that matches the last seven characters of the execution group name.

Viewing the z/OS system console log

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.

Viewing the broker job logs

The broker control address space, and each of the execution group 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.

Interpreting log information

In both logs, each message is displayed on its own, in date and time order; it might span multiple lines, if necessary. For each message, the following information is available:
  • Date and time: The exact date and time when the event was written to the log.
  • JOBID: The started task job identifier of the address space.
  • Message Number: The message number that identifies whether the event is information, a warning, or an error, with diagnostic text.
  • JOBNAME: The JOBNAME of the address space issuing the message. This name is always the same as the broker name.
  • STEPNAME: The STEPNAME of the address space that is issuing the message. For the control address space, this name is the same as the broker name; for execution groups, it is the same as the last eight characters of the execution group that is issuing the message.
  • PROCSTEP: The procedure STEPNAME, which equals BROKER for the main broker control address space. For execution group address spaces, this is either EGNOENV, if there is not an execution group specific profile, or EGENV if there is an execution group specific profile.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:19


Task topicTask topic | Version 8.0.0.7 | an20101