RTVSQLSRC

[robberendt]

RTVSQLSRC

** This thread discusses the article: RTVSQLSRC **
Advantages to SQL over DDS include: I) One stop shopping. Currently, what you can store in a single RUNSQLSTM member would require not only a DDS but a CL to create the file. Providing you use referential integrity and other constraints. Plain DDS is just 'too loose'. Not having the one stop shopping VERY often encourages developers to not use constraints.

[R.Cozzi]

RTVSQLSRC

** This thread discusses the article: RTVSQLSRC **
The API allows you to retrieve the equivalent SQL for an existing database file, whether original created with SQL or DDS. That's all. The RUNSQLSTM command can be used to process the output from my RTVSQLSRC command; that is recreate the file using SQL statements. Will the file be identical to an existing file created with DDS? Sometimes, but not always. SQL after, as you've pointed out, does not support the concept of record format names. For database, record format names are somewhat useless in today's world (meaning new files should not be concerned with them). But legacy issue are always "issues" so that's to be expected.

[R.Cozzi]

RTVSQLSRC

** This thread discusses the article: RTVSQLSRC **
I think using DDS to create files is fine. But it seems as though the reliance on DDS is fading and learning to use a more global/portable data defnition language is a good choice. The goal of my article was to illustrate that you don't really give up anything by creating your files with SQL. Of course if you have multi-format files that require record format names, SQL will NOT support that one situation. Also, unless and until IBM comes up with an alternative to DDS for External Print Files, DDS is here to stay. -Bob

[dchristie]

RTVSQLSRC

** This thread discusses the article: RTVSQLSRC **
These articles are always interesting and informative, but I must ask: What is the advantage of using SQL to create files over DDS?

[luc.pittoors@abvv.be]

RTVSQLSRC

** This thread discusses the article: RTVSQLSRC **
"The RTVSQLSRC command can retrieve the SQL statements needed to create any file on the system, regardless of whether or not the file was originally created with SQL or DDS" . How can the cmd do what it claims to do ? ... ... nowhere I can find an SQL verb that mimics a DDS recordformat name. So the "SQL stmt to create any file" results ALWAYS in levelchecks for any created file that formerly existed on an AS400 or iSeries system. In other words, for our system, the "SQL stmt to create any file" creates ... useless files all the time Help !

[MCWebsite.Staff]

** This thread discusses the article: RTVSQLSRC **
** This thread discusses the Content article: RTVSQLSRC0