Hi Edmund,
Changing the text file encoding to UTF-8 fixed the issue.
The source added to the iProject didn't contain the "?" character anymore. What's even better is that when this same source is pushed back into the iProject associated library in the iSeries the comment line remained highlighted. Doing a source compare confirmed that there wasn't any change made by the upload/download process into the source.
I'll still be doing more testing with a few more sources but I think this issue can be considered as closed, barring any issues/errors that I didn't notice.
Thank you very much!
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Edmund Reinhardt
Sent: Saturday, August 30, 2014 4:11 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.1 issue on uploading sources with colorized comments
Eduardo,
RDi does not have any other tooling. I think the semi manual conversion is the best option so far.
I was wondering if you set the Preferences->General->Workspace Text file encoding to UTF-8, would it handle the hex characters any better.
Regards,
Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i
Phone: 1-905-413-3125 | Home: 1-905-854-6195 IBM
E-mail: edmund.reinhardt@xxxxxxxxxx
RDi YouTube: 8200 Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham, ON L6G 1C7
Find me on: LinkedIn: Canada
http://ca.linkedin.com/in/edmundreinhardt/
From:"Fajardo, Eduardo" <eduardo.fajardo@xxxxxxxxx>
To:"Rational Developer for IBM i / Websphere Development Studio
Client forSystem i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date:29/08/2014 11:35 AM
Subject:Re: [WDSCI-L] RDi 9.1 issue on uploading sourceswith
colorizedcomments
Sent by:"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Thanks, Ken. I appreciate your help.
Someone from the team already created a utility to do just that as well as including the verification of the update. Apologies for the late notice but as I mentioned earlier, we're going to migrate all of our sources to RDi/SVN for the first time and it will entail running this utility hundreds of times with the number of releases/libraries that contain the offending comment lines. The in-house developed utility runs thru any or all source member/s in a specific library, btw.
However, I was hoping that there's an easier way that won't require running this kind of utility. I mean if there is a configuration file somewhere, much like the host character preferences for the LPEX display, that can be tweaked to serve this purpose and run seamlessly with the uploading of sources, that would be a lot easier for everyone. I'm pretty sure there are other installations that use colors in their codes and they'll encounter this as well.
I guess the option is not yet in RDi 9.1 so we will have to do tweak the sources in a semi-manual way. I hope IBM releases an update that caters to it though.
Thank you Ken and Edmund.
Cheers.
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Friday, August 29, 2014 10:49 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.1 issue on uploading sources with colorized comments
Create a simple an RPGLE to override the member with ExtFile to open the correct member. And then use %XLATE to convert invalid Hex Code to Blanks.
At least that is what I did! <smile>
My Mickey-Mouse program to do this on the Power-System running IBM i. And I use the User-Action: "Remove Special Characters"...
CTL-OPT debug(*yes) dftactgrp(*no) Option(*Srcstmt:*Nodebugio);
DCL-F qrpglesrc disk(140) Usage(*Update) ExtFile(LF) ExtMbr(N) UsrOpn;
dcl-s LF Char(21);
DCL-C Hex x'000102030405060708090A0B0C0D0E0F+
101112131415161718191A1B1C1D1E1F+
202122232425262728292A2B2C2D2E2F+
303132333435363738393A3B3C3D3E3F';
DCL-C blk x'40404040404040404040404040404040+
40404040404040404040404040404040+
40404040404040404040404040404040+
40404040404040404040404040404040';
// *ENTRY Interface for Main Procedure
DCL-PI *N;
l CHAR(10);
f CHAR(10);
n CHAR(10);
END-PI;
Iqrpglesrc ns
I 1 6 2Srcseq
I 7 12 0Srcdat
I 13 140 Srcdta
LF = %Trim(L) + '/' + %Trim(F);
open qrpglesrc;
read qrpglesrc;
dow not %eof;
SRCDTA = %XLATE(hex:blk:SRCDTA);
eXCEPT OUTPUT;
read qrpglesrc;
enddo;
close qrpglesrc;
*inlr = *on;
return;
OQRPGLESRC E OUTPUT
O SRCSEQ +0
O SRCDAT +0
O SRCDTA +0
Tried to keep it extremely short & simple to paste into Email message...
<grin>
-Ken Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Fajardo, Eduardo
Sent: Friday, August 29, 2014 7:23 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.1 issue on uploading sources with colorized comments
RFE26471Display hex code characters that represent 5250 display attributes in LPEX (Windows 7)
This fix applies only when viewing iSeries sources via LPEX. However, when this source is uploaded to an iProject column6 changes to "?" and is also the same character that gets pushed back to iSeries when compiling that it gets annoying.
Using colors in a source may be dabatable but isn't there a way to replace the hex code attribute to blanks instead of "?"
Thanks.
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Fajardo, Eduardo
Sent: Wednesday, August 27, 2014 9:48 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] RDi 9.1 issue on uploading sources with colorized comments
Hi,
I'm new to RDi and our company is moving forward to using RDi 9.1 with SVN as our SCM.
We are currently piloting RDi w/ SVN and I've learned that the Host Character preferences is a new thing for RDi 9.1. I set it up to replace the colorized comments hex attribute (column 6) to blanks when initially they appear as question marks (?) when viewed via LPEX editor. I was able to remove the question mark when viewing the remote source via LPEX.
However, when I add the source to my iProject and open it, the "?" sign still appears.
Maybe some of you have encountered this bit before. Thanks.
"Misys" is the trade name of the Misys group of companies. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys.
Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.
"Misys" is the trade name of the Misys group of companies. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys.
Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & 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 Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.
"Misys" is the trade name of the Misys group of companies. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys.
Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & 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 Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.
"Misys" is the trade name of the Misys group of companies. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.
midrange.com
