RE: Question about performance of QUSLSPL vs WRKOUTQ

Turns out I was confused, but google sorted me out. Keywords: asynchronous
list spool. (You really should try this - it's amazing what a little
self-help can do!)

There were four or five Java example sites from IBM, and this:
http://www.code400.com/forum/showthread.php/10140-Get-list-of-spooled-files-
QGYOLSPL-QGYGTLE


Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"One never repents of having spoken too little, but often of having spoken
too much."
-- Philippe de Commynes

I believe QUSLSPL is capable of asynchronous processing. Give it a

smaller

work area (can be a user space, but limit the amount of space you tell the
API to use. It will return to you quickly (from my experience), with an
indication that there's more data. As you consume it, ask for more.

Don't

wait until you have the whole purchase price before you put an offer on

the

house!

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Computers are not intelligent. They only think they are.

I have an Output Queues with 80,000 spooled files (please don't ask why,

I

am working on getting them cleaned up) running V5R4



If I execute WRKOUTQ TEST the processing occurs very quickly and the

list

of

spooled files appears in a few seconds



I have a program that creates a user space then runs the API QUSLSPL to

get

the list of spooled files in the Output Queue

and after 20 minutes it is still running.



I first create a user space TSTOQENT with INITSZ(4000000)



Then

CHGVAR VAR(&OUTQNMLB) VALUE(&OUTQNM *CAT '*LIBL ')

CHGVAR VAR(&FORMAT) VALUE('SPLF0100')



CALL PGM(QUSLSPL) PARM('TSTOQENT QTEMP ' +

&FORMAT '*ALL' &OUTQNMLB '*ALL' '*ALL' )



After 20 minutes this is still running.

Am I using the wrong API?

Is there a faster method of getting a list of spooled files in an OUTQ?

I run this same program against a spooled file with a couple of spooled
files and it is very fast