|
Yes, I do that and it doesn't hit subProcB but goes back to my on-error
statement and promptly exits gracefully. I am going to put these on a test
program to see what happens.
On Thu, Apr 10, 2008 at 8:08 AM, Adam Glauser <adamglauser@xxxxxxxxxxxx>
wrote:
Mike wrote:
I am working through a problem right now. I have a program that callsa
subprocedure, that calls a second subprocedure. Both of thesesubprocedures
have worked in the past and I have not made changes to them. I justPoint
recompiled everything just to be sure. I run it in WDSc Service Entry
debugger and it appears that the call to the second subprocedure bombsout.
Did you try stepping through both subprocedures to see where the problem
lies? If you have:
pgmA --calls--> subProcA --calls--> subProcB
You can set your SEP on pgmA, then on the suspect call to subProcA
choose 'Step Into' instead of 'Step over'.
--
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.
--
Mike Wills
Check out my music show at http://thenextgenerationofradio.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.