|
I really like when using the editor for CL that you can type in a long line and then the command just gets auto formatted to fit when you are done. This is nice when adding parameters to a command or building up a long message with concatenation. I suppose Vern might have been expecting some kind of similar auto-formatting for his C code. I haven't tried free-format RPG in LPEX but I would expect the same there. Mark To: wdsci-l@xxxxxxxxxxxx cc: bcc: Subject: [WDSCI-L] Re: Line truncation message - how to avoid disaster adrian <stori@xxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 09/20/2003 05:07 PM AST Please respond to Websphere Development Studio Client for iSeries <font size=-1></font> When a record length is in effect, LPEX will issue an error message the moment you exceed the limit while editing. That's the best time to correct this. When saving, the truncation message will again be issued, with the cursor positioned on the first record in the document that exceeded the limit and was truncated. You can correct the line in question, and save again. No actual disaster. Unlike CODE, LPEX does allow you to go over the record length limit while editing (it just issues the error message), so that you can edit without problems (inserts may be a problem in CODE when a record limit is in effect, even though you plan the text to only temporarily go over the limit and do corresponding deletes afterwards...). _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.