Re: is there a way too batch SQL scripts

On 1/6/2015 5:46 PM, Darryl Freinkel wrote:

You can run multiple sql statements in 1 script.

My scripts already contain several complex scripts so it's easier to

break them into smaller scripts, more like object oriented.

In this way I can easily test and debug each script.

Yes, I do this every day for a mixture of ad hoc queries and production
work. I debug using iNav and when the script (quite possibly multiple
statements) is working, I copy/paste the SQL statements into an RPG
program where I can make it production-grade with error checking,
variables and all that.

I understand about source file width, and in my case I don't write an
SQL statement that's wider than the screen because I personally don't
find really wide statements easy to read.

When it comes to testing, I basically use iNav for the initial,
pre-production testing only. After the program goes into production,
any mods get tested right there in the RPG program. I don't copy the
SQL out of the RPG and paste it back into iNav for testing.

I mention that because it sounds like your workflow is a bit different;
that you keep the production SQL in the stream file and not only test
from those scripts, but run against production. Which is why you really
only want one copy of those scripts on the system.

In my case, that 'one copy' lives in my RPG programs, in my production
environment.

--
--buck

'I had nothing to offer anybody except my own confusion' - Jack Kerouac
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.