Posted: 8 years 7 months 28 days 12 hours 43 minutes ago
Edited: Tue, 29 Jul, 2014 at 17:05:00 (3163 days ago)
You may want to have a look at how the PARAMETERS are defined in your stored procedure. If they're being called by native IBM i SQL, that's one thing, but if they're being called by .NET you may need to have some SQL standard parameter convention specified. Typically this means "PARAMETER STYLE GENERAL"
I'm no Stored Procedure expert and in fact, I've only written SQL functions using RPG or SQL, never a Stored Procedure, but it sounds like a familiar story.
Posted: 8 years 7 months 27 days 17 hours 8 minutes ago
Show us your CREATE PROCEDURE statement. Bob is right, the parmeter style affects the parms required. Are you able to successfully call the SP from iSeries Navigator?
Chris Ringer
Posted: 8 years 6 months 11 days 20 hours 52 minutes ago
Sorry i did not circle back. We found that the problem was with the inherited library list when the .NET program. We were not seeing it and the SP was blowing up and returning zeros/blanks.
Bob/Chris, thanks for your responses. the Create Proc stmt was solid. Thats why it was so confusing. And I got no help from my .NET programmer. His standard response was, and is, "the problem must be on the AS400, because my program is fine". The problem was i the fuzzy MS server area between .NET and AS400. It was actually a poster on another forum that pointed me to the resolution.
Posted: 8 years 6 months 11 days 20 hours 35 minutes ago
You don't mean this do you? Library List and SQL Functions
The situation might be slightly different from yours but was the solutions the one you're talking about?
Posted: 8 years 6 months 9 days 20 hours 15 minutes ago
Yes. This is the case. Your linked post hit the nail on the head. Thanks. Now we know what to do when we encounter this error with other remote systems, not just .NET