PGMA has an *entry plist with 2 parameters, all fixed C-specs.
PGMB calls PGMA with 3 parameters in the call.
Both programs are RPGLE.
In my testing, there were no apparent errors.
Is there a concern that the data passed in the 3rd parameter may corrupt
memory in PGMA?
This is somewhat an academic question. PGMA currently has two *entry parms
defined. Currently, in development, it is being modified to add a third
parameter. (FWIW, it will be optional because many programs will continue
to call the program with only two parameters. %PARMS is used to determine
the number of parms passed.) There is a web app that calls PGMA with two
parameters currently, but is being modified to call it with three
Since web app deployment and Power i app deployment are on different
schedules, the web app may be deployed before the Power i app. Hence my
This mailing list archive is Copyright 1997-2019 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