Re: Question on securing joblogs -- MIDRANGE-L

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

The /job message queue/ is truncated after QPJOBLOG is spooled. The JMQ is a compact control block of message ID [and details], whereas the QPJOBLOG is a verbose mashup of the text from each message ID, first and sometimes second level text [according to the LOG() filtering that was set for the job], and the associated formatting [including blanks]. I think it is probably safe to say that the *PND will have a disk-saving effect as compared to defaulting to spooling. However, consider that the spool member purging rules, could skew the results for the ability to visualize the effect either way.

Regards, Chuck

Voris, John wrote:

<<SNIP>>
But have you seen a big DASD hit for changing this value?
Rob wrote:

Starting in V5R4 you may wish to look at
WRKSYSVAL QLOGOUTPUT We changed it to *PND. Now, instead of spooling up into output queue QEZJOBLOG when you do a WRKJOB... and take option 4
for spool files there is no joblog. Now, even though the job is ended, you do a option 10
to look at the joblog.

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.