Re: Another CL Parser question

Violaine,

Please excuse the delayed response to this posting, but I tried your
recommendations below and it all works fine except step 3.  When you
type a blank on most lines it nicely reformats the line(s), but when you
type the blank on an ENDDO line it repositions the cursor under the
ENDDO keyword.  This is a nuisance when you are stepping through a
source member and suddenly you have to stop and reposition the cursor.
As far as I can tell, ENDDO is the only keyword that does this.  At
least for all those I use.

It's not a big problem but maybe you can fix it in an upcoming patch?

Thanks,
Mark

Mark Larson | Sr. Architect | ERP LX Architecture | Infor | Office:
312-474-7501 | mark.larson@xxxxxxxxx


-----Original Message-----
From: wdsci-l-bounces+mark.larson=infor.com@xxxxxxxxxxxx
[mailto:wdsci-l-bounces+mark.larson=infor.com@xxxxxxxxxxxx] On Behalf Of
Violaine Batthish
Sent: Thursday, December 28, 2006 9:20 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Another CL Parser question

Hi Dave,

This request is on our list of requirements.

I did do some quick testing, and you can try the following trick:
1) after opening your member, press Esc to go to the LPEX command line
2) Enter the following LPEX command (which will set the record length
for
the currently open member/file  to 12 for sequence numbers + 80 for the
text area):
set save.textLimit 92
Note that this will cause the message about lines being truncated to be
issued if you have text that exceeds 80 characters.
3)You can then trigger formatting on each statement by typing a blank on
the line.

hope that helps!

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab


wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/27/2006 06:48:16 PM:

I like to keep all my source members in one file (DAVESRC for
example) which I define with a maximum record length of 112
characters.  When I am editing CL programs and have the parser set to
not use the One Parameter per line, the parser allows (forces) lines
to extend to the maximum record length (100 in the case of DAVESRC).

While this is okay with me for my source files,  but when working for
a client using these same 112 length source files, the CL source will
be truncated when I transfer my 112 CL source file to their standard
92 character QCLSRC.

Is there a CL parser or editor preference to limit how much of the
source file line can be used?  In my example, when I am using a 112
character source file, I would like the editor and/or the parser to
"know" that I only want the CL source lines to be a maximum of 80
characters.   Currently the editor does tell me that Truncation will
occur when I exceed 100 characters in my CL source.

Thanks again.

Dave Murvin
DRM Enterprises, Inc.