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



Paul,

>When I submit a job and after it runs successfully it is no longer
>accessible when I do a WRKSBMJOB. All these jobs run in QBATCH. The system
>value QSPLFACN is set to *KEEP. I want my spool files to be still
accessible
>from a WRKSBMJOB. Is there something else I am missing?

Is it possible that the SPLFOWN parameter was used for the printer file?
This could cause it to be owned by a group profile and it would show up in
a different job.

If I had this problem I would use security auditing to gather more
information. Make sure that  *AUDLVL is listed for the QAUDCTL system value
and that both *PRTDTA and *SPLFDTA are listed for the QAUDLVL system value.
Then after the application has run again use DSPJRN for the QAUDJRN audit
journal and look at the PO and SF audit records. The SF audit records will
tell you if the spooled files were created, deleted, or moved to a
different output queue. They will also tell you the name of the job that
owns the spooled files. (If SPLFOWN was used.) The PO audit record may help
you determine if the printed output was actually printed instead of being
spooled or if it was printer by a printer writer.

I hope this helps.

Ed Fishel,
edfishel@xxxxxxxxxx


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.