|
AFAIK, subfield is not allowed. However, you could use the datastructure (meaning LibsData) as the parm. -----Original Message----- From: rpg400-l-bounces+lim.hock-chai=arch.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+lim.hock-chai=arch.com@xxxxxxxxxxxx]On Behalf Of RPower@xxxxxxxxxx Sent: Wednesday, January 05, 2005 11:43 AM To: RPG programming on the AS400 / iSeries Subject: *Entry Plist 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.
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.