132 Customizing IBM Tivoli Workload Scheduler for z/OS V8.2 to Improve Performance
7.1 Factors affecting the Job Scheduling Console
Job Scheduling Console (JSC) performance depends on various factors. Apart
from fine-tuning the Tivoli Workload Scheduler for z/OS engine for better user
performance (which would affect not only the JSC, but ISMP and other user
interfaces as well), there are some customizations that are only related to the
Job Scheduling Console performance.
In the following sections, we describe some of these customizations for
optimizing the Job Scheduling Console performance.
7.2 Applying the latest fixes
Always apply the latest Job Scheduling Console fix packs and corresponding
connector patches. Tivoli frequently introduces performance improvements in
these patches and using the latest versions will ensure that you are taking
advantage of these improvements.
7.3 Resource requirements
Although a minimum of 128 MB RAM is required for the base installation, this is
generally insufficient for most Tivoli Workload Scheduler environments. Consider
at least 512 MB, or for larger environments, 1 GB memory for the machine to
host the JSC. Also, if you have a busy Tivoli management region server (with
other Tivoli applications running on it) to host the connector, consider installing a
separate Tivoli management region server exclusively to be used for IBM Tivoli
7.4 Setting the refresh rate
The refresh rate in the JSC determines the number of seconds after which a list
display will periodically refresh. Do not forget that the JSC is not designed to be a
real-time user interface for performance reasons, that is, plan updates appear in
the JSC either on an on-demand request for a snapshot of the information or an
auto-timed request for the same.
By default, periodic refresh is disabled. You can set the scheduling controller
periodic refresh rate property for a minimum of 30 seconds to a maximum of