× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. June 2008

Re: DBGVIEW(*STMT) as default for ILE RPG compilation

Hi James,

Does DBGVIEW(*STMT) actually serve any useful purpose? It always seems to me that if I do a STRDBG on a program that was compiled with this default value, it brings up the ILE source level debugger, with no source, and no obvious way to do anything.

It's not useful for the debugger. However, it's useful for error messages that occur at runtime. When you get a "divide by zero" error, (or whatever exception), it's able to tell you which statement number that error occurred at.

Obviously, the compiled program object no longer has the same code with the same statements. So how does the error message know which statement from your compile listing the error occurred at? ....DBGVIEW(*STMT), of course.

On a related note, with an ILE program compiled under V4 (with the observability left intact), does DBGVIEW(*NONE) interfere with V6 compatibility?

I wouldn't think so.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.