Re: Performance of WRKOUTQ OUTPUT(*PRINT) vs. List Spooled Files (QUSLSPL) vs. Open List of Spooled Files (QGYOLSPL)

2009/5/5 Charles Wilt <charles.wilt@xxxxxxxxx>:

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 :)

Hi Charles

My WRKUSROUTQ uses QUSLSPL to build up a list of spool files (reading
the user space and putting the entries into a file for sequencing,
etc) and performance is okay but not great. It hits a limit on our
joblog queue sometimes when it's over the user space size, and that's
considerably less than your 215,000 entries. Although I've not tried
it I understand QGYOLSPL is more flexible and a better performer.
Resource use when building the list hasn't been dramatic - it can just
be slow (though I'm sure it will be quicker than the WRKSPLF to *PRINT
to DB2 file.

Regards, Martin
[1] http://www.dbg400.net/foswiki/bin/view/DBG400/WrkUsrOutQ