× 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.



The text encoding is CP1252.  As for your other questions, I can't answer 
them for this specific issue as it is the only time I've seen it happen. 
It is RPGLE, and only has the offending 'special' character in column 5.

I have noticed that the behaviour in most cases seems to be converting the 
x'22' to a ? (x'3f' in cp1252, x'6f' in cp037), which then gets pushed 
back to the iSeries as x'6f' rather than x'22'.  I don't know how to 
repeat the original problem, but my steps to repeat the problems I've just 
described are:

Create a new member in QRPGLESRC named 'MANGLETEST' using PDM
Using SEU, add 5 lines, each consisting of six blanks followed by '* 
comment' (without the quotes of course)
Using DBU (or some other hex editing method) to put character x'22' in the 
first position of line 1, second position of line 2, and so on.
In WDSc, find the MANGLETEST either in RSE or using the table view (I used 
the table view).
select the file, context menu->Add to iSeries Project.
Open the member that was just downloaded to a project.

The x'22' characters are now converted to x'6f'.  Note that if I simple 
Ctrl+Shift+A to open the member in the editor, the characters are 
correctly handled.

Hope this sheds some light on the issue,
Adam

wdsci-l-bounces@xxxxxxxxxxxx wrote on 24/05/2006 11:34:12 AM:

> Look at the file properties (select the file, context menu -> properties 
->
> info)? Is the text encoding CP1252? I'm assuming it is, but check 
anyway.
> Is this behavior specific to this column or a particular programming
> language?
> _______________________
> David Dykstal
> david_dykstal@xxxxxxxxxx
> 
> 
>  
>              AGlauser@erbgroup  
>              .com  
>              Sent by: To 
>              wdsci-l-bounces@m         "Websphere Development Studio  
>              idrange.com               Client for iSeries"  
>                                        <wdsci-l@xxxxxxxxxxxx>  
> cc 
>              05/24/2006 08:08  
>              AM Subject 
>                                        [WDSCI-L] Hex codes in position 5 
 
>                                        are being mangled  
>              Please respond to  
>                  Websphere  
>                 Development  
>              Studio Client for  
>                   iSeries  
>              <wdsci-l@midrange  
>                    .com>  
>  
>  
> 
> 
> 
> 
> 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
> 
#####################################################################################
> 
> --
> This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
> mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.
> 
> 
> -- 
> This is the Websphere Development Studio Client for iSeries  (WDSCI-
> L) mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.

#####################################################################################
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.