No, at least for the API's you mention..
The *SPOOL memory pool is used by the spooling subsystem, ie. the writers
themselves.
Unless your third party offers some sort of "logical printer" functionality
(Gumbo's does for instance) it shouldn't be making use of *SPOOL.
Have you ask the vendor?
Charles
On Wed, Jan 30, 2013 at 1:15 PM, J Franz <franz400@xxxxxxx> 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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
