|
My system is down right now. I suspect the problem is from the CL program...I will check the compiled source to make sure it is packed 3,0 Rob Moore Phone: (519) 661-5893 Technical Analyst Fax: (519) 661-4760 London Hydro E-mail : moorer@londonhydro.com <mailto:moorer@londonhydro.com> -----Original Message----- From: Denis Robitaille [mailto:DRobitaille@Cascades.com] Sent: Tuesday, September 29, 1998 4:55 PM To: RPG400-L@midrange.com Subject: Re: RE: Passing parms to RPG Then maybe the variable is not loaded corrctly in the CL. You could run both the CL and RPG in debug mode and display the value of the numeric variable in the CL just before calling the RPG and then, in the RPG, display the value of the parameter in the *entry plist. Also, once in the RPG try the command ATTR <variable>, this will display the definition of the variable. hope this help Denis Robitaille Cascades inc. Tel: 819-363-5187 DRobitaille@cascades.com >>> "Moore, Rob" <moorer@londonhydro.com> 09/29 3:34 pm >>> This is not the case as far as I can tell. Rob Moore Phone: (519) 661-5893 Technical Analyst Fax: (519) 661-4760 London Hydro E-mail : moorer@londonhydro.com <mailto:moorer@londonhydro.com> -----Original Message----- From: Buck Calabro [mailto:mcalabro@commsoft.net] Sent: Tuesday, September 29, 1998 2:50 PM To: 'RPG400-L@midrange.com' Subject: RE: Passing parms to RPG On Tuesday, September 29, 1998 1:02 PM, Moore, Rob [SMTP:moorer@londonhydro.com] wrote: > Oh yes, thanks. I think I remember reading somewhere that the default > parm > size for DEC is 15 5. Yes, it's the default, but you're not using the default here: you've specified *DEC (3 0) in the CL and PARM 3 0 in the RPG. I think Dennis R hit the nail on the head when he mentioned data structures. See if your RPG program is putting the parm in a DS. If it is, then the DS will change the definition from PACK to ZONE - check the compile listing to verify this. Buck Calabro Commsoft, Albany, NY mailto:mcalabro@commsoft.net * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. 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.