Since I've written several of these SQL statement processors on my own
and now the ones we have in our products, I can't agree that putting in
OUTPUT parameters is all that difficult.
It's easy to use an API to get the exact parameter definitions from the
STRQMQRY command, for example. Or just look at a prompt and imitate it -
Then it's simply a matter of passing the value to the STRQMQRY command
in the command-processing program for your command.
Even using the QM commands directly instead of STRQMQRY, this is pretty
trivial stuff, seems to me. But I've been playing with this for years,
so maybe I'm jaded!!
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact