Re: RDi 7.5 Problem with parsing CMD members -- WDSCI-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Brian:

Remote Systems -> Remote Systems LPEX Editor -> i5/OS Parsers ->CL
o auto-format includes a line-length setting

Changing the line-length for *RLEN to 80 seems to have fixed the
problem.

Thanks!

Bill Blalock

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Brian Johnson
Sent: Tuesday, March 03, 2009 4:48 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] RDi 7.5 Problem with parsing CMD members

On Tue, Mar 3, 2009 at 1:20 PM, Blalock, Bill <Bill.Blalock@xxxxxxxx>
wrote:

The editor treats the source member as being indefinitely long. When

line is changed what is back to the display is often over 80

characters.

When the member is saved back to QCMDSRC anything over column 80 is
lost.

I find two places with line length specified in RDi 7.1. Maybe these
settings are there in 7.5 too:

LPEX Editor -> Save

o Max line length (0=use system limit... I assume source file data
length)

Remote Systems -> Remote Systems LPEX Editor -> i5/OS Parsers ->CL

o auto-format includes a line-length setting

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.