|
I my vendor's infinite wisdom, there is not subroutines in their code, it is all subprocedures. I am trying to make a modification and need to run this program in debug (strdbg) to figure what it is doing. Short of putting a break point in every single subprocedure, is there a way to step into the subprocedure. Would using WDSc work better for this? This is a batch only program. I have never used the debugger in WDSc. How would I set this up if it would work better?
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.