Thanks Buck,
Actually turning off the formatter is probably an idea that I will pursue. In this case, I was using F4 and not paying attention to the auto-formatter. Much of my code changes to CL source have been on lines where reformatting would not put beyond the 80 or was not being reformatted. I try not to change much CL code, which is why this is only now becoming an issue after a couple of years of working in RDi.
As to the truncation, that's what was so disturbing. I was merrily editing away, changing every line in the code, allowing it to auto-format so that the command started in column 4 and the total line number reduced, making it much easier to read/recode. Then, I saved it and discovered (after a couple of days of playing and changing) that my code was pooched. Now I get to start all over. Or would have if it wasn't for the fact that my source is salvageable because RDi hasn't cleared the member out of the local copy. I'm happy, but confused. (which is not always a bad thing).
But my formatter only does 80 column if I set it to do 80 column on the line length (for CL) preference. Otherwise, it's set for *RCDLEN and doing it at 100, which appears to be different from what Help says for Line Length for CL.
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Tuesday, September 5, 2017 12:30 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Multiple issues with CL Source editing
On 9/5/2017 11:24 AM, Duane Scott wrote:
First, I'm editing a CL source member in 9.5.1.2 on a V7R1M0. The source file type is PF38-SRC. (I recognize that could be part of the problem, but I hope to deal with that later.) The record length of the file is 92. When editing a member with a type of CLP, the RDi formats lines beyond the 80 character limit. The parser association for CLP is CL. Additionally, as expected, when the member is saved with lines over the 80 character limit, the member is saved with lines truncated at the 80th column. Yet when selecting (again) for editing the full script displays as if it were not truncated. Preferences show that the Line Length for "CL" is set to "*RCDLEN". When changed to "80", the editor properly reformats to the 80th column, but one would think that "*RCDLEN" would reformat to the proper 80th column.
I've had the CL formatter turned off for ages, but I turned it on to test this out. Here's what I did:
Used an existing PF38-SRC file called QCLSRC, 92 recl Used RDi 9.5.1.2 to add a new member BUCKCL PGM
CPYTOIMPF.....150 columns long
ENDPGM
Ctrl-S to save
Receive message 'Line truncation occurred during save.'
With RDi still open, DSPPFM QCLSRC BUCKCL
See that indeed, the long CPYTOIMPF is truncated
F3 back to the command line
In RDi, close the member
In RDi, re-edit the member by clicking on the name in RSE
1) I do NOT see the chopped off end of the CPYTOIMPF line - it /is/ truncated.
2) The formatter seems to work as expected. I paste in the very long line, move the cursor and the formatter makes it all fit into 80 columns.
Are you editing using IBM i Projects?
So, second, how does one clear the cache for the text on a member? I've "cleared cache" a few times, closed RDI, and every time I call up the source, all the data is there. A compile correctly lists errors as if the lines were truncated, but still the line shows as if the source were all there.
Terminology will kill us all yet. By 'text' I'm assuming you mean 'contents of the member'. There isn't a menu option to clear the cache of actual source members, but you can do it yourself:
Close RDi
Using Windows File Explorer, drill down into the workspace:
RemoteSystemsTempFiles
IBM.i.machine.name
QSYS.LIB
YOURLIB.LIB
QCLSRC.FILE
The member will be in there.
Third is the problem of what to set as the record length for the CL Source file. Since the compiler will accept 100 column commands, and the settings on RDi are "*RCDLEN", "80" and "100", one would think that the new record length for CL Source Files should be 112. But record length for CL is not specifically discussed in more recent issues of manuals that I could find. RPG has quite a few discussions of longer settings being available. I'm not sure if we should stick to 80, move to 100, or go beyond. The fact that some of our programmers and operations staff still use SEU is of issue, but I'd like to hear some other viewpoints.
SEU handles 100 just fine.
--
--buck
Try wiki.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@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.
CONFIDENTIALITY NOTICE: This electronic message transmission is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. If you have received this transmission, but are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this e-mail in error, please contact NALC Health Benefit Plan at 703-729-4677 and delete and destroy the original message and all copies.
midrange.com
