AW: QDDLSRC - put library names in source?

We moved from DDS to DDL
1. All SQL DDL Sources are located within a source file named QSQLDDL
2. Instead of TXT we set the attribute according the object we want to
create, i.e. PF, VW, IDX. If there are dependencies for example foreign keys
or views that are base on other views we also added a counter, i.e. PF must
be created first after PF01 after PF02 etc.
3. We do not specify any library or schema within the SQL Scripts.
4. We create our SQL objects by executing RUNSQLSTM through PDM
We added an PDM Option as follows:
RUNSQLSTM SRCFILE(&L/&F)
SRCMBR(&N) COMMIT(*NONE)
ERRLVL(21) DATFMT(*ISO)
DFTRDBCOL(&O)
ERRLVL(21) allows me to ignore errors that occur if a drop statement
fails because there was no object available. (Other level 20 errors must be
checked manually)
DFTRDBCOL allows me to use the object library specified in PDM

In this way you easily can create the database object in each
library/schema you want

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Gqcy
Gesendet: Wednesday, 11. August 2010 19:55
An: midrange-l@xxxxxxxxxxxx
Betreff: QDDLSRC - put library names in source?

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