|
Ah, good point. Here's the prototype for the mainline I posted. d MainLine pr extpgm('AC405I') d pPlantCode like(SDPCDE) d pPartNumber like(UPPART) d pClass like(UPCLAS) HTH, Charles > -----Original Message----- > From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] > Sent: Tuesday, March 16, 2004 2:12 PM > To: RPG programming on the AS400 / iSeries > Subject: RE: PI replaces *entry Plist > > > And don't forget the prototype... > Often done as a /copy member. Sometimes done as a > conditional include. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > CWilt@xxxxxxxxxxxx > Sent by: rpg400-l-bounces@xxxxxxxxxxxx > 03/16/2004 01:44 PM > Please respond to > RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> > > > To > rpg400-l@xxxxxxxxxxxx > cc > > Subject > RE: PI replaces *entry Plist > > > > > > > Dave, > > It's pretty easy....just code a PI right before your mainline C-specs. > > > ************************************************************** > ******** > * Begin MAINLINE > > ************************************************************** > ******** > d MainLine pi > d pPlantCode like(SDPCDE) > d pPartNumber like(UPPART) > d pClass like(UPCLAS) > > * Position file at beginning for initial read > * in case of SHARE(*YES) on open, or in case previous > * call to program returned without LR set to *On > c *LOVAL Setll MPUNPR > c *LOVAL Setll MPUNPRM > > HTH, > Charles > > > -----Original Message----- > > From: Dave Boettcher [mailto:DBoettch@xxxxxxxxxxxxxxxx] > > Sent: Tuesday, March 16, 2004 1:08 PM > > To: rpg400-l@xxxxxxxxxxxx; RPGIV@xxxxxxxxxxxxxxx > > Subject: PI replaces *entry Plist > > > > > > Can anyone point me to information on using PI instead of the *entry > > PLIST? > > > > I thought I saved the e-mails from a few months ago, butt > cannot find > > them. > > The archives only show one post - when I paste the code > from that post > > into CODE I get errors. > > > > What I want to do is use the procedure interface for the > > *entry Plist. > > > > > > TIA, > > > > Dave Boettcher > > > > Any questions, please let me know. > > > > Thanks, > > > > David P. Boettcher CCP > > Senior Systems Analyst and Coordinator > > IBM Certified Specialist - RPG IV Developer > > Kenosha County Information Services > > County Courthouse, Room LL13 > > 912 56th St > > Kenosha, WI 53140-3747 > > e-mail: dboettch@xxxxxxxxxxxxxxxx > > Voice: 262.653.2520 > > > > A truly happy person is one > > who can enjoy the scenery on a detour. > > _______________________________________________ > > 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. > > > _______________________________________________ > 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. > > > _______________________________________________ > 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.