OVERLOADED SQL STORED PROCEDURE PROBLEM

[K.Forsythe]

Can you show us the create statement? I expect the system to take the object name from there.

[K.Forsythe]

When you create an SQL procedure, the system implements that by creating a C program with embedded SQL. Its all (nearly) invisible behind the scenes. I don't think you need to worry about the C module that is created - just keep track of the SQL procedure. iSeries navigator is great tool for seeing the various SQL objects in a library.

[Guest.Visitor]

I understand that, however, my CLE program is being created with a name the AS400 gives it instead of the name of my source member. I would like to find the root cause of this in case other developers in our shop make the same mistake I did.

[Guest.Visitor]

I think I accidently overloaded an sql stored procedure by compiling a 2nd version of it with an additional parm before dropping the first version. Somehow by fumbling around with the drop procedure commands I was able to get rid of everything (I checked the tables in QSYS2 to be sure). However, now when I use RUNSQLSTM to create the procedure it creates a CLE object with a name the AS400 gives it instead of the name of my source member. How can I fix this ?

[K.Forsythe]

What is the problem being caused by the CLE program having a name different than what you expect? Is the call to the SQL stored procedure failing? Kevin