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



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.
User-defined function error on member OUTQ_INFO.
Cancel reply received for message CPF503E.

Message ID . . . . . . : CPF4101 Severity . . . . . . . : 40
Message type . . . . . : Escape
Date sent . . . . . . : 07/05/17 Time sent . . . . . . : 09:23:49

Message . . . . : File QASPOUTQ in library QSPL0002 not found or inline data
file missing.
Cause . . . . . : The file was not opened. The reason code is 01. The
reason codes and their meanings are as follows:
01 - The library does not exist.
02 - The file does not exist. The library does exist.
03 - The file does not exist. The library specified as *LIBL.
04 - The file was saved with storage freed.
07 - An inline data file does not exist.
08 - A diskette file with SPOOL(*YES) is being opened for a read operation
and an inline data file does not exist.
10 - The file on the remote system does not exist.
11 - The library on the remote system does not exist.
14 - The member was saved with storage freed on the remote system.

Recovery . . . : Do one of the following based on the reason code shown,
and try the request again:
01 - Change the library name with an appropriate override file command, or
create a library (CRTLIB command) and a file with the appropriate name.
02 - Change the file name, the library name, or both the file name and
library name with an appropriate override file command.
03 - Add the library to the library list (ADDLIBLE command) or change the
file name, the library name, or both the file name and library name with an
appropriate override file command.
04 - Restore the file (RSTOBJ command) or change the file name, the
library name, or both the file name and library name with an appropriate
override file command.
07 - Add an inline data file (DATA command) or change the file name, the
library name, or both the file name and library name with an appropriate
override file command.
08 - Specify the *NO value for the SPOOL parameter on the Override
Diskette File (OVRDKTF) command or add an inline data file (DATA command) or
change the file name, the library name, or both the file name and library
name with an appropriate override file command.
10 - Change the file name in the distributed data management (DDM) file
with a Change DDM File (CHGDDMF) command or use the necessary procedures to
make the file exist on the remote system.
11 - Change the library name in the distributed data management (DDM) file
with a Change DDM File (CHGDDMF) command or use the necessary procedures to
make the library exist on the remote system.
14 - Restore the file that contains the member (RSTOBJ command) or delete
the file (DLTF command) and recreate the file (CRTLF, CRTPF, or CRTSRCPF
command).

Message ID . . . . . . : CPF503E Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 07/05/17 Time sent . . . . . . : 09:23:50

Message . . . . : User-defined function error on member OUTQ_INFO.
Cause . . . . . : An error occurred while invoking user-defined function
OUTPUT_QUEUE_ENTRIES in library QSYS2. The error occurred while invoking the
associated external program or service program QDBSSUDF in library QSYS,
program entry point or external name QSQWRKOUTQ, specific name
OUTPUT_QUEUE_ENTRIES. The error occurred on member OUTQ_INFO file OUTQ_INFO
in library QSYS2. The error code is 1. The error codes and their meanings
follow:
1 -- The external program or service program returned SQLSTATE 58004. The
text message returned from the program is: .
2 -- The external program failed before it completed.
3 -- The database timed out waiting for the program to return. The timeout
value used by the database was 0 minutes and 30 seconds.
4 -- The external program no longer exists or is not found.
5 -- One of the input parameters of the function had a data mapping error.
6 through 26 -- See the previous message in the joblog.
For an external program, the program entry point displayed will be *N.
ecovery . . . : For error codes 1 and 2, determine the cause of the error
from either the SQLSTATE or a previously listed message.
For error code 3, either increase the timeout limit using the QAQQINI file
setting or determine why the external program or service program did not
return in the time allotted.
For error code 4, ensure the program or service program exists for the
duration of the query.
For error code 5, determine the cause of the data mapping error.
For error codes 6 through 26, see the previous message in the joblog.
Refer to the DB2 for i5/OS SQL programming topic collection in the
Database category in the IBM i Information Center book,
http://www.ibm.com/systems/i/infocenter/ for more information on
user-defined functions.
ossible choices for replying to message . . . . . . . . . . . . . . . :
C -- The request is canceled.
I -- The request is ignored.



Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.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.