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



On 05-Jul-2017 07:40 -0600, Steinmetz, Paul wrote:
I run the below SQL to find largest spoolfiles.

Works fine on Production LPAR.
Fails on R&D LPAR with below error.
Any thoughts from the group on what to check or how to resolve?

SELECT OUTQ, SPOOLNAME, size, pages, job_name, created
FROM QSYS2.OUTPUT_QUEUE_ENTRIES
ORDER BY SIZE DESC
FETCH FIRST 100 ROWS ONLY

File QASPOUTQ in library QSPL0002 not found or inline data file
missing.

msgCPF4101 RC01 RC1 lib QSPL0002 not found
F/?? T/?? <-- missing context from what was given

User-defined function error on member OUTQ_INFO.

msgCPF503E EC1 RC1 SQLSTATE 58004 [sqlcode -901 aka sql0901, IIRC]
service program QDBSSUDF external name QSQWRKOUTQ
F/?? T/?? <-- missing context from what was given

Cancel reply received for message CPF503E.
[…]


Per the library name, the problem/difficulty is related to the iASP number 2. And I presume the original error, i.e. the reference to the missing system [¿copy of the model?] database file name QASPOUTQ [LF over PF QASPLINFO] is in/with the system Procedure Name QSQWRKOUTQ of the Service Program QDBSSUDF that implements the system-supplied UDTF routine named OUTPUT_QUEUE_ENTRIES; unsure if the lack of full details/context of the messaging would change that, but still, that is just a SWAG. There may be something recorded in the feature that tracks -901 conditions.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.