×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




No it does not change the record level identifier.

Also, would be no difference in what is generated between 6.1 and 7.1.

On Fri, Aug 6, 2010 at 9:11 AM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.