WebSphere Application Server for z/OS provides improved message
routing capabilities. You can route many of the BBO prefixed error messages
to specific datasets instead of having them go to SYSLOG, which can create
a lot of traffic. This is implemented with the use of two new environment
variables, ras_default_msg_dd and ras_hardcopy_msg_dd, and then specifying
the appropriate DD statement in your JCL start procedure.
The two new
environment variables are documented in Appendix A of the WebSphere
Diagnosis book. The following explains how messages get routed in WebSphere
Application Server Version 5 in more detail:
- WTO messages issued by WebSphere Application Server during initialization
are sent to hardcopy, but most can be routed to the data set specified by
ras_default_msg_dd (see Setting output destinations and characteristics).
- The Java "Audit" messages are also sent to hardcopy, but can be routed
to the data set specified by ras_hardcopy_msg_dd. (see Setting output destinations and characteristics).
- Trace error, service, and fatal messages are sent to the error log specified
by the ras_log_logstreamName. Otherwise, they go to CERR (SYSOUT). Some may
also go to hardcopy. At the W500104 service level, the ras_log_logstreamName
environment variable is not set to the error logstream name in the was.env
variables. To set the ras_log_logstreamName environment variable, on the administrative
console select Environment -> Manage WebSphere Variables -> New.
- Early error messages will go to STDERR (SYSOUT) until WebSphere Application
Server connects to the log stream. A WTO (BBOO0153I) is issued telling you
how many messages went to STDERR before you connected to the log stream.
- Trace messages (such as BUFFER, SYSPRINT, and TRCFILE DD) are also routed
to ras_trace_outputLocation.
- System.out.println, System.err.println, Tr.Sysout, stdout
(cout), and client output go to SYSPRINT.(see Viewing SYSPRINT output, STDOUT and STDERR streams in an HFS File
- Tr.Syserr, and STDERR (CERR) go to SYSOUT.