Re: [IBMiOSS] UDF works in STRSQL but not over ODBC using Python

We have an RPG program wrapped by a UDF. This function works from
STRSQL, but not in Python via ODBC. The error I'm getting is

SQL0204 - MY_FUNCTION_NAME in *LIBL type *N not found.


I checked the library of the function using the SYSFUNCS view and
added that library to my ODBC connection's library list (using the
ADDLIBLE command via itoolkit on the same connection, if that matters)
and I still get the same error message.

We steer all of our 'external' data access via job descriptions, which
in turn are set by user profile. None of the external code or
configurations changes just because we want to switch between DEV and
PROD. So, connect with DEVUSER to get the DEV *LIBL, and connect the
exact same code/config with PRODUSER to get the PROD *LIBL.

That said, very often, a 'NOT FOUND' in SQL means 'SIGNATURE DOES NOT
MATCH'. I'd carefully check the data types being used in the Python
code. In particular, CHAR vs VARCHAR. Another possibility is authority
- is the same user profile being used in STRSQL as ODBC?

I can't remember the last time I used STRSQL. Ten years, maybe? So, no
advice on that except to say that ACS SQL Script tool also uses ODBC,
so it seems a better way to test database work to me.

--buck