Re: Preventing SQL debug messages

Thanks, Luis:

For security reasons this particular client allows extremely limited access
to the system. For me, as a consultant and this, their production system,
I
have green-screen access and data transfer. Besides, this is not an SQL
problem that I'm chasing; it's a problem in a procedure that happens do to
a
lot of SQL. I haven't tried the tool. Sounds interesting but I don't
think
it applies here, and I don't think I could use it in this case if it did.
But I do appreciate the link and the opportunity to learn about a tool that
may help me elsewhere!

Regards,

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"When I was crossing the border into Canada, they asked if I had any
firearms with me. I said, `Well, what do you need?'"
-- Steven Wright

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Luis Rodriguez
Sent: Wednesday, July 28, 2010 3:53 PM
To: Midrange Systems Technical Discussion
Subject: Re: Preventing SQL debug messages

Dennis,

Have you tried the SQL Graphical debugger? It won't avoid the
generation of
debug messages, but it will allow you to set conditional breakpoints
and
such.

Check this URL,

https://www-
304.ibm.com/partnerworld/wps/servlet/ContentHandler/partnerworld/wps/se
rvlet/ContentHandler?contentId=cntkv8_XCRndVf4MDAD&localeName=en

Tiny URL:
*http://tinyurl.com/22rqyj5*


HTH,

Luis

Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries
--



On Wed, Jul 28, 2010 at 2:33 PM, Dennis Lovelady
<iseries@xxxxxxxxxxxx>wrote:

Hi, Folks:



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,

eventually

overflowing maximum joblog size.



I realize I can set the joblog to wrap, but in this instance 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?



Dennis E. Lovelady
AIM/Skype: delovelady MSN: fastcounter@xxxxxxxxxxxx
<http://www.linkedin.com/in/dennislovelady>
www.linkedin.com/in/dennislovelady --



Live and learn.
(But not in that order.)



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

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