RE: convert dds to ddl

[Mike Cunningham <mcunning@xxxxxxx>]

I would like to see your source for this. Been thinking about writing something similar but maybe your code can save me some time.

Thanks 

I was actually also contemplating if I could possible write an app that would read DDS source and turn it into a CREATE TABLE or CREATE VIEW or CREATE INDEX and just stop using the CRTPF CRTLF commands

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Friday, August 06, 2010 11:11 AM
To: Midrange Systems Technical Discussion
Subject: Re: convert dds to ddl

The work has already been done. There is a command out there that converts
from DDS to DDL. I call it GENDDL but not sure that was original name. I
will be happy to send you the source if you want it.

GENDDL OBJ(CUSTMAST) LIB(ILFILE) OBJTYP(TABLE) SRCFILE(ALANC/QSRCF)
SRCMBR(CUSTMAST) TEXT('Customer Master in DDL.')

i can't remember if converting to DDL changes the level id's. Will test.

On Fri, Aug 6, 2010 at 9:02 AM, Gqcy <gmufasa01@xxxxxxxxx> wrote:

> I have been doing some reading, and I am ready to create a procedure for
> us to convert our database from dds to ddl.  (making sure level id's are
> protected)
> > http://wiki.midrange.com/index.php/Sql_convert_from_dds
>
>
>
> some questions:
>
> we are at 6.1.  is there a benefit to wait for 7.1?
>
>
> I know I can add field alias, change column text, and field text.
> what else can/should I put in the SQL, without changing the level id?
>
> I will create new SQL indexes prior to re-creating my old logicals.
> what else can/should I do to my logicals?
>
>
> Thanks so much.
>
> 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.