× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



hi Donna

Personally, I prefer to set up Turnover to use the suggested lengths for the various source types - all except RPGLE (SQLRPGLE) and C/C++ at 92, as they always were. RPGLE at 112. C/C+ maybe at 240 or whatever value gives you the longest SRCDTA field length in a source physical file.

Now QM queries need a record length of 91 - who know why? And QM forms need a length of 162. Also, who knows now why?

So I would just bite the bullet and set RUNSQLSTM source to 92 and be done with it.

HTH
Vern

donna lester wrote:
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.



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