Automation Concepts

This section provides details of the following automation concepts of SA z/OS:

Overview of Automation Logic
In SA z/OS, the automation function is split up, as follows:
How Requests Become Goals
A request asks that one specific resource (its target resource) should be moved to a specific state (its goal). A resource may, for example, be an application that should run on a certain system.
How Request Propagation Works
Relationship Support
One of the most effective automation capabilities of SA z/OS is the concept of dependency relationships. You define relationships between dependent resources and supporting resources.
How the Automation Manager and Automation Agents Cooperate in a Sysplex
Locked Votes and Requests
When the automation manager tells an automation agent to start or stop a resource, it internally locks the current winning vote on the resource.
Goal Driven Automation
Automatic Calculation of Schedules (Service Periods)
Service periods allow you to schedule the availability of applications, application groups, or monitor resources. A service period is a set of service windows during which a resource (application, application group, or monitor resource) should be active or inactive.
Event and Trigger Support
This section describes the concepts of events and triggers and how you can use them.
Error Thresholds
Error thresholds influence whether or not SA z/OS recovers from an error situation. Thresholds are a number of error conditions within a certain time interval, such as five error conditions requiring restart within one hour.

Parent topic: Concepts