RE: Preventing SQL debug messages

Thank you for your message, Chuck.

I appreciate the thought, and this is probably the right answer. But I
cannot determine since I don't have authority to create a duplicate of
QSYS/QAQQINI. (sigh.) Go figure. I'm not sure who came up with this level
of protection or why, but the powers that be here seem to be afraid the
world will end if we're allowed a peek at that file.

I will make do with what I have.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"To invent, you need a good imagination and a pile of junk."
-- Thomas Edison

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/qryop
t.htm
http://archive.midrange.com/midrange-l/201005/msg00422.html

Regards, Chuck
--
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.