Re: Generating SQL code into a source file

Don't know what to tell you. What IBM is doing is writing <CR><LF>. I have
told them about it years ago but they have never fixed it.

You might report it to IBM. Maybe they will fix this time. Pretty stupid.

Easy enough to write a program to strip it out.


On Fri, Oct 18, 2013 at 1:49 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 10/18/2013 3:23 PM, Darryl Freinkel wrote:

I am using iNavigator to generate the SQL source for tables I have

created.

It generates the code sort of okay. Going to a IFS file, the source is
great, but it uses the space beyond the 72nd character in the line and

this

makes it difficult to convert into a member in QSQLSRC. So I am using the
option to generate the source to a source file QSQLSRC.

Can't really help with the source physical file, but I would share that
we store our SQL in stream files that we use with iNav. Ours are named
like 'CustomerMaster.sql' and double clicking with Windows Explorer
fires up iNav's SQL app. One can select a single statement to execute,
or several. It's nice to have the SQL to create the table, views and
indexes all in one place. In a pinch, one can edit these with EDTF and
execute them with RUNSQLSTM, although that would require judicious
editing to make sure only the desired statements are processed.
--buck

--
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.