× 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. MIDRANGE-L
  3. October 2005

RE: debug not working with CLP??

Not exactly - you have to compile CLPs with OPTION(*SRCDBG) or OPTION(*LSTDBG) to debug in either debugger. STRDBG will handle CLPs if you use OPMSRC(*YES)
I prefer to work with one debugger. STRISDB has some nice features that STRDBG does not have, but it's not worth it to remember conflicting sets of function keys.
In addition, I prefer to use CLLE exclusively when I have a choice, and to convert if possible. Performance has been demonstrated to be better just by changing to CLLE, markedly so. There's a KB article somewhere at IBM on this. Yes, there are a couple things to watch for, but they have been documented in the ILE manuals and programming language manuals. 

Personal choices. YMMV
Vern

At 12:25 PM 10/3/2005, you wrote:
To debug CLP you need to compile with: Source listing options . . . . . > *SRCDBG 
Then use strisdb
To debug CLLE you need to compile with: Debugging view . . . . . . . . . *STMT 
Then use strdbg

HTH
Kim

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.