RE: Keep spool file in outq QEZDEBUG

[Rob Berendt <rob@xxxxxxxxx>]

On a tangential note...
We do not spool up joblogs anymore.  We have changed the system value QLOGOUTPUT to *PND.  Many IBM supplied job descriptions were already changed by IBM to 
Job log output .: *PND
This basically keeps the joblog in a pending state.  This has many benefits
1 - Users do not see any joblogs as a spool file associated with them.
2 - It makes it much easier to query joblogs using https://www.ibm.com/docs/en/i/7.4?topic=services-joblog-info-table-function
3 - Querying spool files with things like https://www.ibm.com/docs/en/i/7.4?topic=services-spooled-file-data-table-function suck because the message could be split over two lines.
4 - If you just have to have a history of joblogs stored into a file it's a hell of a lot easier, and more orderly, to pipe https://www.ibm.com/docs/en/i/7.4?topic=services-joblog-info-table-function into your historical file.

If you just have to have a spooled version (like for sending to IBM) you simply do a DSPJOBLOG OUTPUT(*PRINT) adding additional parameters as needed.
The same GO CLEANUP option to clean up spooled versions of joblogs cleans these up too.

Think of it this way... if you have to look at a file do you do a 
     CPYF FROMFILE(MYLLIB/MYFILE) TOFILE(*PRINT)
And look at that or do you query the data directly?

See also:
WRKJOBLOG JOBLOGSTT(*PENDING *SPOOLED)    

Rob Berendt