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



Thanks, Mark, I'll look further.

Yeah, it's my old bugaboo, C. ;-)

My expectation of JLPEX (promoted by IBM, I believe) is that it'll jave "all" the functionality of the LPEX editor of CODE. That one will not allow you to go beyond the record length. Now it'd be better, sometimes if it'd wrap, IMO. JLPEX knows the record length - as soon as you type or cursor past the record length, a left-right scroll bar is displayed.

I think it'd be useful to display the record length somewhere - the properties window in the lower left corner does not do so, right-clicking to get to Properties does not.

I'd be surprised that an LPEX language profile did not consider the iSeries, It seems to me, it did in CODE.

But again, I'll dig a little more.

Thanks

Vern

At 07:21 PM 9/19/2003 -0400, you wrote:

Vern,

What language is this, C?  I think it is parser specific.  The C parser
that is there in LPEX was probably originally written without the iSeries
in mind.

When I am editing CL I do get warning when I go past the end of the line,
and if I have the CL formatter turned on, it will automatically fit and
wrap the source.

Did you go through the LPEX preferences to see if there was anything about
line length and wrapping?

Mark



      To:   websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>
      cc:
      bcc:
      Subject:    [WDSCI-L] Line truncation message - how to avoid disaster
Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
09/19/2003 05:56 PM
Please respond to Websphere Development Studio Client for iSeries
<font size=-1></font>





















Just got the message that says ' Line truncation occurred during the save'.
I was working in version 5 RSE LPEX, seu editor profile. Unlike CODE, there
is nothing to stop editing past the record length. I also could find
nothing to tell me how long the record is - properties on the source file
did not show it in any of the 4 panels.

So I need to go back to the green screen or use CODE - after even I am
starting to like RSE better!  8-(

Please, source files are STILL fixed-length, and that is not going away
soon.

Regards
Vern


_______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.






_______________________________________________
This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.