RE: Problem with prototyping main procedure

I NEVER use the EXTPGM keyword on the prototype for the "*ENTRY PLIST".
The only time you need to do that is if the compiled program is not the same
name as the source member or more accurately, the same name as that
specified in columns 7 to 21 of the D spec for the prototype.
-Bob


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of CWilt@xxxxxxxxxxxx
Sent: Friday, May 21, 2004 8:27 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Problem with prototyping main procedure

Joel,

I know you said ignore this but, I don't think having the prototype in a
copy member clarifies this answer.


Do you not use the extpgm keyword on the prototype for your mainline in
conjunction with the PI for the mainline?


Even when my prototype is in the same source member, I use the extpgm
keyword.  It was my understanding from Barbara that the extpgm keyword was
required in order to use the PI in place of an *ENTRY PLIST.

Does your work without it?

Charles


> -----Original Message-----
> From: Joel Cochran [mailto:jrc@xxxxxxxxxx]
> Sent: Friday, May 21, 2004 4:53 AM
> To: RPG programming on the AS400 / iSeries
> Subject: RE: Problem with prototyping main procedure
> 
> 
> 
> Just for sake of discussion, why would you need to?  I've 
> never included
> an "internal" extpgm reference and all my main procedures call just
> fine...
> 
> Joel
> http://www.rpgnext.com
> 
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.