|
Sideline: *entry plist can be replaced by a PI definition. See page 36 of the Redbook 3.3.2 Procedure-interface definitions. I will admit that I put a comment that says something like 'replaces *ENTRY PLIST' for the blokes who scan for *ENTRY with their editor. Yuriy_Simonoff@WHJI.COM on 04/10/2000 10:35:28 AM Please respond to RPG400-L@midrange.com@Internet To: RPG400-L@midrange.com@Internet cc: Fax to: Subject: Re: File and Program field definition no it didn't define it as a CONST. There is no PI definition, because it is external pgm with PLIST: 065.00 C *Entry Plist 066.00 C Parm PLU 067.00 C Parm Value and variables defined in the programs as: 0021.00 D PLU S 11S 0 0022.00 D Value S 5S 0 rpg400-l-owner@UUCPHOST.MCS.NET on 04/07/2000 05:54:13 PM Please respond to RPG400-L@midrange.com To: RPG400-L@midrange.com cc: (bcc: Yuriy Simonoff/WHJI) Subject: Re: File and Program field definition Does the procedure interface (PI) on the called program defined it as CONST? Yuriy_Simonoff@WHJI.COM on 04/07/2000 04:45:04 PM Please respond to RPG400-L@midrange.com@Internet To: RPG400-L@midrange.com@Internet cc: Fax to: Subject: File and Program field definition I've got something weird. 1. There is an external program that is defined to the calling program through procedure prototype as: 54+D GetCoupon PR extpgm('ZED005') 55+D PLUParm 11S 0 56+D ValueParm 5S 0 *** note PLUParm parameter. 2. There is a file that has PLU defined as: 0012.00 A S01PLU 11S 0 COLHDG('COUPON PLU') 3. In the program I call procedure as: 0186.00 C CallP GetCoupon(S01PLU:CouponValue) 4. Compiler gives me an error: *RNF7535 30 1 The type and attributes of the parameter do not match those of the prototype. 5. Looking at compiler listing I see that S01PLU field is defined as packed: 0008.36 S01PLU P(11,0) 6. This field is defined ONLY in the file and in the program it gets only referenced. Does anybody have an explanation for this phenomena? +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.