|
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.
As an Amazon Associate we earn from qualifying purchases.
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.