SE59318: RDP 8.0.3 SI/SO CHARACTERS NOT PRESERVED WHEN SOURCE MEMBER IN IPROJECT PUSHED TO HOST

Rational Developer for i 9.1.1

APAR status

• Closed as program error.

Error description

• This is observed with RDP 8.0.3, RDI 9.0 and RDI 9.1
  
  Source members that contain SI/SO in an iProject used with RTC
  have the SI/SO characters replaced with blanks when pushed back
  to the IBM i.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * RPG programmers with DBCS source who have adjacent DBCS      *
  * strings with no SBCS characters separating them.  Note that  *
  * this would only be valid in the compile time data area at    *
  * the bottom of the source or in comments.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Adjacent DBCS bracketing characters prevent editing with     *
  * RDi.                                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  EBCDIC DBCS characters are bracketed shift out (SO) and shift in
  (SI).  When downloading to Unicode, these shift characters are
  not represented and so these characters would be lost.
  In previous releases both SO/SI  (adjacent DBCS strings) and
  SI/SO (empty DBCS strings) were detected and a message was shown
  to the user asking if they wanted to replace these characters
  with 2 SBCS blanks.  For adjacent strings this would have the
  effect of merging the two DBCS strings with a DBCS space in
  between, so the length is preserved.  For the compile time data
  area case this is problematic because RPG variables would not be
  initialized correctly.
  

Problem conclusion

• In order to preserve the fact that DBCS strings are separate
  but adjacent a Unicode character (Zero-width, non-joiner \u200c)
  is inserted when downloading.  On upload the special character
  is stripped and the adjacent DBCS strings have separate
  bracketing characters.  Note that if the RTC EE product is used
  to load and build on the IBM i, it also needs to handle this.
  See associated PTFs.
  co-req
  APAR# PI28694
  

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:

Modules/Macros

• Save
  

Fix information

• Fixed component name

  RPG/COBOL DEV T

• Fixed component ID

  5724Y9901

Applicable component levels

• R803 PSY

     UP

• R850 PSY

     UP

• R851 PSY

     UP