Sounds to me like C# is not using the correct parameter types. This is VB.NET code, but your C# guys should be able to make sense of it.

db2DataAdapter.SelectCommand = db2Connection.CreateCommand()
db2DataAdapter.SelectCommand.CommandText = "MYLIB.MYSP"
db2DataAdapter.SelectCommand.CommandType = CommandType.StoredProcedure

db2DataAdapter.SelectCommand.Parameters.Add("Parm1", iDB2DbType.iDB2Char, 25)
db2DataAdapter.SelectCommand.Parameters("Parm1").Direction = ParameterDirection.InputOutput
db2DataAdapter.SelectCommand.Parameters("Parm1").Value = request
db2DataAdapter.SelectCommand.Parameters.Add("Parm2", iDB2DbType.iDB2VarChar, 5500)
db2DataAdapter.SelectCommand.Parameters("Parm2").Direction = ParameterDirection.Input
db2DataAdapter.SelectCommand.Parameters("Parm2").Value = inputParm

db2DataReader = db2DataAdapter.SelectCommand.ExecuteReader()




-----Original Message-----
From: Charles Wilt [mailto:charles.wilt@xxxxxxxxx]
Sent: Tuesday, May 15, 2018 12:36 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Calling Db2 for i stored proc with Named parameters from C# using Db2 connect .NET driver

All,

Has anybody got a exmaple of calling a Db2 for i stored procedure with named parameters from a C# app using the Db2 connect .NET driver?

We've tried a few ways, but we keep seeing a Sqlstate => 42884 - No routine was found with the specified name and compatible arguments.

with a performance monitor running, I can see that the "PREPARE" call is being done without using parameter names.
PREPARE "CALL MYLIB.MYSP(?,?,?)

instead of
PREPARE "CALL MYLIB.MYSP(p1=>?,p2=>?,p3=>?)"

I'm not the .NET guy having the issue, I'm the guy that wrote the SP and is trying to help. :)

Thanks!
Charles


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.