RE: SQL Filling Job Log -- MIDRANGE-L

Kurt.
You are right on target. From *memory* I think *NO for that setting should suppress . . . HTH

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Anderson, Kurt
Sent: Friday, June 07, 2013 10:45 AM
To: Midrange Systems Technical Discussion
Subject: RE: SQL Filling Job Log

Gary,

I don't think I'm seeing what you're seeing. *YES seems to say that it -will- issue job log messages.

This is from the IBM site on MESSAGES_DEBUG:
MESSAGES_DEBUG
Specifies whether Query Optimizer debug messages are displayed to the job log. These messages are regularly issued when the job is in debug mode.
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Frzajq%2Frzajqqaqqiniproc.htm
*Yes says "Issue all debug messages that are generated for STRDBG."

I'm trying to do the opposite.

-Kurt

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Friday, June 07, 2013 11:42 AM
To: Midrange Systems Technical Discussion
Subject: RE: SQL Filling Job Log

Kurt,
Sorry for your frustration, but I do believe you can suppress these messages.

Maybe re-read this section (noting use of "*YES") from the site you referenced:

SECTION
Viewing debug messages using QAQQINI table:

You can also set the QRYOPTLIB parameter on the Change Query Attributes (CHGQRYA) command to a user schema where the QAQQINI table exists. Set the parameter on the QAQQINI table to MESSAGES_DEBUG, and set the value to *YES. This option places query optimization information in the job log. Changes made to the QAQQINI table are effective immediately and affect all users and queries that use this table. Once you change the MESSAGES_DEBUG parameter, all queries that use this QAQQINI table write debug messages to their respective job logs. Pressing F10 from the command Entry panel displays the message text. To see the second-level text, press F1 (Help). The second-level text sometimes offers hints for improving query performance.
/SECTION

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Anderson, Kurt
Sent: Friday, June 07, 2013 10:27 AM
To: 'Midrange Systems Technical Discussion'
Subject: SQL Filling Job Log

I'm working on a project where I'm introducing more embedded SQL into the heart of our system. When we test our programs that may write out millions of records, we run them with STRDBG on so we don't accidentally update production. The unfortunate side effect is that the test runs a lot longer than it needs to because it's filling up the job log with SQL messages.

A message in the archives from Gary Thompson suggested using QAQQINI to override MESSAGES_DEBUG to *No. Tried that to no effect. Turns out *Default = *No and the purpose of MESSAGES_DEBUG is to obtain SQL information in the job log 'as if' STRDBG was on.
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Frzajq%2Frzajqqaqqiniproc.htm

Does anyone have any recommendations for a way to suppress these messages?

I'm at IBM i 7.1

Thanks,

Kurt Anderson
Sr. Programmer/Analyst at CustomCall Data Systems
[Description: Description: Description: cid:image001.jpg@01CD0CDD.2AC4AAD0]
phone: +1 608 274 3009
web: www.customcall.com<http://www.customcall.com/> | email: kanderson@xxxxxxxxxxxx<mailto:kanderson@xxxxxxxxxxxx>

A Division of Enghouse Systems Ltd.<http://www.enghouse.com/> (TSX:ESL)

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

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