Re: QDDLSRC - put library names in source?

[Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>]

When I converted all files from DDS to DDL a few years back, I did 2 things:

1) I still keep the source in QDDSSRC even though it is DDL.  That way,
during the project (which took a year), all source that referred to a
physical file/table or logical file/index/view was stored in the same
place.  Now that I am done, I still keep it in QDDSSRC along with display
and printer file DDS.  I saw no real benefit in separating them.

2) I hard coded the library name in the DDL.  And the library name I use in
the source is JEFF which is the name of my test library.  In this way, I
can't accidentally run that DDL and replace a production object.  (I have a
DROP TABLE/INDEX/VIEW coded in the source prior to the CREATE
TABLE/INDEX/VIEW.  The DROP statement is also normally commented out like
this -- DROP.  Yes, I'm a belt-and-suspenders kind of guy.)

Just my opinions.



On Wed, Aug 11, 2010 at 1:55 PM, Gqcy <gmufasa01@xxxxxxxxx> wrote:

> When we migrate our Source to DDL, should we have the library name in
> the CREATE TABLE/INDEX/VIEW string?
>
> CREATE TABLE  xyzlib/abcfile...
> -or-
> CREATE TABLE   abcfile
> (and use current library as where the file will be built)
>
> How do we create a test data library?
>
> -gerald
>
>
> --
> 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.