You can attach a data queue to the outq and an entry will be placed in
the data queue for every spool file that goes to a RDY state in the out.
But, it won't do anything if they go in as HLD as I recall. Also,
there isn't a mechanism to tell you if the spool file gets deleted
printed , or moved. Maybe setting up auditing for spool files may be a
better choice? You'd have to process the journals.
charles.wilt@xxxxxxxxx 05/05/2009 1:42:31 PM >>>
All,
We've currently got a home grown app that uses WRKOUTQ OUTPUT(*PRINT)
to build a spool file of all spool files on a particular OUTQ. Then
it loads those into a DB file and displays reports matching a certain
criteria (name, date, user data) to the user for the user to view or
print.
Given that one of the output queues in question has 215,000 spool
files, our application sucks up lots of resources but does provide
currently acceptable performance.
I'm looking to redo the app to use less resources while providing the
same or better performance.
I'm wondering if anybody has any input to provide about the
suitability of List Spooled Files (QUSLSPL) vs. Open List of Spooled
Files (QGYOLSPL) to meet those requirements.
Otherwise, I'm thinking of a redesign that would probably envolve
having a data queue attached to certain output queues so that the
application could maintain it's own DB file without having to rebuild
the file each time.
Comments on that approach are welcome also.
And no, having the users actually delete some spool files is not
realistic on my part :)
Thanks,
Charles Wilt
midrange.com
