Re: JOB_INFO when system job tables are really large.

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

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