We've used QSQLSRC but are slowly moving to use the IFS to store the
source. I prefer the IFS because the file width is unlimited and I can be a
little more descriptive with file names and folders. You can view/edit both
source locations with RDi easily, and both work with the RUNSQLSTM command
when it is time for "compile". (You can not edit IFS members within SEU, if
that is a criteria for you.)
It is slightly tricky checking if the RUNSQLSTM command was successful from
within RDi, and I had to create a (mostly-working) wrapper tool to help
with that. Without that kind of tool you need to be disciplined with your
spooled files and always check the command log in RDi first.
You can use IBM's ACS Run SQL Scripts to also work on the IFS source files,
and you can run the entire script or just parts of it with ease. One day
they'll get some "SQL for i" context assistance in this tool, and it will
become infinitely better to write SQL scripts in ACS-RSS than RDi. (A
challenge to see which IBM team beefs up the SQL editing tools first? :) )
Another method I played with was using the IBM Data Studio, which is free
and can be installed within RDi. Within that you can create "data design
projects" (effectively a standard Java project) and store and maintain
source in there. The Data Studio adds a little (IMO) unnecessary complexity
but if I spent more time with it I could've made it work for me. Even
though the script maintenance and database manipulation was mostly decent,
I stopped using it because the Data Studio's user interface in RDi had some
minor but frustrating bugs.
-Paul.
<snip>
from: David Gibbs <david@xxxxxxxxxxxx>
subject: Where do you store the SQL source for your tables, views,
etc?
Folks:
I'm just curious ... where do you store the SQL source for your
tables, views, etc?
Do you put it in a source PF? If so, what name do you use?
Here, we put SQL source in QSQLSRC.
Thanks!
david
midrange.com
