PI31273: OSGICFGINIT.SH -ALL MAY OUTPUT UNREADABLE MESSAGES

8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Using z/OS WebSphere Application server, when a user issues
  osgiCfgInit.sh -all and doesn't have the correct permissions on
  a folder, the OSGI error log messages are written to the screen
  in ASCII instead of EBCDIC - making the text unreadable.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: The osgiCfgInit script can produce      *
  *                      unreadable output when executed with    *
  *                      insufficient user rights                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an error occurs within the OSGi framework packaged within
  WAS, it will attempt to write the error to a log file within
  the OSGi configuration area.  If the file cannot be created
  (usually due to a lack of write permission), then the error
  will be printed to the console.  Prior to this APAR, the
  framework explicitly set the character encoding to UTF-8, which
  was appropriate for a log file but was unreadable when
  displayed to the z/OS console, which uses EBCDIC encoding.
  

Problem conclusion

• Explicit usage of UTF-8 was removed in favor of the default
  encoding when writing to the console.
  
  APAR PI31273 is currently targeted for inclusion in Fix Pack
  8.5.5.7 of WebSphere Application Server.
  
  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

• R850 PSY

     UP