Re: Replacing *entry plist

Prototypes and Procedure interfaces can be used instead of *ENTRY PLIST. I 
use them all the time. 
Name your prototype and PI the same as the program....  All in the "Who 
Knew..." redbook on RPG.
For others who may follow behind me, on the comment section on the far 
right of the PI, I put *ENTRY PLIST.  That way they can scan, (unless they 
scan position specific - tough for them).

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




MWalter@xxxxxxxxxxxxxxx
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/21/2003 02:32 PM
Please respond to RPG programming on the AS400 / iSeries
 
        To:     rpg400-l@xxxxxxxxxxxx
        cc: 
        Fax to: 
        Subject:        Replacing *entry plist


Hello all,

Checked the archives on this and can't believe that it hasn't come up
before. But currently when calling an RPG module that contains cycle code
from a CLLE module, and needing to pass parameters to the RPG, I still use
*entry plist. Since upgrading to V5R2, I've been trying to use Free Form
RPG. Realizing that there is no free form version of *entry plist, is 
there
a way to create another type of parameter interface that CLLE could use?


Thanks,

Mark


Mark Walter
Sr. Programmer/Analyst
Hanover Wire Cloth a div of CCX, Inc.
mwalter@xxxxxxxxxxxxxxx
http://www.hanoverwire.com
717.637.3795 Ext.3040
/"\
\ /
 X
/ \


_______________________________________________
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.