Re: iSeries Navigator and Rational

Paul,

From Doug's description of the problem, I believe it's related to the fact

that the APIs for generating SQL source used to add tabs for formatting.
LPEX before 9.1.1 didn't handle the tab characters well at all. They
didn't show up as "strange squares". They just messed with the cursor
positioning when you tried to edit. Hex-editing the line would let you
correct these, but that's a pain. APAR SE59530 addressed this precise
issue. The APAR was opened in response to a PMR I had opened.

I believe setting the preference under LPEX Editor, Appearance, Whitespace
Characters had some mitigating effect, but there were some limitations as
I recall. I can't test it as I no longer have anything prior to 9.1.1 on
my system. (Not to mention that the QSQGNDDL now has an option to provide
spaces rather than tab characters. (I don't remember, maybe it's just
selected by default now.) Either the PTFs Doug refers to or RDi 9.1.1
resolve this--or a combination of both.

Michael

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 02/20/2015 01:00:03 PM:

----- Message from Paul Bailey <PaulBailey@xxxxxxxxxx> on Fri, 20
Feb 2015 16:52:41 +0000 -----

To:

Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] iSeries Navigator and Rational

Have a look at this wiki page:
http://wiki.midrange.com/index.php/WDSC_tips/MISC#My_code_doesn.
27t_display_correctly.


The character codes you are looking at were represented as "strange
squares" at one time, and then as invisible characters as operating
systems failed to display them. I think they no longer show-up at
all in RDi 9.1.1 but I am not sure.

You can use the "right-click|source|hex edit line" context menu
option to see the dodgy hex character and change it to a space
character instead (Unicode=0020). Not ideal, but if you can't
upgrade to newer tools just yet then it is a not-completely-
unreasonable workaround.


Paul.