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


  1.  Home
  2. MIDRANGE-L
  3. January 2019

Re: JOB_INFO when system job tables are really large.

Off the top of my head, Rob, the only thing I see is brute force.  Can you get chunks of the data? Perhaps filter by date into temporary tables,  then stitch it all back together.


On 1/3/2019 7:40 AM, Rob Berendt wrote:
I'm trying to clean up some stuff around here after an earlier situation.

I'm hoping the list can tell me how to get the SQL statement running.

DSPSYSSTS
Jobs in system . . . . . : 115123

WRKUSRJOB USER(<redacted>)
CPD0976
Message . . . . : Information displayed is not complete.
Cause . . . . . : There are more items to be displayed than the maximum
size allowed for the list. Only part of the information is displayed.

Run SQL Scripts
SELECT JOB_NAME, JOB_STATUS, JOB_LOG_PENDING, J.*
FROM TABLE(QSYS2.JOB_INFO(
JOB_USER_FILTER =>'<redacted>')) J
WHERE job_status<>'OUTQ'
FETCH first 100 ROWS ONLY;

Hangs...

IBM i 7.3, DB2 group 12, cume 18242

PMR 77048,082,000



Rob Berendt



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.