MIDRANGE dot COM Mailing List Archive



MIDRANGE-L » January 2013

Re: Spool APIs performance and memory pools



You should be able to see which pool jobs are running in - let me see - does DSPJOB show that information? Yeah, option 1 tells you the subsystem and which pool in that subsystem the job is in.

Print jobs usually run in QSPL - you could also WRKSBSJOB QSPL and see what is happening.

HTH
Vern

On 1/30/2013 12:15 PM, J Franz wrote:
Is the pool *SPOOL used when batch programs are calling QUSLSPL, QUSRSPLA and
other spool api programs, or is it the pools associated with the batch
subsystems (or both)?
We are using a 3rd party product for conversion and merging of spools and need
to resolve a performance issue (with the products and system we have). Currently
pool *SPOOL has enough for "printing" but we are driving a batch process with
hundreds to many thousands of spooled files, and performce is not acceptable.

tia
Jim Franz






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact