Re: Preventing SQL debug messages

[CRPence <CRPbottle@xxxxxxxxx>]

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