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



Hopefully I am just not seeing something obvious here...

I know what the SQL0811 error is, and a handful of ways to either fix it or trace it back to a database error (and then fix the program dropping dupes in the table).

What I do not know is an easy way to tell which Select statement caused the error in the first place. Unlike normal errors that show you the program name and line number, the SQL errors always seem to reference a SQL program - QSQRUN2. With all of the service programs and SQL we have in use, it can be a nightmare tracking down and testing every possible SQL to see if it is the offender. Sometimes I get lucky and there is another job log message nearby that does reference the correct program, but not always.

As long as I am complaining, I am also annoyed when I see job log messages for 'Subfile record not found'. I am actually doubly-annoyed. First, because some programmers think it is perfectly ok to just chain your way through a subfile until you hit an invalid RRN -- how hard is it to keep track of the last RRN anyhow?? Second, the error is another one that does not show you your program name - just QSFGET.

I like my job logs to include one of two things: Messages I write to the job log intentionally, or real error messages (not that they ever happen).

Anyhow, I got off topic. Am I missing some way to see what program actually called the SQL that caused the error?

Thanks,
Dave

====
www.openDave.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.