× 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.



I have a problem with the debugger displaying the incorrect source in the
debug editor. This usually means I have not updated the PGM or SRVPGM, which
is expected, so I update the object. Occasionally the object and module are
in sync when this occurs and if I close WDSC and restart the correct source
is displayed in the debugger. This is a pain, and I assume that there is a
cache somewhere that gets cleared when WDSC is closed. If anyone can tell me
what/where to clear this cache I would appreciate it. But this is not my
major problem, twice now I have had the debug editor "loose" a line of code,
closing WDSC and even shutting down my PC has not helped. By loose I mean
that a line of code does not show up in the debug editor, yet the line
number sequence does not skip the missing line. This throws off the rest of
the source being debugged. When I debug the same PGM on a green screen
(strdbg), the source is correct, so it is not a problem with the object or,
it seems, a cache. 
Anyone have any ideas?

Duane Christen   



NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.  Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.