Re: CL formating in LPEX editor

["Jim Essinger" <dilbernator@xxxxxxxxx>]

Brian,

Thanks for the response.  The problem happens with the other developer, in a
particular source member with his instance of WDSc.  I open the SAME source
member in my instance WDSc, and it formats correctly.  So the record length
is the same.  It looks like the option posted as "set save.textLimit 80"
might be headed down the correct path.  We will give that one a try.

Any other thoughts?

Jim

On 6/28/07, Brian Johnson <brian.johnson.mn@xxxxxxxxx> wrote:
> First the obvious question: do you all have the identical selections for
> CL
> formatting?
>
> Do the source files have the same length for field SRCDTA? I've always
> assumed the line length limit is derived from the length of field SRCDTA
> in
> the source file?  This is my favorite feature of the CL formatter.  It
> uses
> the full length of SRCDTA instead of the artificial wrap at 80 like SEU.
>
>
> On 6/28/07, Jim Essinger <dilbernator@xxxxxxxxx> wrote:
> >
> > Listers,
> >
> > I have 2 developers who have V7.0.0 Build id: 20070202_0030 installed,
> > which
> > is the same as mine. One has the latest fixpack and the other does
> not.  I
> > have the latest fixpack installed on mine.  They are having problems
> with
> > the auto format with commands such as CPYFRMIMPF where the editor will
> NOT
> > wrap the command before the 80 character cut off point.  I think I had
> > this
> > problem at one time, but an upgrade somewhere along the line  seems to
> > have
> > fixed it for me.  When I bring up the same source member in my instance
> of
> > WDSc and change the problem line, it formats just great for me.  It will
> > not
> > format for the other 2 developers, no matter what they do. The command
> > looks
> > like this;
> >
> > CPYFRMIMPF FROMSTMF(&PATH) TOFILE(CONSWSF) MBROPT(*REPLACE) +
> >           RCDDLM(*CRLF) STRDLM(*NONE) FLDDLM('|') +
> >           DATFMT(*YYMD) DATSEP('/') ERRRCDOPT(*REPLACE)
> > RPLNULLVAL(*FLDDFT)
> >
> > Any one run into this before and maybe have a fix?  If not, any other
> > ideas?
> >
> >
> > Thanks!
> >
> >
> > Jim Essinger
> > Senior Programmer/Analyst
> > GCO Servicing Corp.
> >
> > 208.452.9475 Direct
> > --
> > 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.
> >
>
>
>
> --
> Brian Johnson
> brian.johnson.mn@xxxxxxxxx
> --
> 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.