|
Vern:
Does the one part per line format so commands list the Parms with
continuation “+”. I’ve been missing that. If so I’m going to get that
done this afternoon.
Did not know that was in there. Fabulous!
On Sun, Dec 29, 2019 at 10:19 AM Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:
Hi Marco
When I enter source in CLLE and go past the 80th column, I get a bell
and a message saying I have done that, and that text will be truncated
when saved.
So the editor knows about length.
I also find that when I move the cursor off the line, it all gets
formatted within 80 columns.
I checked Preferences - I'm using 9.6.0.6, as well. I typed CL in the
text box, and one item of interest was this one -
Remote Systems-->Remote Systems LPEX Editor-->IBM i Parsers-->CL
In there is a group of settings called "Automatic formatting", which is
checked.
And in that group is "Line Length" - it has options of 80, 120, and
*RCDLEN. This setting is available even when "Automatic formatting" is
not checked. If you hover over it, you get help text saying something
about this is the maximum length the CL formatter should use.
I turned off "Automatic formatting", and I still get the message and the
audible signal, but when I click on another line, the text stays where
it is. If, on the other hand, I check "Automatic formatting" again, then
that text was adjusted so that it would fit in the line length.
There is another item I have checked, "One parameter per line" - that
probably has nothing to do with this, but I mention it, as I like the
look of it.
On 12/29/2019 8:56 AM, Marco Facchinetti wrote:
Hi Elden, same problem and I didn't find a way to fix it in RDI.even
My solution was:
- make a list with all CLLE Source files
- Rename all of them
- Created new src files with e record length of 132 (120 + 12)
- copy all members in the new one
and now it's working.
HTH
--
Marco Facchinetti
Mr S.r.l.
Tel. 035 962885
Cel. 393 9620498
Skype: facchinettimarco
Il giorno sab 28 dic 2019 alle ore 00:55 Elden Fenison <
Elden.Fenison@xxxxxxxxxxxxxxxxx> ha scritto:
I am using RDi 9.6.0.6. 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
--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,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.