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.
To set the ras_log_logstreamName environment variable, on the administrative console, click Environment > WebSphere Variables, select a scope, and then click New.
To set these environment variables, on the administrative console, click Environment > WebSphere Variables, select a scope, and then click New.
In the administrative console, click Environment > WebSphere Variables, select the appropriate node or cell from the pull-down list of available nodes, and then click New:
You can set these variables for individual control and servant processes, but it is easier to set them in the Environment variables for the entire cell. For the Daemon, you must prefix them with "DAEMON_" and set them at the cell level:
//* Output DDs //CEEDUMP DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //SYSOUT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //SYSPRINT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //DEFALTDD DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //HRDCPYDD DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE