Use the product message routing capabilities to control
server traffic flow.
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 environment
variables, ras_default_msg_dd and ras_hardcopy_msg_dd, and the specification
of the appropriate DD statement in your JCL start procedure.
The
following explains, in more detail, how messages get routed.
- WTO messages issued during initialization are sent to hardcopy,
but most can be routed to the data set specified by ras_default_msg_dd
(see Log 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 Log 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, click Environment
> WebSphere Variables, select a scope, and then click New.
- Early error messages will go to STDERR (SYSOUT) until the 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.
-
If you are using JES2, the SEBMENT= parameter can
be added to the SYSPRINT and SYSOUT DD cards if you want to segment
output using the periodic writing of form-feed characters to the output
streams. Form-feed characters are written to the output streams based
on the values of the ras_stderr_ff_interval, ras_stdout_ff_interval, ras_stderr_ff_line_interval,
and ras_stdout_ff_line_interval environment variables.
These variables are described in more detail in the topic Application
server custom properties for z/OS The SEBMENT= parameter is
not supported on JES3..To set these environment variables, on the
administrative console, click , select a scope, and
then click New.
![[sep2010]](../../deltaend.gif)
sep2010
- The interval of time between the writing of a form-feed character
to standard error, or SYSOUT is determined by the value specified
for the ras_stderr_ff_interval variable. The interval of time between
the writing of a form-feed character to standard output, or SYSPRINT
is determined by the value specified for the ras_stdout_ff_interval
variable.
To set these environment variables, on the administrative
console, click Environment > WebSphere Variables, select a
scope, and then click New.
- 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.