|
Scott, -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Scott Klement Sent: Thursday, July 22, 2004 11:04 AM To: RPG programming on the AS400 / iSeries Subject: Re: Definition not found for internally defined procedure Hi Rick, >I assume that this is a message that occurs during binding, and shows up >in your job log? Yes. >Here's the thing that surprises me. The message that you posted says that >the program is looking for something called 'CmpVal' -- but the code that >you posted contains a procedure called 'CMPVAL' -- ILE procedure names are >case-sensitive, so these would be two different procedures! I'm not seeing an explicit reference to 'CMPVAL' in the code. Either in the source or the previous message. Are you referring to the conversion mentioned farther down in your message? >I suspect that you've got %paddr('CmpVal') coded somewhere. Or that >you've coded an EXTPROC statement that you didn't show us when you posted >your prototype. Yep, %paddr('CmpVal'). >Try making it read: %paddr(CmpVal) (without the quotes) this will tell >RPG to use the procedure name from the CmpVal prototype. When you put the >procedure name in quotes, ala %paddr('CmpVal') it directly searches for a >procedure with that exact name instead of checking the prototype. Removing the quotes worked but I'm not sure I'm following all of this. Where is it searching for a prototype? I thought it searched the source first before going to binding directories. I compared the prototype to the definition many times to check for stuff like case to make sure they matched. I'm confused as to why the compiler didn't match them up. >If you do want to use the procedure name directly, it should be >%paddr('CMPVAL') since (in the absense of an EXTPROC keyword) RPG converts >subprocedure names to all-uppercase.
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.