CL Parsing/Wrapping

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