|
midrange.com
I started using this technique, and I know it is more 'modern', but I
am not sure of the exact benefits. Basically, instead of the
following:
C *Entry PList
C Parm Acronym 3
you would use this:
D AcdChk PR N
D Acronym 3A
D AcdChk PI N
D Acronym 3A
The name (AcdChk) must be the name of the program object.
On Wed, 5 Jan 2005 14:37:31 -0330, RPower@xxxxxxxxxx <RPower@xxxxxxxxxx> wrote:
> To be honest, I'm not sure how to do that. But I'm open to ideas. :)
>
> Ron Power
> Programmer
> Information Services
> City Of St. John's, NL
> P.O. Box 908
> St. John's, NL
> A1C 5M2
> Tel: 709-576-8132
> Email: rpower@xxxxxxxxxx
> Website: http://www.stjohns.ca/
> ___________________________________________________________________________
> Success is going from failure to failure without a loss of enthusiasm. -
> Sir Winston Churchill
>
>
> Tony Carolla <carolla@xxxxxxxxx>
> Sent by: rpg400-l-bounces@xxxxxxxxxxxx
> 05/01/2005 02:34 PM
> Please respond to
> RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
>
> To
> RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
> cc
>
> Subject
> Re: *Entry Plist
>
>
> It probably won't make a difference, but have you tried using a
> prototype spec in the D-specs instead of *Entry Plist in the Calc
> specs?
>
> On Wed, 5 Jan 2005 14:13:09 -0330, RPower@xxxxxxxxxx <RPower@xxxxxxxxxx>
> wrote:
> > Can you have the fields in the *Entry Plist definition defined as part
> of
> > a data structure? Here's my definition of the 20 parms being passed to
> > this program:
> > d LibsData ds
> > d Lib01 10
> > d Lib02 10
> > d Lib03 10
> > d Lib04 10
> > d Lib05 10
> > d Lib06 10
> > d Lib07 10
> > d Lib08 10
> > d Lib09 10
> > d Lib10 10
> > d Lib11 10
> > d Lib12 10
> > d Lib13 10
> > d Lib14 10
> > d Lib15 10
> > d Lib16 10
> > d Lib17 10
> > d Lib18 10
> > d Lib19 10
> > d Lib20 10
> > d Libs 10 Dim(20)
> > d Overlay(LibsData)
> >
> > The Lib01 thru Lib20 are my parms being passed to this program. However,
> > I'm getting an error during compile time:
> > RNF5029: Result-Field entry of PARM operation in *ENTRY PLIST is not
> > valid; specification is ignored.
> > Any ideas?
> >
> > Ron Power
> > Programmer
> > Information Services
> > City Of St. John's, NL
> > P.O. Box 908
> > St. John's, NL
> > A1C 5M2
> > Tel: 709-576-8132
> > Email: rpower@xxxxxxxxxx
> > Website: http://www.stjohns.ca/
> >
> ___________________________________________________________________________
> > Success is going from failure to failure without a loss of enthusiasm. -
> > Sir Winston Churchill
> > --
> > 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.
> >
> >
>
> --
> "Enter any 11-digit prime number to continue..."
> --
> 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.
>
>
--
"Enter any 11-digit prime number to continue..."
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.
