RE: SQL exception diagnostics -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Thanks, I'll check it out.

-----Original Message-----
From: Barbara Morris [mailto:bmorris@xxxxxxxxxx]
Sent: Tuesday, January 14, 2020 12:23 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: SQL exception diagnostics

On 2020-01-10 9:26 a.m., Rob Berendt wrote:

I seem to remember that the trick of using STRDBG to get further information from STRSQL was rather deprecated for getting it from performance information. Not that I have further details but it may be a train of thought to pursue.

As far as I can tell, this post didn't go through on 2020-01-10 ...

I don't know the exact relationship between the joblog and GET DIAGNOSTICS, but there's a QAQQINI option MESSAGES_DEBUG that might help.

Around the middle of this page:
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzajq/qryopt.htm

"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.
*DEFAULT - The default is set to *NO.
*NO - No debug messages are to be displayed.
*YES - Issue all debug messages that are generated for STRDBG."

--
Barbara

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.