|
You don't put the EXTPGM parameter when you're prototyping the PI statements for a program when replacing the *ENTRY/PLIST with a PI. Bob Cozzi Cozzi Consulting www.rpgiv.com -----Original Message----- From: rpg400-l-bounces+cozzi=rpgiv.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+cozzi=rpgiv.com@xxxxxxxxxxxx] On Behalf Of Cyndi Bradberry Sent: Wednesday, August 20, 2003 10:14 AM To: RPG400-L (E-mail) Subject: *Entry PLIST I looked in the archives and couldn't find the answer to my question. Can I code my PLIST this way ? * Program Entry Parameters (PLIST) D LJParms PR ExtPgm(PgmName) D ParmDate 8 D LJParms PI D EndDate 8 * ------------------------------------------------------------------------ D PgmName 10 Inz('LJRB004') The reason for this question is that I have a job stream of 6 programs that all use the same PLIST. I would like to put the PLIST definition into a /COPY module and have the ExtPgm name be a variable that I define in each program. Unfortunately, I can't test this right now. Our test system is currently undergoing some work. Thanks for any help. Cyndi B. Boise, ID _________________________________________________________ "The Idaho Housing and Finance Association provides funding for affordable housing in Idaho communities. IHFA is not a state agency under state law, and uses no state funds or state employees to support its operations." _______________________________________________ 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.
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.