×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 08/20/2019
02:52:17 PM:
I did.
That said, I'd guess that Jack is right. It's wicked unlikely that IBM
is going to spend much effort on Rexx. It was never that popular on IBM
i. It hasn't been enhanced in... well. A long time. The canonical
reference material is in the 6.1 Knowledge Centre but isn't materially
different from the V5R3 material.
But if we don't let IBM know we want improvements, then how will they
know?
REXX, itself, hasn't changed since then so I don't see it as an
issue that REXX/400 hasn't changed, either. Rather, it is changes in
CL/ILE and RPG/ILE that are needed in order to more fully support REXX
procedures. I don't see it as all that difficult for IBM to allow the
REXX RETURN instruction to pass back values in the STRREXPRC command. Once
that is done, then it is another "simple" step to support REXX procedures
from RPG/ILE, too. The first stipulation, of course, is that parameters
passed from RPG/ILE to REXX/400 will *always* be passed by value.
Sincerely,
Dave Clark
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
