|
Yeah, somehow Brian & I continued our discussion in private e-mail. (Not sure why it wasn't on the list) and I explained about the EXTPGM keyword on the PI.
But... I have a question for you, Barbara... why is the EXTPGM on the PI needed? If you have DFTACTGRP(*YES), and the PI is for a main procedure, shouldn't RPG automatically "know" that it's a program call? What else could it be? This strange requirement of coding the EXTPGM is acting as a deterrent -- people are sticking with *ENTRY PLIST because of stuff like this.
Also, when you put EXTPGM on the PI, why do you need to provide the external program name as a parameter? Surely the program name is not used by the PI -- you can't actually make a CALL using the PI, so why is the external program name parameter required?
If you like, you can consider this a suggestion for the next TR :-)
On 6/21/2013 5:42 PM, Barbara Morris wrote:
I was going to say the same thing, until I tried Brian's example. Then I
realized that the missing EXTPGM keyword on the PI means that the
EXTPROC keyword is assumed.
As an Amazon Associate we earn from qualifying purchases.
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
