Re: RunSQLStmt in production

On 3/29/2013 11:17 AM, James H. H. Lampert wrote:

Can you suggest a better way to automate the creation of SQL tables and
views, than to call RUNSQLSTM from a CL program?

Use a HLL program that can trap errors and make decisions based on that.
If there is something worse than 'production code' that can't handle
errors, I'm not sure what it might be.

Conversely, how would adding the ability to process a naked SELECT (as
opposed to one encapsulated in the creation of a VIEW) be useful in
RUNSQLSTM, given that we have STRSQL and various iNav functions (not to
mention freeware utilities like SQUIRREL) for that?

When testing, it's quite handy to have a quickie utility to show me the
columns that are different between the 'before' and the 'after' versions
of a file. I like to see this ordered by my key, and I like to see just
the columns that actually have changes rather than a generic query where
I need to look through each column side by side. This sort of thing
pretty much needs to be dynamically scripted which rules out STRSQL and
iNav (which cannot be scripted at all) as well as Squirrel, which might
be scriptable, but I'm not sure how to do that from the IBM side.

Bizarrely enough, I used this technique in CL before I had the ability
to use SQL in RPG (which is how I'd do the same thing now).
--buck