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



Found this setting under LPEX Editor/Save -- maximum line length = 0 (I
hope that means unlimited).
Simlar setting found under each open member LPEX Editor/<tempfilepath>
Maximum Line length = 92. Cannot imagine where that came from. Set to
112. Member saves fine. Close, Open, reverts to 92.

I wonder where it comes from?

"The Cache", I'll have to assume, since clearing that (thanks Thomas)
cleared up the issue.

Stu








On Mon, Jan 27, 2014 at 8:24 AM, <thomas.raddatz@xxxxxx> wrote:


If that does not help, try to clear the file cache from "Preferences ->
Remote Systems -> File Cache". That helped me when I had a similar problem
after I recreated a source file with 112 bytes after I accidentally had
created it with 92 bytes.

Thomas.

wdsci-l-bounces@xxxxxxxxxxxx schrieb am 27.01.2014 14:36:30:

Von: vhamberg@xxxxxxxxxxxxxxx
An: wdsci-l@xxxxxxxxxxxx,
Datum: 27.01.2014 14:36
Betreff: Re: [WDSCI-L] Odd behavior on member save
Gesendet von: wdsci-l-bounces@xxxxxxxxxxxx

Hi Stuart

There's a setting in RDi related to record-length - look in the RPGLE
section under LPEX under Remote Systems, I think - maybe type LPEX in
the filter and go from there.

Anyhow, I think it can be set to 92 or 112 or to length of source file -

I'm not on the system right now - but that could be what is controlling
this.

Vern

On 1/27/2014 7:02 AM, Stuart Rowe wrote:
Darndest thing.

I open a source member from a source file that has record length of
112. I
verified this both on the iSeries and via RSE right click properties
on the
source file.

I key a comment line of dashes right over to column 100, which ought
to be
fine.

I get "Line truncation occurred during the save" and the line lights
up
(pink in my case). The member was saved but did hack off the bit of
line
exceeding column 80 (which sounds suspiciously like the old 92 byte
record
length files of which there are none on my system).

Huh?

I edited the exact same member in SEU. Keyed the same comment all the
way
to 100. Saved just fine. Opened again in RDi, I get the truncation
error
again.

I open a source member from a different source file different library,
record length 112. I key the same comment, all the way to column 100,
saves without issue.

It's not the language (it does the same with C, RPGLE, CMD, PNLGRP,
and
XML).

Anyone have an idea what to check (perhaps cache-wise or temporary
source
member-wise) that makes the two identical source files be handled
differently? I can see (in my server job on the i) a temporary source
member being created and copied and removed.

Stu

--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & 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.


--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution, or
reliance on any of it by anyone else is prohibited and may be a criminal
offence. Please delete if obtained in error and email confirmation to the
sender.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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-Ups:
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.