If anyone wants to see what has been fixed when in RDi, just go to our fix
list.
http://www-01.ibm.com/support/docview.wss?uid=swg27038481
There are tabs to take you back to 9.0
Edmund
From: Edmund Reinhardt/Toronto/IBM@IBMCA
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Date: 06/04/2016 05:50 PM
Subject: Re: [WDSCI-L] Question on invalid characters in the member.
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Hi Darryl,
The latest RDi will work fine with V5R4, I highly encourage you to upgrade.
The issue began with Windows 7 and a Microsoft font change.
The issue with hex characters was solved in RDi 9.1
|-----------+-------------------------------------------------------------------------------------------|
|RFE26471 |Display hex code characters that represent 5250 display
attributes in LPEX (Windows 7) |
|-----------+-------------------------------------------------------------------------------------------|
But I do think it is a good idea to get rid of the hex characters, since
they are not proper EBCDIC content.
This was discussed on the list
http://archive.midrange.com/wdsci-l/201403/msg00154.html
Apparently some others on the list have created simple tools to replace
these characters with blanks.
HTH
Edmund
From: "Darryl Freinkel" <dfreinkel@xxxxxxxxxxxxxxxxx>
To: "WDSC" <wdsci-l@xxxxxxxxxxxx>
Date: 06/04/2016 03:41 PM
Subject: [WDSCI-L] Question on invalid characters in the member.
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
I have had a problem converting RPG to RPGLE. The program was changed to
use
some free form and SQL so SQLRPGLE.
I use RDi (8.03) and have found the following problems that are show
stoppers. Getting a newer release is not possible now and we are on V5R4 at
this site.
1. There are characters in the record that are not visible that skew
the column positions. It may be that in the past the programmers used the
control characters to change line colors.as the data is not visible I
cannot
see what it is. Does anyone know of a fix or work around?
2. When there are these characters, printing the member especially
using the indented print fails when it gets to these characters.
3. I have a program that compiles normally on our development LPAR
but
fails to compile with SQL invalid characters when I compile it on the
production LPAR.
4. I am unable to use scan and replace in RDi as it does not know I
want to do a hex search. Is there a way to do this?
Darryl Freinkel
Assignment 400 Group, Inc.
Tel: 770.321.8562 ext 111 | Fax 770.321.8562 | 2247 La Salle Dr, Marietta
GA, 30062, USA | PO Box 72556, Marietta, GA 30007-2556
--
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.
midrange.com
