Re: Reason(s) for SQL generating debugging messages -- 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.

Is an INI file being used? There is an option in QAQQINI, MESSAGES_DEBUG, that effects the same as STRDBG. A CHGQRYA to name a query options library, or by the odd choice of system-wide default for QRYOPTLIB(QUSRSYS), per existence of that file in QUSRSYS. I am not sure if the query options for a job will be /carried/ into a submitted job, or if only activated either as the default from QUSRSYS or an explicit CHGQRYA.

Regards, Chuck

Dennis Lovelady wrote:

What would be the reason that an embedded SQL (RPG ILE) program on V5R3 would be generating SQL debug messages when it's not
being debugged?

I'm trying to determine why the joblogs are so large for a number
of programs, most of which involve imbedded SQL, and one factor that I'm seeing is that there are significant numbers of CPI434B,
CPI4339,CPI434A, CPI432D (et cetera) in the job log. I am
accustomed to seeing these when debugging an RPG SQL module, but
not when the program is run without debug, and certainly not in a
batch environment.

What might we have done to cause this, and how might we stop it at V5R3?

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.