Re: CL Source truncation issue

Thanks Phil. That was the answer I was hoping to see.
--Michael

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of ssc1478
Sent: Thursday, November 05, 2009 4:43 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] CL Source truncation issue

On Thu, Nov 5, 2009 at 4:18 PM, Koester, Michael <mkoester@xxxxxxxxxxxxx> wrote:

My preferred MO is to have a sourcefile of 112 record length so that I
can have all the RPG, DDS, and CL members for a task in one place.  Our
production cl source file is 92, so when the development copy gets moved
to production, I run the danger of losing essential stuff at the right
end of the source record.  We discover this when the production source
fails to compile, and we've also had fun when it does ompile, but we
have production behaviors that weren't as pretty as the test behaviors.
I've since changed to my not-so-preferend MO (having a separate
source-file for CL development).



We're using WDSC V 7.0.0.8 Interim Fix 001 and i/OS  V5R4M0



I saw that this was issue mentioned in the archives, but my question is:
Does RDi have a better approach for this?  Like maybe a CL parser
preference that restricts CL source to 92?

Yes it does in RDi:
Remote Systems > Remote Systems LPEX Editor > IBM i Parsers > CL

You can set the line length there. We set ours to 80. The default is *RCDLEN

Weird problem - only happens sometimes, and only to some people.

Phil