×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
James
Since a subsystem is a description of a run-time environment for jobs,
yeah, I think it could be set up in a way that makes jobs run more
slowly. This is a technique used to control remote data access and web
server jobs, e.g.
There are several settings - pool sizes and activity levels and all,
classes, routing entries for different kinds of work, all that. This is
a work management question, and that's the book.
If you want help, show us all the stuff you see when you do wrksbsd -
all the options there. And maybe a printout or wrkactjob sbs(yoursbsd)
output(*print) to show us priority levels and all. Also wrksyssts,
especially for that subsystem, and maybe wrkshrpool.
Vern
On 12/10/2010 3:30 PM, James H. H. Lampert wrote:
The subject line sums it up: We have a batch job running on a customer
box, that is taking at least one or two orders of magnitude longer than
it ought to.
I just happened to notice that it's running in an unusual subsystem.
Could the subsystem be what's acting like a sea-anchor on the job? How
would I determine this?
--
JHHL
This mailing list archive is Copyright 1997-2025 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.
midrange.com
