RE: source file

From: Elvis Budimlic <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: source file
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Date: Thursday, October 9, 2008, 4:35 PM
Good news is that V6R1 brings you some terrific enhancements
in this realm
that would solve this riddle for you (provided you're
on V6R1 of course).
See this article for details:

http://www.mcpressonline.com/tips-techniques/programming/techtip-runsqlstm-i
s-bigger-and-better-in-v6r1.html

If you're on a prior release, I'm afraid you'll
have to live with the
limitation or resort to an alternate way to build your
database objects
(i.e. iNav's Run SQL Script facility).
BTW, I think STRQMQRY has a similar limitation (for some
reason I keep
thinking 79, but that can't be right).

Hth, Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM
i, i5/OS and
OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: source file

Hi All,
To promote the SQL based objects such as Tables, Stored
Procedures, etc.,
TurnOver uses the RUNSQLSTM which has the limitation that
it only reads the
first 80 columns of the source file even when the file
length is greater
than that and we took 112 as source file record length.
So, if I create or
change the code using a file with record length greater
than 80 and the
code extends beyond the 80 columns then the code in column
81 and above gets
ignored. This is resulting in a syntax error thus
preventing the objects
from being promoted or if this doesn't result in a
systax error then the
objects will be promoted with no errors and could cause
runtime error .
Is it only resolution that I have to reduce source file
length (QSQLSRC)
from 112 to 92?
Are there any commands that support only 80 length or less
than that or more
that? any insights are highly appreciated.


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