Customizing IBM Tivoli Workload Scheduler for z/OS V8.2 to Improve Performance

132 Customizing IBM Tivoli Workload Scheduler for z/OS V8.2 to Improve Performance

7.1 Factors affecting the Job Scheduling Console

performance

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

Workload Scheduler.

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

Chapter 7. Optimizing Job Scheduling Console performance 133

7200 seconds (12 minutes). Note that in addition to this default value, you can

use a separate setting for each filter window.

To adjust the refresh rate:

1. In the Job Scheduling view, select a scheduler engine and click the

Properties button in the toolbar. The Scheduler Properties window opens

(Figure 7-1).

2. Open the Settings page and alter the Periodic refresh value by entering the

number of seconds after which a list display will periodically refresh.

Figure 7-1 Setting the refresh rate and buffer size

Tip: Do not set this property value too low. Otherwise, if the displayed list gets

very large, the interval between auto-refreshes might be less than the time it

takes to actually refresh, and the Job Scheduling Console will appear to lock

up. Also, if you are using several detached windows (you can detach up to

seven windows), setting the refresh rate properly becomes even more

important.

Important: Increasing the frequency that a list is refreshed decreases

performance. Unless separate settings are set for each filter window, the

default refresh rate will be used.