Re: SQL question on default *LIBL at connection

Elvis Budimlic wrote:

Nice find Chuck. Jim is using a .NET provider
(IBM.Data.DB2.iSeries), not the OLE DB one. Do you know
if same restrictions apply to the .NET driver?

I had to shutdown & restart... memory issues. Could not even get the name & link of the .pdf I was viewing; was not even sure the post was going to go through. I would have to search again, but... Probably going to be away most of the [expected to be] nice weekend. MC time. I recall I effectively searched:
overloading sql stored procedure ambiguous deriveparameters
Variations on that search using "system naming" or "library list", resolution [name, function, routine], "best fit"

Given my complete ignorance on DeriveParameters() [and I read nothing due to the memory issue], I think the first step for Jim would be to eliminate any UDT or errant overloading. Overloading [within a library] may be an accident, which can be eliminated.

Regards, Chuck