PM47306: HPEL LOG VIEWING FUNCTION NEEDS TO HAVE THE ABILITY TO PASS IN SPECIFIC CODEPAGE INFORMATION CORRECT VIEWING OF DATA

8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• When using the HPEL Log viewing facility, if the messages were
  written using a specific codepage, the Log Viewer needs to be
  able to use the same codepage, to display the data correctly.
  

Local fix

• modify the export script, to add -Dfile.encoding=xxx
  there xxx is the codepage the messages were written in.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0 using HPEL logging mode.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: logViewer utility does not provide      *
  *                      option to convert log records into      *
  *                      text using other than default           *
  *                      encoding.                               *
  ****************************************************************
  * RECOMMENDATION:  As a work around users can update           *
  *                  logViewer utility and add                   *
  *                  '-Dfile.encoding=<encoding>' option to the  *
  *                  java call to enforce using other than       *
  *                  default encoding.                           *
  ****************************************************************
  Strings used in log records can be targetted for different
  encoding than what is setup as a default encoding on a machine
  where logViewer utility is used. Characters specific to the
  targetted encoding will be either substituted by different
  characters or cause truncation of the output.
  

Problem conclusion

• Fix introduces '-encoding' option to the class used by the
  logViewer utility to specify encoding to use when log records
  are converted into text. If logViewer utility was updated with
  the work around it needs to be restored to its original state
  to avoid interference between the new option and the value
  specified with 'file.encoding' system property.
  
  APAR PM47306 is currently targeted for inclusion in
  Service Level (Fix Pack) 8.0.0.3 of WebSphere Application
  Server V8.0.
  
  Please refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  In addition, please refer to URL:
  http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack PTF information.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R800 PSY

     UP