Re: Preventing SQL debug messages -- MIDRANGE-L

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

On 28-Jul-2010 12:03, Dennis Lovelady wrote:

I have a particularly difficult problem to solve in an
SQL-based procedure. I would like to be able to set a conditional
breakpoint and trace through the program when a specific
condition occurs. The issue is that that condition occurs after
hundreds of thousands of SQL statement have been executed; and in
debug mode each of them writes to the job log <<SNIP>>
I am not interested in the SQL debug messages, and there may be
things in the joblog that might help identify the real problem.
Can I avoid SQL debug messages (at V5R3) in a debug session?

Does the QAQQINI option MESSAGES_DEBUG being set to *NO, override the effect of STRDBG being active? The documentation is not very helpful in explaining, but seems to suggest that it would; the value *YES seems clear enough for the reverse effect, as discussed in a past conversation.
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzajq/qryopt.htm
http://archive.midrange.com/midrange-l/201005/msg00422.html

Regards, Chuck

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.