Re: Upcoming spring 2021 RPG enhancements announced today

If you haven't written an upper or lower ile function yet, where have you
been? :)

What RPG really needs these days is the ability to parse JWTs, or be able
to call node.js directly (not using a web service, etc... nothing else
needing to be running). If you can already, I'd love to see how. There is
so much functionality available with OSS (node.js being my favorite) that I
wish I could call it similar to calling Java or even just calling a CL or
RPG program.

Maybe that would be more suited for SQL (JWT processing that is)?



On Sat, Apr 17, 2021 at 8:10 AM <midrangel@xxxxxxxxxxxxxxxxx> wrote:

Naïve, hardly, you raise a good point.

As to your first question, I think you answered it yourself. The compiler
merely turns RPG into executable code. I don't believe there is a classic
"runtime" involved, since ultimately it winds up being some fashion of MI
before the executable is created. Therefore the complier has to come up
with a way to build efficient MI code to execute the instructions. Hence
only patching the complier. Furthermore if IBM wanted to patch more than
the compiler in one PTF they certainly can do that. (and sometimes do...)

Yes, this has been done many, many times in the past going back several
versions if not releases.

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of John
Yeung
Sent: Friday, April 16, 2021 9:29 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Upcoming spring 2021 RPG enhancements announced today

7.3
ILE RPG runtime: SI76098 - you need this PTF on any 7.3 system where
you run a program with %LOWER, %UPPER, or %SPLIT ILE RPG compiler:
SI76100

Interesting. So you need to patch the runtime as well. Is this normal?
I don't recall other language updates mentioning runtime PTFs, only
compiler
PTFs.

Notably, the RPG Cafe entry for the FOR-EACH, IN, %LIST, and %RANGE bundle
doesn't mention any runtime PTFs:

https://www.ibm.com/support/pages/node/6342821

Those strike me as more substantive changes. If anything, I would have
expected those to require an updated runtime. %LOWER, %UPPER, and %SPLIT
seem like functions that a competent and motivated RPG programmer could
implement themselves, and many *have* implemented their own DIY versions.
Granted, the DIY ones are almost always vastly more rudimentary than these
BIFs (for example, a lot of native-English shops wouldn't bother to handle
accented characters). But conceptually, these still seem very achievable
with the preexisting runtime. Is it naive of me to think that?

John Y.
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com