As well RDI should beep with each edit action (typing a character, deleting
a character, etc.) on the line while the line extends beyond the source
file line length. Also there is a message displayed in the status line at
the bottom of the edit session when there will be truncated lines.
When the source is re-opened and there have been no changes on the remote
file then the local cached source is used which is not affected by the host
Mike Hockings, M.Eng., P.Eng.
DevOps for Enterprise
IBM Developer for z Systems and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Date: 2019/12/27 20:31
Subject: [EXTERNAL] Re: [WDSCI-L] RDi CL editor and source file record
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>
There is an autoformat setting for CL where I think you specify the
record length, or to honor it. It also has a setting to put all
parameters on separate lines - several options available.
On 12/27/2019 5:55 PM, Elden Fenison wrote:
I am using RDi 126.96.36.199. I don't normally do much with CL. But today I've
done a bunch of editing and I'm seeing something really goofy.
The LPEX editor for CL in RDi seems to have no concept of a source file
record length. It happily lets me go beyond the end of the record. And even
when prompting CL commands will automatically wrap beyond the end of the
record length. Viewing the source member via SEU shows truncation of the
long lines. And the compiles fail for that reason. But when I load the
members up in RDi again... I see the untruncated source.
This is crazy. Any thoughts?
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@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Help support midrange.com by shopping at amazon.com with our affiliate
As an Amazon Associate we earn from qualifying purchases.