× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I've experienced this as well and not only just using iSeries projects
even just using RSE/LPEX saves does this.  It's also a hit or miss type
thing in my case, it doesn't mangle all occurances just some of them... 


Thanks,
Tommy Holden


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of AGlauser@xxxxxxxxxxxx
Sent: Wednesday, May 24, 2006 8:09 AM
To: Websphere Development Studio Client for iSeries
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
########################################################################
#############

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.