|
Hello Peter:
When you compile with DBGVEW(*ALL) the debugger has both the *SOURCE and *LISTING views available to be used. For some reason though it will always prefer and choose the *SOURCE view even when the *LISTING view is also available.
When you first start the debugger you can press F15 to switch views, to select the "ILE Listing View".
Or, you could also just always compile with DBGVIEW(*LISTING) -- to force the debugger to use that view.
Also, this scenario suggests to me that the source member identifiedby that second program (PgmB) no longer "matches" what was used when it was compiled. You can verify this by DSPPGM then press Enter twice to get to the "Modules" screen, then "5" next to the module to see what the date/time stamp says for that source member and compare that with the current source member date/time stamp ... e.g., using option "8" in PDM next to the member.
Hope that helps...
Mark S. Waterbury
> On 8/8/2018 4:22 PM, Peter Dow wrote:
This is on v7r3, ptf group SF99876. I'm using STRDBG on PgmA, which calls PgmB.
Both PgmA and PgmB are RPGLE programs that have been compiled with DBGVIEW(*ALL), no optimization.
Using F10 to step through PgmA when it calls PgmB, the debugger switches to PgmB and shows a statement in the middle of the program, not the first statement in the *INZSR subroutine.
I used F15 to switch between all 3 available listings (source, list, copy) and they all show the same statement.
Call stack shows I'm in the correct programs.
The usual problem when I've encountered this before is I'm not in the right program, or the program pointing to the wrong source, or optimization has been done. None of these are the current situation.
--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /
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.