Re: Hex codes in position 5 are being mangled

Sorry - should have mentioned that I'm on WDSc v6.0.1.1, with all PTFs 
applied.

Adam




AGlauser@xxxxxxxxxxxx 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
24/05/2006 09:08 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] Hex codes in position 5 are being mangled






Hi all,

I've searched the archives a bit but to no avail.  I seem to be having a 
problem with a character x'22' in position 5, when pushing changes from an 

iSeries Project.  The source file on the iSeries is CCSID 37.  If I do 
'hex edit line' in WDSc, it shows that the encoding in the source CCSID 37 

should be x'22', but when I push the member I end up with something 
entirely different:
For the first seven characters:

WDSc reports:  Unicode= 0020 0020 0020 0020 0082 0020 002a
                               CP1252  = 20 20 20 20 3f 20 2a
                               CP0037  = 40 40 40 40 22 40 5c

When I push the member to the iSeries I end up with:
40 40 40 40 62 3F 40 5c

Some how x'22' is becoming x'623F'.  I have used this member in other 
iSeries projects with no problems.  Anyone have any ideas why this might 
happen, or where to start hunting for a solution?  I have to admit, my 
knowledge of how the translation from EBCDIC to ASCII/Unicode happens when 

using WDSc is woefully inadequate.

Any ideas would be much appreciated, as I'd really rather not reapply my 
changes to the production version of this source.

Adam
#####################################################################################
Attention:
The above message and/or attachment(s) is private and confidential and is 
intended 
only for the people for which it is addressed. If you are not named in the 
address 
fields, ignore the contents and delete all the material. Thank you. Have a 
nice day.

For more information on email virus scanning, security and content
management, please contact administrator@xxxxxxxxxxxx
#####################################################################################