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 is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.