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



There were many more apparently problematic messages issued before the SQL0901 was listed. Most notably a MCH1210 was the first message preceding many instances of "File not found" where the replacement text values are very suspect. FWiW a copy\paste from an interactive request to DSPJOBLOG OUTPUT(*) lacks significant relevant /context/ for the situation [including the V#R#M# which appears in the headings]. A DSPJOBLOG OUTPUT(*PRINT) for a job defined with LOG(4 0 *SECLVL) provides the context that is missing from the non-spooled version.

FWiW the SQL0901 to SQL is the effective equivalent of CPF9999 to the OS; i.e. they are both a /generic/ "function check" condition to explain a prior unmonitored\unhandled error condition. It is always the prior condition(s) that lead to the generic failure that are relevant; although whether the relevant details are available in prior messaging, is not assured.

In this case however, at least the CPF4204 is shown in the joblog... but its details and context are missing. As well as all of the other messages preceding that /generic/ query failure... which, like the other aforementioned /generic/ failures, *preceding* conditions and thus possibly preceding *messages* are also likely relevant details to further describe the problem. But again, the /context/ for the errors is important, and only the *spooled* joblog [with LOG(4 0 *SECLVL) provides that information, both concisely and in its entirety.

Regards, Chuck

On 06 May 2013 06:46, Mike Wills wrote:
When I list tables (the plus sign on the left side to get a list of
tables) to add a table to journaling though the Start/End Journaling
dialog box I get the following error:

SQL0901 SQL system error.

<<SNIP>>

Looking at the job log, I see:

=========
Job 065563/QUSER/QZDASOINIT started on 05/06/13 at 06:58:38 in subsystem
QUSRWRK in QSYS. Job entered system on 05/06/13 at 06:58:38.
User XXXXXXXXX from client 192.168.XXX.XXX connected to server.
The following special registers have been set: CLIENT_APPLNAME: CWBUNNAV
Receiver value too small to hold result.
File HVR0005F in library ORMAT0001 not found.
File  in library  not found.
<<SNIP three identical to above>>
File V in library  not found.
File  in library  not found.
<<SNIP fifteen identical to above>>
Internal failure occurred in query processor.
SQL system error.
Ownership of object GPTFLST in QTEMP type *USRSPC changed.
Output file QAUGDBJOBN created in library QTEMP.
Member QAUGDBJOBN added to output file QAUGDBJOBN in library QTEMP.
=========

This happens on multiple computers.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.