×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Mon, Jun 24, 2019 at 1:25 PM Duane Scott <dscott@xxxxxxxxxxx> wrote:
Doesn't quite fit where there are multiple selects within the same source member.
You're absolutely correct that to be 100% sure you've caught
everything, there is no substitute for inspecting all the code
manually.
However, Art's approach does at least find the most egregious "problem
members" quickly. So if you focus on fixing those first, you will
enjoy an initial phase where *all* the members you look at are
improved, and during that phase, you're rapidly moving the codebase as
a whole toward full robustness. After that initial phase, then it
becomes the same, slow slog that you're suggesting.
I don't work with a lot of SQLRPGLE code myself, but I would expect
that for any given source member which contains multiple uses of SQL,
it's likely that SQL code/state checking is consistently used
throughout the member, or consistently not used anywhere in the
member. The members that would fall through the cracks are the ones
which are inconsistent.
John Y.
midrange.com
