Re: Overriding the defaults of a sql command.

On 2/14/2013 4:07 PM, rob@xxxxxxxxx wrote:

I am still transitioning from the mindset of a DDS shop. In a DDS shop
you have QDDSSRC. And you do your CRTPF from that. Transitioning shops
may have QSQLSRC and use RUNSQLSTM on that. So, in theory, you could have
one QSQLSRC producing both your PRODuction schema and your TEST schema.

Here, we store our SQL in a directory off the root and use iNavigator's
SQL GUI to open and execute it. Changing from 'test' to 'production' is
simply changing the SET SCHEMA to the right environment. No SSDs yet.

If we were to get SSDs and I needed to put only production tables on
SSD, I'd probably leave the source where it is, as it is, but write a
green screen command, maybe I'd call it RUNDDL with a parameter for Test
or Production. The underlying code would read the stream file and if
destined for TEST, would replace SSD with ANY and pass the lot to a PREPARE.

Production-bound tables would have their DDL left as-is.

For those of us (me) who would groggily revert to our old habits and try
to use iNav, I'd put some big comment blocks to remind me, er... them to
use RUNDDL instead.
--buck