Re: Generating SQL code into a source file

Darryl,

Some more information will be helpful.

What version of iNav are you using? Go to the control panel and open the
"IBM i Access for Windows Properties" then look under the "General" tab.
Mine shows V7R1 with service level SI49800 which is fairly up to date if
not the most current.

What version of IBM i5/OS are you saving to? I have V7R1 with most PTFs
current

That said, when I run the iNav generate on a table in my schema I get a
source member in the QSQLSRC file that is appropriately tokenized in RDi
9.x. It shows in the source code as a comment Version: V7R1M0 100423.

Does the member that is created have a type of SQL?

...

Jim Essinger
Western Power Sports
Boise ID


On Fri, Oct 18, 2013 at 1:23 PM, Darryl Freinkel <
dfreinkel@xxxxxxxxxxxxxxxxx> 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.



The problem I have is that when I generate the source into QSQLSRC, it does
not create it okay. I can open it okay in SEU/PDM. It has highlighting etc.
in the code (junk), but it is usable.



When I open the source in RDi/RDp, it does not recognize the sequence and
date fields in the source file and brings them up as part of the source
record. I then have to delete the first 13 characters of each line and this
is a task with over 50 tables to do.



1. Does anyone know why this is?

2. How do I overcome the issue so that it opens as a normal source
member?



Darryl Freinkel

Assignment 400 Group, Inc.

Tel: 770.321.8562 ext 111 | Fax 770.321.8562 | 2247 La Salle Dr, Marietta
GA, 30062, USA | PO Box 72556, Marietta, GA 30007-2556



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