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



rob@xxxxxxxxx wrote:
My question is, if you changed the system value to leave them in a *PND state instead of the default to print them, why would you then want them to print? Or is the point of the api and this joblogsvr to programmatically determine which ones to print automatically? Frankly, I don't see a need to print any joblog automatically. Nor to even spool it up. Just makes it easier for the user to delete the spool file.

Rob Berendt
The only problem you'll have is that if you don't keep up on deleting old jobs then after awhile the Work Control Block Tables will get quite large and numerous. It used to be IBM advised us to keep those tables as small as possible by deleting spool files. Don't know if this advice has changed, but I suspect it hasn't.

My guess is that since you're only seeing it in the history log then it's probably not that important. IBM is probably issuing a warning in case there are jobs that change their LOGOUTPUT to *JOBLOGSVR.


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.