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



There's a difference between creating a joblog and creating a spool file
in an output queue of that joblog.
All jobs create a joblog. With the system value QLOGOUTPUT set to *PND
the joblog is still associated with that job. Hence why DSPJOBLOG
JOB(...) OUTPUT(*PRINT) still works. And why option 10 on WRKJOB still
works. And I can have a job, totally complete, even with no spool files,
stay on the system until the CLEANUP removes the joblog. You've seen that
with your JOBLOG PENDING jobs.

For testing purposes, or maybe even a gradual roll out, look at
CHGJOBD JOBD(lib/jobd) LOGOUTPUT(*PND)

As far as troubleshooting, well, we try to do it before GO CLEANUP removes
the joblog. We normally find the issue before the week is out. I do have
a command exit program on signoff that says if initiated by QSECOFR then
do a DSPJOBLOG OUTPUT(*PRINT) after overriding the output queue to
QPJOBLOG to an output queue that automatically generates a PDF and emails
it to me.

<snip>
PCI compliancy may also require them.
</snip>
"May" being the key word here. I doubt it.

Look at it this way, the joblog from a job that's all qsHell scripts is
worthless. How would that help with compliance?

And there are a few APIs to deal with these non spooled up joblogs also.

Rob Berendt

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.