|
On 11/05/2010, at 10:57 AM, DrFranken wrote:
You do need to allow for activity levels for the threads however. For
example we have one job that runs all in it's own subsystem and is the
only job in the memory pool. The job runs well over 400 threads so
there
must be a high enough activity level for that subsystem to allow
many of
the threads to run at once. In our case well over 100. Before threads
an activity level of 1 would have been good for that memory pool.
View
the number of threads for jobs in WRKACTJOB and press F11 until the
thread count is displayed.
Isn't that an implication of "thread" being short for multiple thread
of execution therefore to have multiple threads active at one time
would require an available activity level? Seems obvious to me but
perhaps worth pointing out for batch jobs.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
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.