|
> I think this is misleading, because the source debugger does not show any > source or listing for programs created with DBGVIEW(*STMT). It is a small > step better than *NONE in that it can still be debugged. *STMT means "statement". The only thing you can view in debug are the statement numbers. This is what we had in the old days, before the debugger displayed the source on the screen for you... back when you had to refer to the compile listing to see where you were in the program.. > > I'm sticking with DBGVIEW(*ALL). > I started out using DBGVIEW(*ALL) but ran into some errors where the compiler would say "Internal Error" and generate pages and pages of memory dumps and only really lovely things. It didn't do that all the time, but occasionally it would, depending on the code I wrote. Switching to DBGVIEW(*LIST) solved the problem for me -- so that's what I always use now. I'm curious why you'd want the *COPY listing view included when you've got the *LIST view included as well? Not that *COPY is a bad thing, it just seems superfluous when you've got *LIST. At any rate, the problem I had was many years ago, and was probably fixed long, long ago.... Now I just use *LIST because it's been my habit...
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.