IV48098: FILEOUTPUTSTREAM WITH DBCS CHARACTERS THROWS UNEXPECTED ERROR AF TER DATABASE CONNECTION ON WINDOWS PLATFORM

APAR status

• Closed as program error.

Error description

• Error Message: Error dialog with the message "Java(TM) Platform
  SE binary has stopped working" appears on the screen.
  .
  Stack Trace: N/A
  .
  The issue is observed with DBCS locale like Japanese
  

Local fix

• The problem can be work around by one of the following options:
  1. Modify the number of DBCS characters (either increase or
  decrease by one) in the file name.
  2. Create the  new File before the database Connection.
  

Problem summary

• The JDK provided incorrect buffer length  to the Windows system
  API wcstoms_s with certain number of DBCS characters.
  

Problem conclusion

• This defect will be fixed in:
     7    SR7       (7.0.7.0)
     7 R1 SR1       (7.1.1.0)
  .
  The JDK has been updated to provide the correct buffer length to
   the wcstombs_s API. There is a limitation with  wcstombs_s API
  that it can handle only 512 bytes. This limitation is
  addressed in APAR IV60518 by using the API WideCharToMultiByte
  instead of wcstombs_s.
  

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

  JAVA CLASS LIBS

• Fixed component ID

  620700130

Applicable component levels

• R700 PSY

     UP