|
Don, Have you gotten an answer for this yet? If not, then your problem is the VALUE keywords. SQL ( and CL for that matter ) don't support pass-by-value. If you want those params to be read only in the RPG, then use the CONST keyword. HTH, Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121 -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Fisher, Don Sent: Tuesday, November 15, 2005 8:09 AM To: 'Midrange Systems Technical Discussion' Subject: RE: Parameter values for SQL function call not passed correctly Sure. I eliminated some spaces to make it easier to read. AProcedure PR 4 0 Parm1 10A VALUE Parm2 1A VALUE Parm3 10A Parm4 7A Parm5 100A Parm1 is the one that's getting the garbage. Thanks. Donald R. Fisher, III Project Manager Roomstore Furniture Company (804) 784-7600 extension 2124 DFisher@xxxxxxxxxxxxx <clip> could you please show the prototype for your RPG-function? <clip>
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.