Re: RDi 9.9 **FREE RPG parser

Thomas and Steve,

I have read the fix list before, but I didn't thought, that # might be a NL character.

So thank you very much for pointing into the right direction.

Kind regards,
Daniel

Am 03.02.2026 um 16:28 schrieb Steve Ferrell via WDSCI-L <wdsci-l@xxxxxxxxxxxxxxxxxx>:
Hi Thomas,

If you have 'Automatic Syntax checking' turned on, the Program Verifier DLLS are called automatically.

This impacts NL text, but ALSO those lovely hex color characters so popular to color 5250 source members.

Steve Ferrell
Team Lead Software Engineer - RDi
Fortra.com





-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Thomas Raddatz via WDSCI-L
Sent: Tuesday, February 3, 2026 9:21 AM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: Thomas Raddatz <thomas.raddatz@xxxxxx>
Subject: Re: [WDSCI-L] RDi 9.9 **FREE RPG parser

External: Pause and review the sender's email address, any URLs before clicking links, opening attachments, or following requests. When in doubt, contact the Service Desk.


Sorry, I made a mistake, because I forgot to start the verifier. I just loaded the member into the editor without starting the verifier.

If I start the verifier I get the same error. The good thing is that adding "-Dfile.encoding=CP1252" to "RDi.ini" fixed the problem. E.g.:

-Dequinox.resolver.batch.timeout=1000
-Djavax.net.ssl.trustStoreType=Windows-ROOT
-Djavax.net.ssl.trustStore=NONE
-Xms2048m
-Xmx2048m
-Dfile.encoding=CP1252

Thomas.



Am Di., 3. Feb. 2026 um 14:58 Uhr schrieb Steve Ferrell via WDSCI-L <
wdsci-l@xxxxxxxxxxxxxxxxxx>:

Hi Thomas and Daniel,

Yes, the Program Verifiers (COBOL and RPG) likely need the work around.

Java changed the default encoding on Windows to UTF-8. The Program
Verifiers are still expecting them to be CP1252.

The compiler team is aware of the issue.

If you don't use the program verifiers, you can turn off the
'Automatic Syntax checking', and the errors should go away.

Steve Ferrell
Team Lead Software Engineer - RDi
Fortra.com





-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Daniel
Gross
Sent: Tuesday, February 3, 2026 7:12 AM
To: wdsci-l@xxxxxxxxxxxxxxxxxx
Cc: wdsci-l@xxxxxxxxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDi 9.9 **FREE RPG parser

External: Pause and review the sender's email address, any URLs before
clicking links, opening attachments, or following requests. When in
doubt, contact the Service Desk.


Hi Thomas,

on my side it's a source member - using CCSID 273 - German W11 -
German partition.

But I will try that - could be the problem.

Thanks,
Daniel

Am 03.02.2026 um 13:57 schrieb Thomas Raddatz via WDSCI-L <

wdsci-l@xxxxxxxxxxxxxxxxxx>:

I use RDi 9.9 on a German Windows 11 PC and your test source does
not show any errors when pasted into a member of an i Project.
My workspace settings are:
Text file encoding: UTF-8
New text file line delimiter: Linux
Opening the same source from a member on the IBM i (Object Table
view) works fine (without errors), too.
Maybe it helps setting property "file.encoding" as described in the
fix
list:
Known issues:
* On Windows, program verifiers issue errors for NL characters. As
a workaround, add the following in the rdi.ini after -vmargs:
-Dfile.encoding=CP1252
I did not need to set that property.
Thomas.

Am Di., 3. Feb. 2026 um 07:56 Uhr schrieb Daniel Gross
<daniel@xxxxxxxx

:

Hi there,
maybe I'm missing something or a default setting has changed, but
my RDi
9.9 is flagging variables and constants starting with # as errors.
**free
dcl-c #CONSTANT 0;
dcl-s #variable int(10) inz(#CONSTANT); #variable = #CONSTANT;
*inlr = *on;
This little program is compiling without problems. But lines 2, 3
and
4 are flagged as error in RDi 9.9.
It's a wild mix of RNF3904, RNF3312, RNF3301, RNF0633, RNF3429,
RNF0607 and RNF0604.
The same code isn't flagged in RDi 9.8.0.6. And as I wrote, the
code compiles without errors (on 7.5).
The same happens with other sources - the example above is only as
short as I thought to have all possible problems
So do I have something wrong, or is this a defect? And if it's a
defect, has someone a workaround until IBM/Fortra is supplying a fix?
TIA and kind regards,
Daniel
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lis/
ts.midrange.com%2Fmailman%2Flistinfo%2Fwdsci-l&data=05%7C02%7Csteve
.f
errell%40fortra.com%7C984ad7ca6e284579462608de6325d804%7Cca81e23b35
09
45eea9983e346acf274d%7C0%7C0%7C639057211379022168%7CUnknown%7CTWFpb
GZ
sb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIk
FO
IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=6XOvuZwgNCR1ifmbcUs
HK
GiwHgtMN4jTGXnzzhWMnBU%3D&reserved=0
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.

--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://list/
s.midrange.com%2Fmailman%2Flistinfo%2Fwdsci-l&data=05%7C02%7Csteve.f
er
rell%40fortra.com%7C984ad7ca6e284579462608de6325d804%7Cca81e23b35094
5e
ea9983e346acf274d%7C0%7C0%7C639057211379109013%7CUnknown%7CTWFpbGZsb
3d
8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjo
iT
WFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=G0wiJg2P3P4JoB8ptBvqT3qPR
ND
tXAHJmcMWr%2FoYt%2FA%3D&reserved=0
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.

--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://list/
s.midrange.com%2Fmailman%2Flistinfo%2Fwdsci-l&data=05%7C02%7Csteve.fer
rell%40fortra.com%7Cb5a08eb828b0434bb20b08de6337f15c%7Cca81e23b350945e
ea9983e346acf274d%7C0%7C0%7C639057289091695524%7CUnknown%7CTWFpbGZsb3d
8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiT
WFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=bWuvPdJPerJ5xTL6dvZl84rozRj
Yoku8%2FkEq4hNBa6E%3D&reserved=0 or email:
WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.


--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://list/
s.midrange.com%2Fmailman%2Flistinfo%2Fwdsci-l&data=05%7C02%7Csteve.fer
rell%40fortra.com%7Cb5a08eb828b0434bb20b08de6337f15c%7Cca81e23b350945e
ea9983e346acf274d%7C0%7C0%7C639057289091783033%7CUnknown%7CTWFpbGZsb3d
8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiT
WFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=so8NcPBb3p22UjRvzTHNznqi%2F
C%2BYMDIyxX4HskvSHOU%3D&reserved=0
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.

--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.


--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.