Re: Storing source as DDL instead of DDS

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 02/24/2017
01:27:30 PM:

Doing all new development using DDL instead of DDS is a reasonable
approach.

Since you would be supporting a mixed environment one option would be to

put the DDL into the same QDDSSRC pf. While this may drive a purist mad

I

believe it would make the transition for a new employee the easiest.

We do pretty much the same except we don't store our DDL source in
QDDSSRC. The reason is that we didn't like the 80-column restriction. So,
we created SQLTBLSRC, SQLIDXSRC, and SQLVIEWSRC source physical files with
a longer record length and simply specify the WIDTH() option for the
RUNSQLSTM command. We are very happy with the results.

Sincerely,

Dave Clark