Hello, Vengoal
I'm suggesting that this should not be done. This i after reviewing the
Work Management manual, to see if this is suggested. I found nothing there.
The spooling support is very tightly defined. There's a whole set of
subsystem descriptions, job queues, job descriptions, classes, etc., that
are used to manage this. It seems risky to change this too much. There's
even a special shared pool, *SPOOL, for these jobs. And only one of those.
One area I saw that COULD be adjusted is the classes used for spooling.
There are different job descriptions for each kind of spool (reader or
writer, remote or local, data base, diskette, print, etc.). Each job
descriptions has different RQSDTA values, thus pointing to different
classes via routing entries. You COULD add pools to the QSPL subsystem
description, then change the classes as you want. And you would normally
put them into *SPOOL, anyway, so you gain little of anything - certainly no
memory segregation. But you could put local writers one place, AFP writers
in another, and remote writers in yet another. There are guidelines in the
Work Management for the size you need for each kind of writer.
But any upgrade of the OS will probably change these back - but there are
subsystem descriptions that are save in an upgrade and can be restored.
One thing you might consider - not sure I'd do this - is to change the
paging value for QSPL to *CALC - this'd let the performance adjuster change
the size of the pool as needed. Ours is *FIXED, so there may be a reason to
leave it that way - e.g., the need to have rapid response when a writer
needs to print something. Because printers are often inactive, *CALC may
result in not enough memory at the time of need.
At 11:40 AM 12/4/2003 +0800, you wrote:
Dear all,
I have about 360 printer writer job running in QSPL subsystem. I
want to divide those printer job to other than QSPL. The system default
set those printer writer job to QSPL. How do I separate those printer
writer job to myself created subsystem ?
Best regards,
Vengoal
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.