PQ70978: ACTIVITY LOG CANNOT BE READ ON SPANISH - ES INSTALL

 Fixes are available

5.0.1: WebSphere Application Server Version 5.0 Fix Pack 1 (Version 5.0.1)
5.0.1: WebSphere Application Server Enterprise Edition Version 5.0 Fix Pack 1



APAR status
Closed as program error.

Error description
Activity log cannot be read on Spanish - ES install.
Attempts to open the log result in a blank - empty
loganalyzer screen.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All non-English WebSphere Application Server *
*                 users of the JFace Log Analyzer.             *
****************************************************************
* PROBLEM DESCRIPTION: Binary activity log files are not       *
*                      parsed correctly when opened by the     *
*                      JFace Log Analyzer on non-English       *
*                      locales.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When non-English binary activity log files are opened by the
JFace Log Analyzer on non-English locales, they are not parsed
correctly.  The JFace Log Analyzer displays an empty UI when
non-English binary activity log files are opened by the JFace
Log Analyzer on non-English locales.  Non-English textual
activity log files can be parsed correctly but binary files
can not.  The problem is the InputStreamReader on the showlog
process is reading the input stream using the default encoding
and not the encoding set in the textual activity log file.
For example,

$LANG = es_ES
$CODESET = Cp1252

Steps to Reproduce:

1) Change the default locale for your operating system to es_ES.
2) Open a binary activity log file.
3) Note that the binary activity log file is not parsed
   correctly.
4) Open a textual activity log file.
5) Note that the textual activity log file is parsed correctly.
Problem conclusion
The solution is to pipe the output from showlog to a temporary
textual file and parse the temporary textual file.  This will
allow the Log Analyzer to read the encoding used by showlog
and adjust its readers accordingly.
Temporary fix Comments
APAR information
APAR number PQ70978
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-02-13
Closed date 2003-02-13
Last modified date 2003-02-13

APAR is sysrouted FROM one or more of the following:
PQ68550

APAR is sysrouted TO one or more of the following:

Modules/Macros
ANALYZER          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ70978
IBM Group: Software Group
Modified date: Feb 13, 2003