Re: RDi 7.5 Problem with parsing CMD members

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Bill

I'm not at 7.5. yet, so this might not apply - hope it does.

The editor should tell you, near the bottom, that lines have exceeded 
the source record length - do you see that? Also, have you turned off 
auto-formatting? Not sure if that will help to turn it on.

Now you can force the length you want by clicking in the command line 
area below the editor, or pressing Esc - then type

set save.textLimit 92

and press Enter - this forces an 80-character source data length.

HTH
Vern

Blalock, Bill wrote:
> Hi all:
>
>  
>
> This is for RDi 7.5.
>
>  
>
> I am having problems with LPEX when editing CMD members.
>
>  
>
> The editor treats the source member as being indefinitely long.  When a
> 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.
>
>  
>
> Does anyone have any ideas?
>
>  
>
> QCMDSRC was created with CRTPFSRC with a length of 92.  It has 3 fields,
> 6, 6 and 80.  SEU is fine with it.
>
>  
>
> The parser associated with the type CMD is cl.
>
>  
>
> The only way I can use LPEX with a CMD member is to remove the parsing
> definition so LPEX doesn't try to help me.
>
>  
>
> Any ideas?
>
>  
>
> Thanks
>
>  
>
> _____________
>
> The information contained in this message is proprietary and/or confidential. If you are not the 
> intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, 
> distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, 
> please be aware that any message addressed to our domain is subject to archiving and review by 
> persons other than the intended recipient. Thank you.
> _____________
>