PQ91944: <ERRORSTREAMREDIRECT> AND <OUTPUTSTREADMREDIRECT> TAGS CAUSE STDOUT AND STDERR GARBAGE IN HFS FILES

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
WebSphere Application Server for z/OS v5.0 at PTF level
W500102 (GA level code) allowed for, in the ISPF customization
dialogs, the option to redirect stdout and stderr to HFS files.
This is not supported on z/OS and was corrected at the
W500103 level. However, customers that ran the ISPF dialogs
before this PTF level were not given a method to remedy this
redirected output. The tags that appear in the incorrect version
of server.xml are:
<errorStreamRedirect xmi:id="StreamRedirect_1" fileName="${SERVE
R_LOG_ROOT}/SystemErr.log" .....
<outputStreamRedirect xmi:id="StreamRedirect_2" fileName="${SERV
ER_LOG_ROOT}/SystemOut.log" .....
The presence of these tags can cause output to appear
garbled or scrambled in the logs. One example of this is: If an
application is deployed, and the pre-compile jsp option is
selected, and one or more of the jsps fail to compile during
this process. The Systemxxx.log will display garbled text,
instead of the failing jsp's error information.
Local fix
remove these two tags from server.xml and restart the server.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: JSP pre-compile error messages do not   *
*                      appear in the Deployment Manager        *
*                      servant log.                            *
*                      An example of the missing message is    *
*                      Compiling jsps in caremgmt.war          *
*                      Invoking compilation ..                 *
*                      JSPG0044E: Error while generating code  *
*                      for /x.jsp : org.apache.jasper.         *
*                      compiler.ParseException:                *
*                      /x.jsp(2,64) Attribute y                *
*                      has no value.                           *
*                      Errors compiling jsps in                *
*                      /tmp/app_fdb55bb7b8/ear/abc.war         *
*                      Return code from jsp-compilation is: 1  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem was that System.out/System.err messages were being
redirected to a file on the HFS, rather than appearing in the
server log.
The server.xml files may contain the
following entries that are not supported in WebSphere
Application Server on z/OS.
These entries may appear in configurations that were
customized at the WebSphere Application Server 5.0 GA level
code.
Websphere Application Server on z/OS does not support
stream redirection via the following setting since
multiple servant regions could write simultaneously to the
same file overwriting previous entries.

<errorStreamRedirect xmi:id="StreamRedirect_1091562124851"
fileName="$(LOG_ROOT)/$(SERVER)/SystemErr.log"
rolloverType="SIZE" maxNumberOfBackupFiles="1" rolloverSize="1"
baseHour="24" rolloverPeriod="24" formatWrites="true"
messageFormatKind="BASIC" suppressWrites="false"
suppressStackTrace="false"/>
<outputStreamRedirect xmi:id="StreamRedirect_1091562124852"
fileName="$(LOG_ROOT)/$(SERVER)/SystemOut.log"
rolloverType="SIZE" maxNumberOfBackupFiles="1" rolloverSize="1"
baseHour="24" rolloverPeriod="24" formatWrites="true"
messageFormatKind="BASIC" suppressWrites="false"
suppressStackTrace="false"/>
Problem conclusion
This APAR will remove the errorStreamRedirect and
outputStreamRedirect stanzas from the server.xml files
if they exist.
The JSP pre-compile and other System.out/System.err messages
should now go to the JOBLOG by default.

APAR PQ91944 is associated with SERVICE LEVEL W502015 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ91944
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-07-26
Closed date 2004-09-03
Last modified date 2004-10-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PQ93428

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ92596    UP04/09/13 P F409

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ91944.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ91944
IBM Group: Software Group
Modified date: Oct 5, 2004