Re: Wrong Statement Number with CL INCLUDEs -- MIDRANGE-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.

Subject: Re: Wrong Statement Number with CL INCLUDEs
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Fri, 6 Apr 2018 16:11:01 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 2018-04-06 2:41 PM, dlclark@xxxxxxxxxxxxxxxx wrote:

Is there some compiler option that says to use the original CL
source line numbers in these situations? It seems like there was such a
compiler option at one time for when RPG used COPY/INCLUDE compiler
directives.

ILE RPG has OPTION(*SRCSTMT) that causes it to use the sequence numbers from the source for the statement numbers instead of just numbering the statements sequentially.

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.