Re: External Stored Procedure Vs. External UDF -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Thanks for the guidance, Vern. I'm restricted to the SQL parameter style in
this particular implementation. I'm piecing it together with SG24-6503-02
and D. Gibbs pointed this out this morning:
http://faq.midrange.com/data/cache/185.html

On Wed, Apr 9, 2008 at 9:46 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxx> wrote:

Alfredo

Which parameter style are you using? There are several, and some add
parameters for the call - DB2SQL could have 18-21 parameters if you
expect to use 7 - 6 input, 1 result, 6 input indicators, 1 result
indicator, sqlstate, 3 more, then 0 - 3 optional.

Vern

At 04:32 PM 4/9/2008, you wrote:

I'm not worried about VARCHAR vs. CHAR since Peter's casting suggestion

got

me past that.

The UDF's signature now matches but when it calls the external program

it's

dying because 20 parameters are being passed? even though the UDF only

has

7 defined? ?!!?

Cause . . . . . : Program QQQSVUSR attempted to call program J5540721Z
with 20 parameters. Program J5540721Z expects a minimum of 7 and a

maximum

of 7 parameters.

Recovery . . . : Use the Display Program (DSPPGM) command to determine
the correct number of parameters to pass.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

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.