×
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.
Apologies if I am repeating something that was noted earlier in the thread
that I didn't see.
I think I saw somewhere that the debug source in the program does not
effect performance of the program, but like Vern says, it just makes the
program object bigger. For some reason, I am thinking that the
observability information is not normally loaded at execution time, but
only if needed (such as for a dump or debug) but can not provide a
reference for this.
While I use the DEBUGVIEW(*ALL) so WDSC debugger can always find the
source, I would not remove observability unless it is a product you are
sending out to other people and you do not want them to be able to see your
code. For use internally, I don't think the program object size matters
that much and I believe that you want to keep the observability for
possible future re-translations and being able to see the variables in any
possible program dumps.
At 06:29 AM 4/2/2005, you wrote:
I like using DBGVIEW(*ALL) when I create the program. Yes, this makes the
program object larger, but when your testing is done, use CHGPGM to remove
observability - this will remove the debug information from the program object.
Vern
Dave Murvin
DRM Enterprises, Inc.
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
