|
>From the names of the subprocedures, it looks like you are using embedded SQL. > If so, that would explain why the weird behavior. Place break points on RPG >statements is the simplest solution. Contact me off line for further >information. Marvin ------------------------------ message: 4 date: Mon, 16 Jan 2006 14:53:35 -0600 from: Mike Wills <koldark@xxxxxxxxx> subject: Debugging Problem I have a weird problem. I am not sure how to even really describe this. I have a program with 33 internal subprocedures. I call OpenNIBTCursor. The debugger hits line one of the procedure, then hits line 1 of OpenStockholdersEquityCursor, which is MANY lines down in the code. As far as I can tell, I have everything setup correctly. Are there any bugs like this? We are on V5R3 with the latest CUME (just installed last night). This happens with both STRDBG and the WDSc debugger. -- Mike Wills koldark@xxxxxxxxx http://mikewills.name Want Gmail? Email koldark+gmail@xxxxxxxxx to get on my waiting list. "There are 10 types of people in the world: those who understand binary, and those who don't." -Unknown
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.
midrange.com
