×
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.
On Wed, Oct 19, 2011 at 6:14 PM, Eric Chan <emchan@xxxxxxxxxx> wrote:
The error message comes up if one of the selected lines would exceed
the record length after commenting. ?The block commenting shifts your
line over to the right by one character (two in free), so the idea of
the error is to preemptively prevent truncation.
Eric Chan
Rational Developer for Power
IBM Toronto Software Lab
A simple solution we use in our shop is to create the source physical files
with a longer record length than the IBM default. We use a record length of
132 (SRCDTA = 120), the maximum that SEU can easily handle with all data
viewable on a single screen.
In V6R1 IBM added the MARGINS parameter to the RUNSQLSTM, allowing you to
use SRCDTA up to a maximum length of 32754. When we create complex stored
procedures and UDFs we will always maintain them in RDP so we throw away the
SEU limitations. This allows us to write code that is much easier to read
and maintain.
Jon Everton
Vertex Business Solutions
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.
midrange.com
