|
----- Original Message -----
From: CRPence <crp@xxxxxxxxxxxxxxxxxxxx>
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Relating a statement number to a source line number
Date: Fri, 07 Dec 2007 13:04:37 -0600
What is seen in the stack for an ILE program [on "Display Call Stack"
panel], is not the MI instructions. The OPM IRP listing generation did
allow seeing the actual MI instruction numbers in the listing, and those
were visible in the /Instruction/ column of the program stack display.
ILE programs have only a /Statement/ number that is visible on that
screen. An ILE program compiles into W-code, not MI, and there is no
compile option to give that information.
What is shown for WRKJOB OPTION(*PGMSTK) OUTPUT(*PRINT) when the
program is /hanging up/ ?
Regards, Chuck
--
All comments provided "as is" with no warranties of any kind
whatsoever and may not represent positions, strategies, nor views of my
employer
Albert York wrote:
I'm sorry. I meant the generated MI program listing which contains
the statement numbers (not the source line numbers) shown in the
program stack.
<<SNIP>>
Albert York wrote:
<<SNIP>>
I am having trouble with an RPGLE program hanging up. When I
look at the job stack it shows me a statement number. How do I
relate that back to the source? With RPG you could generate a
listing of the generated program. Is there a way to do that
with RPGLE?
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-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.