Re: Executing a program through an ODBC/JDBC connection?

On Fri, Sep 27, 2024 at 11:59 AM Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

That has nothing to do with the fact that there's no store procedure
registered and everything to do with the (lack of) library list configured
for ODBC/JDBC.

It is possible to configure a library list for ODBC (and presumably
JDBC) from the client side, when setting up the connection. As far as
I can tell, this is rarely done. The usual thing to do, if library
list is important, is to wrap whatever it is you want to call in a CLP
that sets up the library list (and any other relevant environment
details), and call that wrapper.

My memory is hazy, but I *think* an ODBC connection will default to
the library list of whichever user profile was used to make the
connection.

Regardless, I think the CLP wrapper is the way to go, because that is
the most explicit, obvious, and maintainable approach. I avoid relying
on configuration details (like user profile/job description, ODBC
connection parameters, etc.) whenever possible.

One other thing to note: if for whatever reason CALL statements aren't
supported by the ODBC/JDBC client, you can always use the
QSYS2.QCMDEXC scalar function to issue an arbitrary CL command.

John Y.