Re: Job log wrap?

[Justin Taylor <jtaylor.0ab@xxxxxxxxx>]

That pointed me to the problem.  The Info Center for QLOGOUTPUT had a note
about "job message queue full action", which led me to the QJOBMSGQFL
system value.

Thanks


date: Fri, 25 Feb 2022 15:39:59 +0000
> from: Rob Berendt <rob@xxxxxxxxx>
> subject: RE: Job log wrap?
>
> Why have the joblogs spool at all?  We stopped doing that years ago.
> WRKSYSVAL QLOGOUTPUT
> We changed that to *PND.
> Some job descriptions from IBM may have LOGOUTPUT(*PND) set also.
> So when the job ends it may not be sitting with a status of
> OUTQ
> It may be sitting at a status of
> JOBLOG   PENDING
> If you need to see the joblog you
> 5=Work with
> 10. Display job log, if active, on job queue, or pending
> The key word being "or pending".
>
> If you just have to have a spool file then it's a simple matter of
> DSPJOBLOG job(...) OUTPUT(*PRINT)
> And basically the only reason I can think of that might be to send to IBM.
>
> And when you start using *PND it makes searching all your pending job logs
> across your entire system for a particular message really simple with
> https://www.ibm.com/docs/en/i/7.4?topic=services-joblog-info-table-function
>
> And if you're really into storing joblogs into some custom archive it's a
> lot easier to use the above function to output them to a DB2 file.
>
> I fail to understand the fascination with spool files.  After all, if you
> need to query a file do you do a CPYF OUTPUT(*PRINT) and look at the spool
> file or do you query the file directly?
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  7310 Innovation Blvd, Suite 104
>           Ft. Wayne, IN 46818
> Ship to:  7310 Innovation Blvd, Dock 9C
>           Ft. Wayne, IN 46818
> http://www.dekko.com