Also keep in mind that the data types of your parameters must match exactly. SQL allows for overloading of stored procedures.

In other words... If your stored procedure is defined to accept a numeric parameter and you pass a character you will get a message that the stored procedure can't be found.

Glenn

On 4/12/2010 5:03 PM, MattLavinder@xxxxxxxxxxxxxxxxxxx wrote:
I created the stored procedure with iseries navigator. I am assuming it
shortens the name because it is now called PROC_00001. But that object
has never been called. So I know my call the stored procedure call has
NEVER been successful.


You should call the procedure with whatever name came after the CREATE
PROCEDURE statement when you created it. So, if your create procedure
statement was:

[code]
create procedure this_is_a_really_long_name()
// procedure code
[/code]

You need to call it with:

[code]
call this_is_a_really_long_name();
[/code]

It doesn't matter what the object name generate is. The SQL Engine handles
translating the procedure name to the actual system object name.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
______________________________________________________________________


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.