|
rob wrote: >>You mean like storing the generated sql statement in a source physical >>file member and doing a RUNSQLSTM ... PROCESS(*SYN) would do? Well almost, except that RUNSQLSTM doesn't allow PROCESS(*VLD) either - it's only available on the STRSQL command, as far as I can see (and also if you change your interactive SQL session defaults, obviously). So even if I copy my statement into a source file and execute RUNSQLSTM over it, I still can't get the full validity checking that I'd like. In fact even the API link you suggested in a subsequent email (for the QSQCHKS API) doesn't allow validity checking :-( Rory
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.