Re: CL Parsing/Wrapping

Addendum...I did some experimenting to see at what character position it would cause the line to be broken into two...it was in character position 69.

Ken

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Tarr, Kenneth
Sent: Friday, November 20, 2009 12:41 PM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] CL Parsing/Wrapping

Hmmm...this might answer it...if you go into Window, Preferences, Remote Systems, Remote Systems LPEX Editor, iSeries Parsers, CL...there is an option entitled User defined tabs. Then right below it is a label named General which features a bar above the open field that only goes out to position 80. No matter what I change the Maximum line length value to (I tried 92, even 132 for fun), the length of this bar doesn't change. I'm thinking WDSC is locked into 80 characters before it will break up the line automatically, and the only way to do it is manually. I can use the keyboard shortcuts to merge or split the line and work it that way or just manually type it in.

Unless someone else knows how to circumvent this, whether there is a setting out there I can't find, or something in a file that could be changed, I will simply work around the limitation as needed.

Thanks for your help.

Ken

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Kurt Anderson
Sent: Friday, November 20, 2009 11:55 AM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] CL Parsing/Wrapping

Our CL source is 80 long, and it also wraps quite a ways before position 80. (Possibly 60). I've generally found it to be annoying and will manually reformat it.

Thanks for asking the question, Ken - I hope there's an answer.

-Kurt Anderson

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Tarr, Kenneth
Sent: Friday, November 20, 2009 11:28 AM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] CL Parsing/Wrapping

Vern:

Actually I get the message after position 100...I see where the value is set (in this case, to 112). It seems to be breaking around position 80 or sooner. This lead me to believe there was a separate setting for this. This isn't a big issue but it has me puzzled.

Ken

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Friday, November 20, 2009 11:16 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] CL Parsing/Wrapping

Ken

What happens when you type past position 80? Do you get a message about
"One of more lines exceed the text limit"? If so, the WDSC is assuming
the standard length for CL source or 92. In that case, there is a
command you can use to change it in that editor window - not
permanently, if I remember correctly.

While your cursor is in the editor view, press Escape. The cursor will
go to that command line at the bottom. Enter the following there -

set save.textLimit 112

Now it should format things according to your 100-character limit.

HTH
Vern

Tarr, Kenneth wrote:

I am currently working on a new CL program that will accept a line length of up to 100 characters. When I enter a command with parameters, the LPEX Editor splits the line as it should with a + sign at the end for each continuance. It seems like it is splitting the line early though; I've had several examples where the last parameter could easily fit on the same line. I'm trying to locate the setting to change this in the Windows, Preferences section but can't locate it. I also tried looking up information online to no avail. Can someone direct me to where this setting is, or to the file where I can manually change it? Or is this one of those "I have to learn to live with it" scenarios? (We are looking to go to RDi 7.5 next year.)

Also the parser just LOVES inserting a bunch of single quotes around some stuff in a statement where I am concatenating several items together, including the single quote itself (which I enter as ''' to get that). In one instance it surrounded a literal and had nine single quotes to the right of it. It only needed four (three for a single quote reference, plus one to actually enclose the literal in quotes). What is causing this odd behavior? (It also makes the first issue above more noticeable.)

Using WDSC V7.0.0.8.

Ken Tarr
Associated Banc Corp
Green Bay Service Center, Mail Stop 7055
2870 Holmgren Way
Green Bay, WI 54304
www.associatedbank.com




*********************** NOTICE***********************

This e-mail and attachment(s) may contain information that is
privileged, confidential, and/or exempt from disclosure under
applicable law. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination,
distribution, or copy of this message is strictly prohibited. If
received in error, please notify the sender immediately and
delete/destroy the message and any copies thereof. Although
Associated Banc-Corp and/or its affiliates (collectively
"Associated") attempt to prevent the passage of viruses via e-mail
and attachments thereto, Associated does not guarantee that either
are virus-free, and accepts no liability for any damage sustained
as a result of any such viruses.

Any federal tax advice contained in this communication (including
any attachments) is not intended or written to be used or referred
to in the promoting, marketing, or recommending of any entity,
investment plan or agreement, nor is such advice intended or written
to be used, and cannot be used, by a taxpayer for the purpose of
avoiding penalties under the Internal Revenue Tax Code