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 by the Application Server 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 might 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 this environment variable, on the administrative console,
click , select a scope, and click New.
- Early error messages go to SYSOUT until the product connects to
the log stream. A WTO (BBOO0153I) is issued telling you how many messages
went to SYSOUT before you connected to the log stream.
- If you are using JES2, the SEGMENT= 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 SEGMENT=
parameter is not supported on JES3..
To set these environment variables,
on the administrative console, click , select a scope, and
then click New.
- Trace messages are routed to ras_trace_outputLocation.
- System.out.println, System.err.println,
STDOUT and cout go to SYSPRINT (see the topic Redirectiong SYSPRINT
and SYSOUT output to an HFS File for more information.
- STDERR and cerr go to SYSOUT