Configuring for availability

It is recommended that you install the tracker and controller as separate subsystems on a Tivoli Workload Scheduler for z/OS controlling system. The tracker can then continue to collect events even when the controller is stopped. Events are created by SMF and JES exits, and added to a queue in the z/OS extended common service area (ECSA). If the event writer is not active while work is running in the system, the queue might fill up, and new events might be lost. Tivoli Workload Scheduler for z/OS cannot recover these lost events.

You can improve Tivoli Workload Scheduler for z/OS availability using the z/OS® Automatic Restart Manager (ARM). Automatic restart management can reduce the impact of an unexpected error on Tivoli Workload Scheduler for z/OS because it can restart it automatically, without operator intervention.

To use Automatic Restart Manager, set the ARM parameter in the OPCOPTS statement to YES. For details about the ARM parameter, see Tivoli® Workload Scheduler for z/OS: Customization and Tuning.