PQ52525: WEBSPHERE V4.0 FOR OS/390 ISSUES TOO MANY WRITE TO OPERATOR (WTO) MESSAGES TO THE CONSOLE / SYSLOG.

APAR status
Closed as fixed if next.

Error description
WebSphere Application Server Version 4.0 for z/OS and OS/390
issues too many Write to Operator (WTO) messages to the
console / SYSLOG.  Besides having the WTOs going to the
console / SYSLOG, they also show up in the job log JESMSGLG
and JESYSMSG datasets.  Therefore, there are three copies of
the same WTO.
..
A WTO indicating the server is starting and another WTO
indicating either the server has completed initialization or
the server failed to initialize should be sufficient.
For example:
..
 BBOU0007I CB SERIES DAEMON DAEMON01 IS STARTING.
 BBOU0016I INITIALIZATION COMPLETE FOR DAEMON DAEMON01.

All other current WTOs should be written to a specific DD
statement specified in the server's start-up JCL.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of the WebSphere Application       *
*                 Server Version 4.0 for z/OS and OS/390.      *
****************************************************************
* PROBLEM DESCRIPTION: Too many of the trace messages issued   *
*                      by the V4.0 WebSphere Application       *
*                      Server are written to the operator's    *
*                      console/SYSLOG.  The trace messages and *
*                      other messages are also written to the  *
*                      job's JESMSGLG and/or JESYSMSG          *
*                      datasets.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Too many messages are written to the operator's console/SYSLOG
by the V4.0 WebSphere Application Server for z/OS and OS/390.
This is because many of the trace messages are written using
the Tr.audit() method, which always writes to the log even when
tracing has not been turned on.  These messages are also written
to the job's JESMSGLG dataset.

In addition, many other messages are written to the job's
JESMSGLG and/or JESYSMSG datasets as well as to the
console/SYSLOG.  Some of these messages are not needed in
either place and should be written only when tracing is
activated or written to a specific DD statement specified in
the server's start-up JCL.
Problem conclusion Temporary fix Comments
The first problem has been fixed in V4.0.1 of the Application
Server.  All the Tr.audit() method invocations have been changed
in that release of the product to invocations of another trace
method which does not write to any log when tracing is not
activated.

The second problem is being addressed via V4.0.1 APAR 
PQ57645.
This APAR (PQ52525) is being closed with the FIN closing code
for V4.0.
APAR information
APAR number PQ52525
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Submitted date 2001-09-18
Closed date 2002-02-08
Last modified date 2002-08-13

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
NA NONE        

Fix information
Fixed component name WEBSPHERE OS/39
Fixed component ID 5655A9800

Applicable component levels
R400 PSN    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ52525
IBM Group: Software Group
Modified date: Aug 13, 2002