Re: CL Source truncation issue

[Mike <koldark@xxxxxxxxx>]

Unfortunately (to the best of my knowledge, this can't be set as a permanent
change. Put the following on the command line of the editor "set
save.textLimit 92"

--
Mike Wills
http://mikewills.info
P: (507) 933-0880 | Skype: koldark


On Thu, Nov 5, 2009 at 3: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?
>
>
>
> PS: Replies to this post not received before 6 PM EST won't be seen by
> me until Monday.
>
>
>
> --Michael Koester
>
> --
> This is the Websphere Development Studio Client for 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.