Re: iSphere 3.2.5.b001 - Bugfix Ccsid Issue in Compare Editor

Hi Folks,

I am very sorry, but today a colleague found a CCSID issue in the
iSphere Compare Editor. The bug had already been reported and
(partially) fixed on December 17th, 2017.

But today I again stumbled about it. Murphy is ...

I am pretty sure that I fixed it thoroughly, now, provided that
QSYSEditableRemoteSourceFileMember.download() stores the file on the PC
with UTF-8 encoding. That is my assumption for now.

CAN SOMEBODY CONFIRM THAT MY ASSUMPTION IS TRUE?

My test data was:

**free

// Original and unmodified data.
dcl-c up
'ABCDEFGHIJKLMNOPQRSTUVWXYZ-

ÄÖÜÂÀÁÃÅÇÑÉÊËÈÍÎÏÌÔÒÓÕÛÙÚÝÞ';
dcl-c lo
'abcdefghijklmnopqrstuvwxyz-

äöüâàáãåçñéêëèíîïìôòóõûùúýþ';


It was great if some of you could install and re-test 3.2.5.b001. Feel
free to start with my test data but please be creative and add your own
special characters.

Here is what I did:

1) Created member CCSID_1 with the data from above.
2) Created member CCSID_2 with the same data.
3) Modified the headline of CCSID_1 a bit to get a difference.
4) Started the iSphere Compare Editor for both members and made a
pseudo-change, e.g. I changed a space or dot to the same value just to
enable the SAVE button.
5) Saved the changed member.
6) Closed the compare editor.
7) Started the compare editor for both members again and got a few
changes in the lines with the special characters.

From my point of view this is a critical bug that should be fixed asap.

So please help testing and let me know the result.

Thanks,

Thomas.