Re: Multiple issues with CL Source editing

There are actually two caches under Remote Systems. I just put "cache" in the "type filter text" box.



-----Original Message-----
From: Duane Scott [mailto:dscott@xxxxxxxxxxx]
Sent: Tuesday, September 05, 2017 10:24 AM
To: WDSCI-L@xxxxxxxxxxxx
Subject: [WDSCI-L] Multiple issues with CL Source editing

I'm having some issues that I'm not sure are answered in any postings that I can discover by searching the archives or Google.

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.

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.

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.



Duane

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.