× 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.



On 17 Jun 2013 15:48, Alan Campin wrote:
<<SNIP>> effectively locked out of using V7R1 features unless we turn
off syntax checking. A big reduction in productivity.

Anybody know of any efforts to get checking turned back on in V7R1?

I have found that the line command X=Exclude [or variants] enable me to effectively ignore errors until either I change [e.g. to TXT, or overwrite the R in RPGLE to x] and then reset the source type or exit editing; then using the S=Show variants to get the line(s) back, along with their syntax error.

When exiting without having effected the source-type change, always being sure to change the "Return to editing" to "N"=No in order to override that error-correct-assist feature, /knowing/ that I expect those syntax errors and that I am purposely choosing to ignore them. Unfortunately, unless something has changed, there is no CHANGE nor SET invocation from the Source Entry Utility "Command line" to reset the Source Type of the member being edited; only using F13="Change Session Defaults".

I became very proficient in doing that navigation to change the source type, from having often coded records after a //DATA command within CL a source type, but wherein those data records were non-CL source and thus would be flagged with syntax errors. Effectively, coding multiple source types within one source member.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.