I execute a DLTF command (and ignore the possible error message) in
the CL program before executing the RUNSQLSTM command. My software
has to run on a V4R5 machine.
Works great on views and tables.
Not so good on UDFs: even if you DLTSRVPGM the underlying service
program, SQL still thinks the UDF exists until you DROP it.
At any rate, instead of futzing around with prepared statements, I opted
to just generate hard-coded library-specific UDF source on-the-fly, and
ERRLVL 20 the RUNSQLSTM that generates the library-specific UDF.
I figure that the less overhead I have in the UDF, the better, as it
could get called dozens of times per returned record (at least where
there aren't any cached results).
This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact